E-Commerce API Integration: Products, Inventory, Catalogs, and Sales Channels Across Platforms

February 9, 2026

Commerce systems sit at the center of how products are created, priced, stocked, and presented across digital storefronts. Catalogs change constantly, variants move in and out of stock, collections are reorganized, reviews are moderated, and sales channels are added or removed. When commerce data is fragmented across platforms—or stitched together with batch sync jobs—inventory drifts, catalogs fall out of date, and downstream systems make decisions on stale information.

Commerce API integration exists to solve this problem.

In this guide, we explain what a Commerce API actually does, which data models matter in practice, how real-time updates are delivered, and how Unified's Commerce API fits alongside Accounting, Payments, Shipping, CRM, and Marketing within Unified's broader platform.

Introduction to Commerce API Integrations

E-commerce platforms such as Shopify, WooCommerce, and BigCommerce power online catalogs, inventory, and storefront presentation.

Each platform exposes its own APIs, object models, and update mechanisms. Products may be structured differently, inventory may be tracked at variant or location level, and collections or categories behave inconsistently across systems.

Products that need to support multiple commerce platforms quickly encounter:

• Incompatible product and variant schemas
• Platform-specific inventory models
• Inconsistent collection and category hierarchies
• Uneven webhook support for catalog and stock changes

A Commerce API provides a consistent way to read and write catalog and inventory data across platforms, without building and maintaining separate integrations for each provider.

What Is a Commerce API?

A Commerce API allows applications to programmatically manage and consume product-side e-commerce data.

In practice, this includes:

• Creating and updating products and variants
• Synchronizing inventory across locations and channels
• Managing collections, categories, and catalogs
• Retrieving storefront metadata and sales-channel configuration
• Aggregating product reviews and ratings

Commerce APIs focus on what is being sold and how it is stocked and presented. They are deliberately not responsible for orders, payments, customers, or fulfillment.

Commerce API vs Accounting, Payments, CRM, Marketing, and Shipping

Unified treats Commerce as one category within the Finance & Commerce group, with strict boundaries.

• Commerce APIs manage product catalogs: items, variants, inventory, collections, locations, reviews, and sales channels
• Accounting APIs manage financial records: orders, invoices, bills, journal entries, tax rates, and reports
• Payment APIs manage money movement: payments, refunds, payouts, subscriptions
• Shipping APIs manage logistics: shipments, labels, carriers, tracking, and rates
• CRM APIs manage people and relationships: contacts, companies, deals, and pipelines
• Marketing APIs manage audiences and campaigns: lists, members, and engagement data

Commerce data often feeds these systems, but Commerce itself never becomes the source of truth for finance, customers, or fulfillment. Any handoff across categories is explicit and application-controlled.

Real-Time vs Batch Commerce Data

Commerce systems are highly dynamic. Inventory levels change with every sale, catalogs update throughout the day, and reviews are constantly added or moderated.

Live Access to Source Platforms

Unified's Commerce API routes every request directly to the underlying commerce platform. There is no cached replica and no background sync job. Reads reflect the current state of the source system, subject to provider rate limits and availability.

Update Delivery with Webhooks and Polling

Commerce platforms vary widely in event support.

• Some platforms emit native webhooks for product, inventory, or collection changes
• Others provide no webhooks at all
• Certain objects support polling only

Unified supports both native webhooks, forwarded when available, and virtual webhooks, which use polling-based change detection. For objects or providers without webhook support, applications poll list endpoints using incremental filters such as updated_gte.

Core Commerce Data Models

Unified normalizes commerce data into seven standardized objects. Provider behavior varies, and integrations should be designed defensively.

Items (Products)

Items represent products in the catalog.

• Support create, read, update, and remove operations where providers allow
• Store internal and public names, descriptions, tax flags, vendor names, and metadata
• Contain embedded variants and collection relationships

Some platforms restrict deletion or treat it as archiving rather than removal.

Item Variants

Variants represent sellable SKUs such as sizes or colors.

• Support full CRUD where providers allow
• Include SKU, pricing, options, physical dimensions, and visibility flags
• Track availability timing and shipping requirements

Stock is not stored on the variant itself. Inventory is tracked separately.

Inventory

Inventory represents stock levels at specific locations.

• Links items or variants to locations
• Stores current available quantity
• Updates frequently and is often latency-sensitive

Many platforms restrict inventory writes or expose only a single default location.

Collections

Collections group products into categories or catalogs.

• Support hierarchical structures via parent_id
• Control storefront visibility and merchandising
• May be read-only on some platforms

Removing a collection does not delete items, only the association.

