EDI providers report that every Kohl's carton needs a GS1-128 label whose SSCC-18 matches the ship notice. One mismatch can turn into a chargeback.
EDI providers report Kohl's wants the ship notice by the time freight leaves with the carrier. Keying it after the truck departs puts every shipment at risk.
Store replenishment runs on EDI, and drop ship may run through Rithum. Separate counts for each mean one unit can be promised to both.
| iPaaS & Custom Builds | Legacy OMS | Pipe17 | |
|---|---|---|---|
| Native API-First Connectivity | ✅ | ❌ | ✅ |
| Pre-Built Commerce Connectors | ❌ | ❌ | ✅ |
| Custom Integration Mappings | ✅ | ❌ | ✅ |
| Advanced Order Orchestration | ❌ | ✅ | ✅ |
| Exception Management & Alerts | ❌ | ❌ | ✅ |
| Unified Inventory Management | ❌ | ✅ | ✅ |
| Rapid to Implement & Go-Live | ❌ | ❌ | ✅ |
| Easy to Add / Swap Channels & Flows | ❌ | ❌ | ✅ |
| Low Total Cost of Ownership (TCO) | ❌ | ❌ | ✅ |
Each Kohl's acknowledgment, ship notice, and invoice comes from what Pipe17 recorded for the order and its cartons, checked in testing Kohl's approves.
Replenishment orders arriving by EDI, and any drop ship orders you receive through Rithum, draw on the same live count as your DTC storefront.
Pipe17 flags Kohl's orders it cannot route or validate, so your team can fix them before anything goes back to Kohl's.
is better with
EDI providers report that Kohl's expects the ship notice (856) on or before release to the carrier, and that late notices are a common chargeback trigger. Pipe17 creates the advance ship notice (ASN) out of the shipment record your warehouse confirms, and Pipe17's order operations raise an exception for your team on any Kohl's order they cannot route or validate.
EDI providers describe each Kohl's carton as needing a GS1-128 (UCC-128) label with its own SSCC-18, a number that must match the carton's pack-level entry in the advance ship notice (ASN, EDI 856) exactly. Your warehouse or 3PL prints and applies the label from the per-carton data Pipe17 supplies, as Pipe17's retail carton label data describes, scoped to your program.
EDI providers list late ship notices (856) and cartons whose count, UPC, or SSCC-18 does not match the shipment as the most common Kohl's chargeback triggers, and Kohl's publishes evidence requirements for vendors who dispute a charge. Pipe17 keeps the ship notice, the invoice (810), and the order together, and the shipment data behind a disputed charge stays with the EDI order it belongs to.
If your Kohl's drop ship runs through Rithum (DSCO), the platform Kohl's announced for drop ship suppliers in 2019, those orders reach Pipe17 by API through its DSCO drop ship integration, apart from store replenishment EDI, which Pipe17 handles through managed EDI. Confirm your current drop ship setup with Kohl's. Both kinds of Kohl's orders draw on one inventory count with your ecommerce platform, such as Shopify.
EDI providers report that Kohl's tests your EDI documents, including GS1-128 label validation, before it sends production purchase orders (850). After you connect Pipe17 with the Kohl's EDI team and send your vendor number and sample documents, Pipe17 builds the mapping and runs the test exchanges, part of the EDI onboarding Pipe17 scopes per connection.
No, Kohl's suppliers can get Pipe17's managed EDI only by also running the Order Operations Platform. That pairing pays off when Kohl's orders share stock with a storefront, a marketplace, or other retail accounts. Whether Pipe17 fits your Kohl's business explains who it serves.