Go to App
destinations/overview

Channel Matrix

The seven destinations eListSync ships: auth, rate-limit behavior, and how to connect from the hub.

Integration matrix

These are the destinations in the product today. If a marketplace is not in this table, we do not publish to it.

ChannelAuthTypical limitsNotes
ShopifyOAuth + shop domainGraphQL cost budgetproductCreate, inventory scopes
AmazonSP-API LWA OAuthBurst + restore rateListings items JSON
eBayOAuthInventory API quotasItem + offer
TikTok ShopSeller OAuthShop API rpmProduct sync + shop binding
WooCommerceConsumer key/secretHost-dependentREST /wp-json/wc/v3
Medusa / custom RESTBearer + Base URLYour serverHealth-checked /health
WalmartMarketplace credentialsItem feed quotasItem + inventory mapping

Each destination is a **connection** under your organization. Hobby: 2 channels. Pro: 8. Enterprise: see Pricing.

Supported attributes

Transformers map from the canonical catalog:

  • Title, description, handle
  • Price and currency
  • SKU, stock, GTIN/MPN when stored on the variant
  • Images (absolute URLs)
  • Option values (Size, Color, and similar)

A channel that requires an extra attribute (Amazon product type, TikTok category id) will fail the mapper with a log line naming the field. Fill metadata or the variant, then republish. We do not silently drop required fields.

Connecting stores

Use **/dashboard/destinations**.

  1. Choose the channel
  2. Complete OAuth or paste keys (Woo, Medusa)
  3. Wait for health check
  4. Publish from the Publisher hub

Circuit breaker banners on the hub mean that channel is skipping new publishes until a probe succeeds. Other channels stay up.

Health and breakers

Health is not a ping of our marketing site. For Medusa/custom REST we call your GET /health (and often GET /admin/store) **before save**. For OAuth channels, a failed token refresh opens the breaker.

Read Circuit Breakers, Bulkhead Queues, and Rate Limit Backoffs for the worker behavior.

Channels we do not list

Etsy, Square, Wix, Shopee, Lazada, Mercado Libre, and ad-feed networks are **not** in eListSync. Do not configure a “custom REST” destination hoping those marketplaces will appear — custom REST is for **your** Admin-compatible API (Medusa or a store you operate).