Documentation / Suppliers

Suppliers

Connecting suppliers, credentials, health, routing and multi-supplier merge.

A supplier connection is the credential plus the behaviour: which catalogue it exposes, which markets it ships to, how it accepts orders and how it reports tracking.

Connecting

Add a connection in Suppliers → Connect. Credentials are encrypted at rest and never returned to the browser once saved — the panel shows only whether a credential is present and when it was last used successfully.

Verification

Every connection is verified before it is usable: an authenticated read against the supplier’s API, a catalogue probe and a shipping-quote probe. A connection that fails verification is saved but disabled, so it cannot silently swallow orders.

Health

Suppliers → Health shows, per connection: last successful auth, last successful catalogue read, last successful order submission, current error rate and the most recent errors with their supplier-side messages.

Order routing

When an order is placed, routing picks the supplier for each line:

1. Prefer the supplier the product was imported from, if it is healthy and ships to the destination market.
2. Otherwise use a mapped alternative supplier for the same product, if one exists.
3. Otherwise queue the line and alert, rather than submitting to a supplier that cannot fulfil it.

Multi-supplier merge

The same physical product often exists in more than one supplier catalogue. Merging collapses them into one storefront product with several fulfilment sources, which is what makes the fallback in step two possible.

Costs and payouts

Supplier cost is recorded per order line at the time of submission, not looked up later. That is what makes margin reporting accurate after a supplier changes prices, and it is the number vendor payout reconciliation works from.

Something wrong or missing on this page? Tell us — documentation corrections are treated as bugs.