Amazon
Purpose
Amazon becomes a sales channel. Four peculiarities of Amazon shape the design — knowing them saves the typical first-attempt failures.
Scope
- Listings through the Listings Items API. Amazon has no „product creation" like a shop: a
listing needs a product type, and which one applies depends on the assortment — hence it lives in the channel configuration.
- Price and quantity are attributes of the SAME listing, not separate endpoints; all three
operations therefore go through PATCH.
- The external id is your own SKU, not an Amazon id: an ASIN belongs to the catalogue, not to
the listing.
- Orders and fulfilment for merchant-fulfilled shipping (FBM).
- Five settings per channel: country, region, seller id, product type and fulfilment mode.
Interplay
The channel is a sales channel in the sense of Channels — not a special path beside the document. Items, prices and stock come from the product catalogue and stock; incoming orders become regular sales orders and travel through warehouse, shipping and invoicing like any other order. Credentials live as an integration under Integrations in the encrypted store. Flows and mappings at the system boundary — which field goes where, when a sync runs — belong to OctiConnect; conditions and waiting times remain the business of automations.
Limits
- FBA stock is READ, never written. Only Amazon knows what it has stored; sending our own number
would overwrite a stock we do not keep. Stock only goes out for merchant-fulfilled items.
- Fulfilment only for FBM. Amazon reports an FBA shipment itself; a report from outside would be
a second shipping truth.
- The real run is still outstanding. What is verified is that we ask correctly and read the
answer correctly — not that Amazon accepts the request. A real seller account is missing.