EDI
A marketplace operator does not care how your systems fit together, only that acknowledgements, availability and ASNs land inside the windows its own platform enforces, and that the settlement it sends back can be posted without finance rebuilding it from a spreadsheet. Whether the connection is a flat file or a full API, the scoring, the fee structure and the tax treatment all belong to them. Trading well means working to their rulebook from the first order, not after the first dispute.
Marketplace failure points
Once a marketplace's settlement structure, tax model and feed behaviour are mapped, the pattern repeats without someone re-deriving it each quarter. The work sits in posting templates and arbitration rules rather than in a person's memory of how that account behaves.
Facilitator and direct tax lines post separately, and fee or adjustment lines stay mapped against the order they belong to, so finance works from the ledger instead of a statement CSV.
When the storefront and a marketplace disagree on price, stock or an attribute, the difference gets recorded as a named override rather than left as a mismatch no one can explain.
Order and inventory updates get batched and queued rather than fired one at a time, so a sales spike doesn't trigger rate limiting and leave orders unacknowledged.
Each page covers the documents and the failures specific to that platform.
A posting template built for one marketplace's facilitator model and settlement structure does not transfer to the next one unchanged. Jurisdiction rules, fee lines and channel overrides get written down once per account, so adding another marketplace reuses a known pattern instead of starting the diagnosis from nothing.
Pick based on who issues the document that starts the transaction for you, a purchase order, a seller listing feed or a vendor confirmation, and read the page written for that platform. This hub only covers what every one of them shares: the compliance model stays the partner's, whatever the transport looks like.
Each keeps its own posting template, acknowledgement window and settlement structure, nothing merges between them. What changes is the catalogue layer, where price, stock and attribute overrides now need arbitrating across both channels rather than one, since a change made for one audience can quietly break the other's feed.
A list of which jurisdictions each marketplace account collects and remits in, which direct channels still require you to calculate and remit tax yourself, and the current chart of accounts split between the two. Without that split written down, the ledger has no way to know which line belongs to whom.
That conversation sits with us. We hold the relationship with the posting templates, so a restructured settlement file gets mapped to the ledger again before finance ever has to query a figure that no longer matches what it used to.
Updates get queued and retried rather than dropped when that happens, so an acknowledgement delayed by a burst of traffic still clears before the partner's cutoff instead of falling outside it and counting against the account.
Talk to a Cogent2 operator who has actually delivered this work. We will help you scope, plan and ship — without the agency overhead.
We use essential cookies to keep this site secure and working. We do not run advertising or analytics tracking. You can accept optional cookies or keep only the essentials. See our Cookie Policy.
