Capability
Every channel you sell through, and a record of what it did.
Connecting a channel is easy. Knowing what it changed, when it last succeeded and who owns the failure is the part that usually goes missing. Channel synchronisation here is a piece of work with an owner and an audit trail, not a background job nobody reads.
Synchronisation you can hold somebody to.
A failed sync becomes a task
Channel sync is a work type in its own right, so a failure lands in a queue with an assignee rather than in a log file. It carries the same blocked state, which requires a named unblock action, as any other work.
Credentials you cannot read back
Channel credentials live in Secret Manager. They never reach a browser and cannot be retrieved through the interface — you can confirm a key exists, never see it.
Scoped like everything else
A channel belongs to your tenancy and cannot be addressed from another. Connecting, editing and disconnecting are separate capabilities, so an operator can run a channel without being able to repoint it.
Audited both ways
Every call made for a channel records the tenancy, the key, the actor and the outcome — reads included. Bulk extraction through a channel integration is therefore highly visible.
Priced per channel, per month.
A channel is charged at a flat monthly rate on top of your tenancy, however much volume goes through it. We price the connection rather than the transactions, because a per-transaction rate quietly penalises the channel that works.
Add and remove channels as your distribution changes; the charge follows the channels you actually have connected.
- A flat monthly rate per connected channel
- No charge on volume, orders or messages through it
- Charged on top of the tenancy, like every other metered module
- Disconnect a channel and the charge stops with it
Questions about channels
What counts as one channel?
One connected destination you sell or list through. If you run the same marketplace in three countries as three separate accounts, that is three channels, because it is three sets of credentials, three sync states and three things that can fail independently.
What happens when a channel goes down?
The sync failure becomes a work item in a queue with an assignee, rather than a retry loop nobody is watching. Blocking it requires both a reason and the action needed to unblock, so it cannot be parked silently.
Can a channel see my customer records?
Only what you connect it to, and only within your tenancy. A channel integration is bound to one tenancy and cannot address another's data; every call it makes is audited, including reads.
Do I need the commerce module as well?
It depends what the channel is doing. Listing and distribution can stand alone; if orders are coming back and need to reach a ledger, that is the commerce module's job. We will tell you plainly which you need rather than bundling both.
Related capabilities
Tell us where you list and what has to come back, and we will say which part is a single connection and which part is work at your end.