Commerce connections
What is specific about shops and marketplaces, and the two questions to settle before connecting one.
Commerce connections carry two properties nothing else in the catalogue does: they are the source of truth for money that has already moved, and they are usually not the only such source. Both change how you should set them up.
Settle these two first
- Which system owns stock?
- If two channels both hold a quantity and neither is authoritative, an agent comparing them can only ever raise a disagreement — which is useful, and is not the same as being able to correct one. Decide which is the sheet and which is a listing.
- What is an order's identity?
- The reference an agent attaches to items. Where a marketplace order number and your internal number differ, pick one and be consistent, because that field is what merges two arrivals about the same problem.
Per-shop rather than per-account
Several commerce providers issue credentials scoped to a single shop rather than to a seller account. Two shops means two connections, which the connection model already supports — but it also means the shop is part of the connection's identity, and naming your connections after the shop rather than the platform saves confusion in month two.
Marketplaces have approval queues
Several marketplace providers review applications before granting production access, and the reviews are not quick. Where that is the case, the practical consequence is that the application should be submitted at the start of the work rather than when everything else is ready.