Locations

Locations represent warehouses, stores, or fulfillment points.

• Store address, currency, locale, and hierarchy
• Control where inventory is stocked and sold

Location creation or modification is often restricted by providers.

Reviews

Reviews represent customer feedback.

• Include rating, title, content, author details, and moderation status
• Support creation and moderation only where platforms allow
• Expose verification and vote counts as read-only fields

Reviews may contain customer-generated content and should be handled carefully downstream.

Sales Channels

Sales channels define where products are distributed.

• Use a stable slug as the channel identifier
• Reference collections to control catalog exposure
• Are often fixed or read-only on marketplaces

Identity and Ownership in Commerce

Commerce objects use commerce-scoped identities only.

• No CRM contact or company identifiers
• No payment or transaction references
• No marketing list or member linkage

The only cross-category reference is an optional account_id on items, linking to an Accounting account. All other relationships remain strictly within the Commerce domain.

Inventory and Catalog Updates in Practice

Inventory Changes

Inventory updates are delivered through native or virtual webhooks where available, or retrieved via polling with updated_gte. Latency depends on provider capabilities and polling configuration.

Catalog Changes

Item, variant, and collection updates follow the same pattern. Native webhooks provide immediate updates when supported. Virtual webhooks introduce short delays.

Reviews and Moderation

Review creation and moderation behavior varies by platform. Many providers require polling to detect changes.

Security, Privacy, and Data Handling

Commerce data includes both business-sensitive and customer-generated information. Unified's architecture minimizes exposure.

Zero-Storage Design

• No commerce data is stored at rest
• No payloads are written to logs
• Requests are stateless and region-aware (US, EU, AU)

If persistence is required, applications store data themselves.

Sensitive Data Considerations

• Reviews may include names, emails, avatars, and free-text content
• Media assets may include embedded metadata
• Pricing, cost, and inventory levels are commercially sensitive

For AI-driven workflows, MCP-based integrations can remove sensitive fields before data reaches downstream systems.

Common Commerce API Use Cases

Unified Catalog Management

Manage products and variants across multiple platforms from a single integration.

Inventory Synchronization

Keep stock levels aligned across sellers, channels, and locations to prevent overselling.

Marketplace and Channel Enablement

Expose product catalogs consistently across storefronts and marketplaces.

Review Aggregation

Collect and analyze product feedback across platforms.

Commerce Analytics

Combine catalog, inventory, and channel data for reporting and forecasting.

Constraints to Design Around

• Write support varies by provider
• Inventory updates may lag on polling-only platforms
• Reviews often have moderation and write restrictions
• Deletions may be soft-deletes or archives
• Platform feature parity is uneven

These constraints reflect real commerce platform behavior and should inform system design.

Build vs Buy Commerce Integrations

Building In-House

• Multiple APIs to maintain
• Inconsistent product and inventory models
• Custom polling and retry logic
• Ongoing maintenance as platforms evolve

Using a Unified Commerce API

• One category-specific API surface
• Normalized catalog and inventory models
• Live access to source platforms
• Centralized authentication and maintenance
• Usage-based pricing aligned with API volume

Best Practices for Commerce Integrations

• Treat Commerce as product-side data only
• Design for provider variability and partial write support
• Use webhooks where available and poll selectively
• Keep catalog concerns separate from orders and payments
• Restrict access to sensitive pricing and review data

Build commerce integrations with clean boundaries

If your product relies on product catalogs, inventory levels, and storefront configuration across multiple platforms, maintaining separate commerce integrations quickly becomes complex and error-prone.

Unified's Commerce API provides a consistent way to manage items, variants, inventory, collections, locations, reviews, and sales channels, without storing commerce data or collapsing category boundaries.

→ Start your 30-day free trial

https://app.unified.to/login

→ Book a demo

https://calendly.com/d/cph9-g8n-jzg/connect-with-unified

FAQ

What is a Commerce API?

An API that allows applications to manage product catalogs, variants, inventory, collections, locations, reviews, and sales channels programmatically.

Which platforms are supported?

Unified supports platforms including Shopify, WooCommerce, BigCommerce, and many others.

Does the Commerce API handle orders or payments?

No. Orders belong to Accounting, and payments belong to the Payment API.

Are inventory updates real time?

Yes, subject to provider capabilities. Native or virtual webhooks are used where available, and polling is used otherwise.

Does the Commerce API store product data?

No. Commerce data is never stored at rest.

How does Commerce differ from CRM or Marketing?

Commerce manages products and inventory. CRM manages people and deals. Marketing manages audiences and campaigns.