EDI
A wholesale or marketplace partner reading your stock feed assumes it reflects what's on the shelf right now, not what was on the shelf before the till rang through the last sale. If the store sells faster than the feed updates, the partner is working from a number your own shop floor already disproved. This page covers EDI for point of sale platforms, where the till is the first place stock actually leaves.
Till to feed
Cogent² sits between the till and the partner, publishing the sale the moment it clears and watching for the gap where a reservation should have released but didn't. The work is wired through Patchworks so a sale decrements the shared pool once, not once per channel.
A till transaction decrements the shared stock pool straight away, and the republished figure goes out to every channel reading from the same source, not just the one that sold it.
Cogent² AI flags units held past a reasonable browse or checkout window, so a reservation that should have cleared doesn't sit there quietly understating what's actually sellable.
Each page covers the documents and the failures specific to that platform.
A POS account rarely ships anything through EDI, so the document that matters here is the inventory advice, not the ASN. What matters is cadence and source: who republishes after a sale, how fast, and whether the reservation logic behind in-store browsing is accounted for before the figure goes anywhere a partner can see it.
Start with where the sale is recorded first, not where reporting happens. Whichever system clears the till transaction and holds the reservation logic for store browsing is the one whose page governs this problem, and its own page covers the detail that applies to it specifically.
Yes, if both decrement from the same shared pool. One system publishing while the other stays silent means the partner is only ever seeing half the picture, and the half they're missing is the half that's actually selling.
It can, if the last till sale of the day is published before the window closes rather than batched overnight. The gap to check is between closing time and whatever time the feed actually refreshes.
No. The mapping between the till's sale event and the partner's feed is configuration work Cogent² carries, not a role your store operations team needs to fill.
Not necessarily. The question is whether that provider can read a till sale the moment it clears and treat it as the same event type as an online order. If it can, it stays. If it can only work from a nightly batch, the gap it leaves is the one this page is about.
A clear answer on how long a browsing or checkout reservation should hold stock before it releases, and confirmation of which system is the single source for the shared pool. Without those two, the feed has nothing reliable to publish from.
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.
