EDI
Shopware's admin API authenticates as a single admin user against one shop URL, not as a trading partner account. That matters because a wholesale purchase order arriving through that same door has no separate channel to carry contract pricing in with it, so the order prices however the storefront's sales channel says it should, and the difference comes off the remittance weeks later as a deduction nobody flagged in advance.
Most of these trace back to timing or to a figure that never matched what the partner expected. A price that resolved against the storefront instead of the contract shows up as an invoice discrepancy. A carton count invented after the fact rather than confirmed against the order shows up as ASN non-compliance.
The admin API needs credentials and a route before it will take a partner's order at all, and the order needs a price to land on besides the one the storefront would offer a browser.
Every one of these runs through the same admin credentials, which means every one of them depends on the order carrying the right price before it moves.
The order lands through the admin API like any other order. Nothing in that order object says it should price differently from a customer checking out on the storefront unless that gets attached separately.
Shopware's shipment confirmation doesn't carry carton counts on its own. Those have to come from the warehouse and get matched back to the order before the ASN goes out the door.
The invoice price has to trace back to the rate agreed when the order was created, not whatever the sales channel's price list shows on the day the invoice gets raised.
This has to go out before picking starts. Sent after the fact, it tells the partner nothing they can still act on.
The order updates in place. The risk is the update resetting the line back to the storefront's default price instead of keeping the contract rate.
This has to land first, ahead of anything above it. Missing, and the partner has no way of knowing their file was even read.
None of these six carry weight on their own if the order they describe was priced against the wrong list.
A wholesale buyer's account terms don't travel through the same admin login a customer order does, so without something carrying that rate across, the order books at whatever the sales channel charges a browser. That gap doesn't show up at order creation. It shows up on the remittance, as a deduction against an invoice that never should have been raised at the storefront rate.
Cogent² AI sits across the order and shipment data moving through the admin API and flags what looks wrong before it reaches a chargeback. The integration layer, Patchworks, carries the connection itself, so a credential change or a shop URL update doesn't mean rebuilding the link from scratch.
Every order converting from a purchase order gets checked against the contract price before it's confirmed, not after.
Carton and quantity detail gets matched to the order before the ASN goes out, not invented at the dock.
The invoice price gets checked against the rate the order was created with, before it reaches the partner.
Anything that doesn't match, a price, a quantity, a missing acknowledgement, gets surfaced and owned rather than left to show up as a deduction later.
The order itself confirms quickly once it's in Shopware, but the ASN depends on the fulfilment record and the carton detail reaching it from the warehouse first. Cutoffs get missed when that handoff is slow, not when Shopware is.
No. Generating the client secret inside Shopware and wiring the scope through is one-off setup work, and Cogent² handles that configuration rather than leaving it for someone on your team to maintain.
Nowhere it has to change. Cogent² takes on the Shopware account and the documents running through it. What the other provider handles for the separate account carries on as it is.
Your team generates both inside Shopware's own admin panel, since they're tied to your account credentials. Cogent² tells you exactly what's needed and where to find it, and takes it from there.
Cogent² updates the check and confirms it with the partner directly. Your team doesn't need to go back into Shopware to make that change.
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.
