EDI Integration
NewStore POS authenticates every call with OAuth 2.0, so a feed to a partner only moves on an authenticated push, not on the moment a till rings up a sale. A shirt sold on the shop floor at two in the afternoon does not drop out of the available count until the next push catches up with it. That lag is where an order gets confirmed against stock a customer is already walking out of the shop with.
PO accuracy fails when an order was matched against a stock figure the shop floor had already moved past. Delivery window and late ASN both trace back to a pick that waited on a store opening its doors rather than a warehouse starting its shift. Invoice discrepancy shows up when a store shipped a substitution and nobody carried that change through to the invoice. Late acknowledgement is the easiest one to lose: if the order's receipt isn't confirmed the moment it lands, the partner has no record it arrived at all.
None of this runs until NewStore POS, the shared stock figure and the partner's own order cadence are checked against each other. These three get confirmed before the first document moves.
Each one has to account for a sale that already happened on the shop floor before the partner ever sees a number.
NewStore POS decrements stock the moment a register rings up a sale, mobile or fixed. The figure sent out has to carry that decrement forward before the partner's own count runs stale against it.
Activity gets logged against individual stores and mobile devices, not a single warehouse line, so the feed has to roll several till points into one activity record per partner.
This is the handshake, not the order. If it doesn't go back promptly, the partner has no proof the order ever reached NewStore at all.
The order has to land against the same stock pool the till is already selling from, or it gets picked against a number that was true an hour ago.
Built once a store or mobile device marks an order picked, so the timing runs on store opening hours and staff rota, not a warehouse shift pattern.
Priced off the shipped quantity, so a partial pick or a substitution has to be carried through before the invoice goes out.
Any one of these breaks if the store's own sale isn't reflected in the figure sent out first.
NewStore POS runs on REST, and every request to it needs a live OAuth 2.0 token before it goes anywhere. That shapes how an EDI feed gets built against it: the connection has to hold a valid token through the whole exchange, refresh it without dropping a document mid send, and treat an expired token as the reason a feed stalled, not a mystery. Nothing about inventory advice or acknowledgement timing works if the authentication layer underneath it is an afterthought.
Confirmed against your instance during onboarding.
Once an account is trading, Cogent² AI watches for the two failure points behind most of the chargebacks above. Both get flagged before they reach a remittance, not after.
The AI compares the last authenticated push against register activity since, and flags a feed that's running behind the floor.
A document sitting unsent gets surfaced while there's still time to file it, not once the partner has already logged it late.
It gets matched against whichever stock pool NewStore treats as the shared figure for that store, the same one the till is drawing down in real time. If the order checks against a count that hasn't picked up the last few sales, it confirms against stock that's already gone.
A deprecation notice is the warning, not the event. It gives a window to remap whatever document the connector sends through that endpoint before NewStore retires it, so the feed needs rebuilding ahead of the cutover, not after the old path stops answering.
The decrement has to be republished the moment it happens, not batched up for later. NewStore drops stock at the point of sale, so the figure sent to a partner is only as current as the last push that picked that sale up.
It depends on when in the store's day that pick actually happens, not on a warehouse shift pattern. A deadline set as if a dedicated pick window exists will slip if the order only gets picked once the floor goes quiet.
No. Cogent² carries the OAuth 2.0 connection, the document mapping and the exception handling. Store staff keep ringing up sales on the floor, and nobody there needs to understand how an acknowledgement gets filed.
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.
