Tabgrid
Sign in
← All documentation

Distribution

Send one catalog to stores, marketplaces, and other systems.

A channel decides which published products go out. A store is the account that receives them. Custom output lets another system read the catalog with its own key.

Why a channel is not a product list

Teams usually sell the same assortment in more than one place. A channel keeps the category selection once and sends that feed to every store linked to it. Child categories are included with the parent you select. Draft products in those categories are not sent. Publication is a separate step from completeness.

Example

A seasonal channel includes the Pumps category and two stores. A feed limit of 10 proves the connection. Raise the limit only after both destinations report a result you accept.

How to send a channel feed

  1. Open Channels and add a channel with a name the team recognizes.
  2. Select the categories that belong in this assortment. Children follow the parent.
  3. Select the stores that should receive the same feed. If the list is empty, connect a store first.
  4. Save. Feed limit accepts 1 to 100 and caps that run, which is useful for a trial.
  5. Send the channel feed and read the result per store: sent, failed, and any message. Do not treat one success as proof that every destination accepted the file.

Amazon updates existing SKUs. A new article that has never been listed there is not the same operation as updating a title. Renaming or removing a category that is already on a channel changes the next feed. Review the channel before you send it.

Connect the store that receives the feed

External stores hold credentials. Product descriptions do not. Direct store types include WooCommerce, Shopify, Magento, and Amazon. Google Merchant can receive a product feed and does not provide order data for sales statistics.

  • WooCommerce

    Store URL and consumer credentials. Test the connection before the first channel.

  • Shopify

    The shop domain and either an Admin API token or both Dev Dashboard credentials from the same organization. Do not save both methods at once.

  • Magento

    The fields the form asks for, then a connection test.

  • Amazon

    Seller identity and the other fields on the form. Updates existing SKUs.

  • Google Merchant

    A product feed. Use another source when you need order and sales figures.

Name each connection if you have more than one, for example a full-price shop and an outlet. Run the connection test, then attach the store to a channel. Disconnecting a store does not rewrite a channel that still points at it.

Let another system read the catalog

Custom output is for a website, B2B portal, or other reader that is not one of the store connectors. An ERP project is not required. The workspace has a default feed and can have one additional feed per sales partner. Each feed has its own key. A partner-specific feed can carry that partner's pricing. The public output identifies the feed from the key. Do not pass a partner id on the public request.

  1. Open Custom output. If the feed has no products yet, the page shows an example card shape.
  2. Add a feed when a partner needs a separate key or separate prices. Each feed keeps a distinct import key.
  3. Issue the key and store it as a secret. The caller sends the client id and that feed's output key.
  4. Rotate a key that has been copied into chat, email, or a catalog template. Update only the system that is allowed to hold the new key.
  5. The feed keeps its client, type, and import key. You can rename it. A partner feed can be pointed at a partner that does not already have one. The default feed stays the default.