← Back to all docs

CommerceHub API

CommerceHub (now part of Rithum) is a commerce operations platform connecting brands, retailers, and suppliers across 600+ marketplaces and channels for dropship, marketplace, listing, inventory, and order workflows. An unofficial API lets you programmatically pull orders, inventory, catalog, shipments, returns, and supplier records—and push updates like inventory levels, order acknowledgements, shipment tracking, and invoices back into the platform.

By Alex KlarfeldMay 30, 2026
CommerceHub API

What is CommerceHub?

CommerceHub, now part of Rithum, is a commerce operations platform that helps brands and retailers list, market, and optimize products across all major commerce channels. Its connected ecosystem links more than 600 marketplaces and powers tens of thousands of global brands and retailers running multi-channel listing, dropship, inventory synchronization, and order routing through a shared supplier-retailer network—including the modern, API-first Dsco platform.

Core product areas include:

  • Marketplace & Listings (centralized product distribution and compliance across 600+ channels)
  • Dropship (third-party supplier fulfillment management for retailers, via the Dsco platform)
  • Order Management (unified order consolidation and intelligent routing to fulfillment centers)
  • Inventory Management (synchronized stock visibility across warehouses and sales channels)
  • Private Marketplaces & SupplyExplorer (curated seller networks and supplier discovery)
  • Retail Media, Paid Search & Product Feeds (channel advertising and AI-powered product data optimization)
  • Commerce & Delivery Insights (supplier performance and operational reporting)

Common data entities:

  • Orders, Order Line Items, Acknowledgements, Cancels
  • Shipments, Tracking, Shipping Labels, Invoices
  • Inventory, Stock Levels, Warehouse Locations
  • Catalog, Products, Attributes, Images, Assortments
  • Returns, RMAs, Suppliers, Retailers, Trading Partners

The CommerceHub Integration Challenge

Brands, retailers, and suppliers run high-volume fulfillment on CommerceHub every day, but turning its network workflows into reliable API-driven automation is non-trivial:

  • Partner-gated credentials: API access requires client credentials issued by Rithum support per trading-partner relationship, not self-service signup
  • Mixed integration models: Many connections still run over CSV/EDI batch files rather than the modern Dsco REST APIs, so coverage varies by partner
  • OAuth2 token lifecycle: Access tokens expire and must be refreshed proactively or after 401s, complicating long-running headless automation
  • Retailer-vs-supplier asymmetry: The same objects (orders, shipments, inventory) flow in opposite directions depending on whether you are the retailer or the supplier
  • Catalog mapping variability: Product attributes, assortment rules, and compliance requirements differ across the 600+ connected channels
  • Sync and reconciliation timing: Inventory levels and order status must stay consistent across warehouses and channels to avoid oversells and chargebacks
  • Batch and async operations: High-volume orders, inventory, and catalog updates run as asynchronous batch jobs that need polling and error handling

How Supergood Creates CommerceHub APIs

Supergood reverse-engineers the authenticated Dsco platform flows, OAuth2 client-credential exchange, and CommerceHub's order, inventory, and catalog surfaces to deliver a resilient API layer for your trading-partner account—whether you connect as a retailer or a supplier.

  • Handles OAuth2 client-credential authentication and automatic token refresh securely
  • Maintains session continuity with proactive token rotation and 401 recovery
  • Normalizes responses across Orders, Shipments, Inventory, Catalog, and Returns so you integrate once and rely on consistent objects
  • Aligns with your retailer-vs-supplier direction, assortment rules, and channel-specific attribute mappings

Use CommerceHub with AI agents: CommerceHub MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your trading-partner role, modules, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a hardened CommerceHub adapter tailored to your retailer or supplier configuration and channel mappings.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as CommerceHub and Rithum evolve.

commercehub

API Endpoints

Authentication

POST/authenticate

Exchange OAuth2 client credentials for an access token used on downstream CommerceHub/Dsco calls.

Orders

GET/orders

List consumer orders routed between retailers and suppliers with filters for status, channel, and date range.

Orders

POST/create_shipment

Acknowledge an order and post shipment tracking with line items to fulfill against a retailer order.

Inventory

GET/inventory

Retrieve stock levels and warehouse locations across connected suppliers and channels.

Inventory

PATCH/inventory

Push updated stock quantities to keep channel availability synchronized and prevent oversells.

Catalog

GET/catalog

Pull product attributes, descriptions, images, and assortment membership from the catalog.

Returns

GET/returns

Retrieve returns and RMAs with status, reason codes, and associated order references.

Use Cases

Automate dropship order fulfillment

- Pull new retailer orders and acknowledge them without portal clicks - Post shipment tracking and invoices back to the retailer automatically - Route cancellations and backorders to the right warehouse

Keep inventory synchronized across channels

- Push warehouse stock levels to CommerceHub on a schedule - Reconcile available quantities across 600+ connected channels - Surface low-stock and oversell risks to operations dashboards

Sync catalog and listings to a warehouse

- Pull product attributes, images, and assortments into a central catalog - Validate channel-specific compliance and attribute requirements - Stream listing and product-feed changes to downstream BI tools

Manage returns and supplier performance

- Pull RMAs and return events into your OMS and support tools - Match returns against original orders and shipments - Feed supplier and delivery insights into performance scorecards

Technical Specifications

Authentication

OAuth2 client-credentials flow with partner-issued credentials, handled in a managed session

Connectivity

Authenticated Dsco REST/JSON APIs plus CommerceHub portal flows where modern endpoints are not exposed

Response format

Normalized JSON across Orders, Shipments, Inventory, Catalog, and Returns objects

Rate limits

Adaptive throttling tuned to your trading-partner account to respect per-endpoint platform limits

Session management

Automatic access-token refresh, proactive rotation, and 401 recovery

Data freshness

Near real-time pulls for orders and inventory with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for new orders, shipment confirmations, inventory changes, and returns

Latency

Sub-second reads on cached entities; multi-second writes when posting shipments and inventory batches

Throughput

Horizontally scaled workers sized to high-volume dropship and marketplace order flows

Reliability

Retry, backoff, and idempotency keys for order acknowledgements, shipments, and inventory updates

Adaptation

Continuous monitoring of CommerceHub/Rithum and Dsco platform changes and channel-specific configuration drift

Frequently asked questions

Yes. CommerceHub's network moves the same objects—orders, shipments, inventory—in opposite directions depending on your role. Supergood adapts to your retailer or supplier configuration and normalizes the data either way.

API access uses client credentials issued per trading-partner relationship by Rithum support. Supergood works with your existing entitlements and authenticated sessions—you do not need to build the OAuth and token-refresh plumbing yourself.

Yes. Many CommerceHub connections still run on CSV or EDI files. Supergood surfaces the modern Dsco REST APIs where available and normalizes both paths, so you get a consistent API regardless of the underlying transport.

Both. The Dsco platform supports dropship, marketplace, and buy-online-pickup-in-store flows, and Supergood exposes orders, inventory, catalog, shipments, and returns across all of them through one normalized surface.

Each connection is profiled against its channel-specific attribute, assortment, and compliance requirements. Supergood preserves those mappings rather than forcing a single generic schema across every marketplace.

Ready to get a real API?