AIMS360 runs Crate & Barrel EDI natively inside the ERP: 850 purchase orders, 855 acknowledgments, 856 ASNs with GS1-128 labels, 810 invoices, 852 sell-through and 997s at X12 4010 from one master stock record, across Crate & Barrel, CB2 and Crate and Kids.
Crate & Barrel EDI Integration
AIMS360 is a consumer brands ERP with Crate & Barrel EDI built in. One platform manages your inventory and exchanges every document Crate & Barrel requires at X12 4010: 850 purchase orders in, 855 acknowledgments, 856 ASNs with GS1-128 labels, 810 invoices out, and 852 sell-through data read back against your own item records, across Crate & Barrel, CB2 and Crate and Kids. No separate EDI provider, and the connection is fully managed by our EDI team.
What does it take to trade EDI with Crate & Barrel? The core set is the 850 purchase order, 855 acknowledgment, 856 ASN, 810 invoice and 852 sell-through, with 997 acknowledgments, all published at X12 version 4010. Cartons need GS1-128 labels, and Crate and Barrel International runs as a separate trading partner profile. AIMS360 runs the whole flow natively, and reads the 852 sell-through feed against your own inventory instead of leaving it in a file nobody opens.
The Banner Map
Vendors rarely sell to all of it at once, and the operational demands differ more than the shared parentage suggests.
The core banner, with a heavy registry and gifting calendar. Registry demand makes availability accuracy matter more than in ordinary wholesale, because a gap shows up in front of a customer who is already committed.
Faster assortment turns than the group average, so item setup speed and feed accuracy carry more weight than pallet volume.
Safety documentation expectations sit alongside standard vendor requirements, with sharper gifting and seasonal peaks.
Listed and mapped separately from the domestic connection, with its own document expectations. Cross-border programs add their own documentation, duty and currency handling.
Banner assignments, trading partner IDs and program scope are set by your vendor agreement and can change. Confirm the live list with your Crate & Barrel contact before onboarding.
Crate & Barrel EDI Documents
Each document below is created from the same ERP records that run your inventory, warehouse and accounting, so what Crate & Barrel receives always matches what shipped.
| Transaction | What it does for Crate & Barrel |
|---|---|
| EDI 850 purchase order | Crate & Barrel transmits order details by banner at X12 4010. AIMS360 turns them into sales orders automatically, validated against live inventory. |
| EDI 855 acknowledgment | Confirms acceptance, changes or backorders from the order record. |
| EDI 856 ship notice (ASN) | Carton-level shipment notice with GS1-128 label data, transmitted at shipment close. |
| EDI 810 invoice | Bills Crate & Barrel electronically, with the order, shipment and terms already attached. |
| EDI 852 sell-through | Product activity and movement data read back against your own item records, informing the next reorder. |
| EDI 997 acknowledgment | Confirms every document arrived and parsed, tracked in both directions. |
| EDI 846 / 860 / 870 | Inventory advice, purchase order change and order status, used depending on the program. |
| EDI 832 / 820 / 864 | Price catalog, remittance advice and text message, used depending on the program. |
Two Things That Are Unusual Here
Most retailers treat sell-through data and version handling as background details. Crate & Barrel makes both load-bearing.
Most retailers treat the 852 as optional. Crate & Barrel runs it as part of the core set, which means you get product activity and movement data back rather than only knowing what was ordered. That only helps if the file lands against your own inventory and open purchase orders rather than sitting in a folder.
Crate & Barrel's published guidelines run at X12 version 4010, while many newer retailer programs run 5010. With a third-party EDI service that split can mean extra mapping charges. AIMS360 maps to whatever version each retailer specifies as part of the platform, so version differences are configuration rather than cost.
How Crate & Barrel EDI Works
AIMS360 sits between Crate & Barrel and your warehouse, turning each EDI document into action and each action back into the compliant document Crate & Barrel expects.
| Step | What happens |
|---|---|
| 1. 850 PO received | Crate & Barrel transmits the purchase order by banner at X12 4010. AIMS360 imports it against live inventory. |
| 2. 855 acknowledgment sent | Acceptance, changes or backorders go back from the order record. |
| 3. Pick, pack, ship in the built-in WMS | Mobile scanning and GS1-128 carton labels printed from the same shipment record as the ASN. |
| 4. 856 ASN at shipment close | Transmits the moment the shipment closes, derived from the real carton record. |
| 5. 810 invoice | Accounting invoices Crate & Barrel automatically with the order, shipment and terms attached. |
| 6. 852 sell-through read back | Product activity data lands against your own item records rather than sitting unread. |
Managed Crate & Barrel Onboarding
Crate & Barrel issues the EDI vendor guidelines, trading partner IDs and labelling requirements once your vendor agreement is in place. AIMS360's EDI specialists clean your item data first, then map and certify test documents at the version your guideline specifies, with the 852 feed confirmed before go-live, the same fully managed EDI service behind every retailer we support. Additional banners or the International profile are added onto the same connection afterwards.
Crate & Barrel EDI FAQ
Crate & Barrel EDI is the electronic data interchange link a vendor runs to trade purchase orders, ship notices and invoices with Crate & Barrel and its sister banners CB2 and Crate & Kids. The core set commonly runs 850, 855, 856, 810 and 852 product activity, with 997, and optional 846, 860, 832 and 870.
The 852 carries sell-through and inventory movement data back to the vendor, and Crate & Barrel treats it as core rather than optional. That is genuinely useful, but only if the file lands against your own inventory and open purchase orders rather than in a file nobody opens.
Crate & Barrel's published specifications, including the 856, run at ANSI ASC X12 version 4010, while many newer retailer programs run 5010. AIMS360 maps to whichever version each retailer specifies, so running both at once is a configuration rather than a second system.
They sit under the same parent business and can share a connection, but assortment, buying team and program details differ per banner. There is also a separate Crate and Barrel International trading partner profile. Confirm which banners and profiles your vendor agreement covers.
Crate and Barrel International is its own trading partner rather than an extension of the domestic connection, with document expectations that can differ. AIMS360 configures each profile separately while keeping both on one stock record.
Yes. Deductions are tracked at document level with reason codes, the originating order and shipment, and the evidence needed to dispute them. See EDI chargeback management.
No. AIMS360 includes managed EDI as part of the platform, with no separate EDI vendor, no per-document fees and no middleware layer to reconcile.
Typically a few weeks depending on how many banners and profiles are in scope and how clean your item data is. Weights, dimensions and carton counts are usually the long pole for home goods vendors.
Yes. Crate & Barrel orders, other retailer EDI programs, Shopify DTC and marketplace orders all allocate against one inventory pool with channel rules.
Get Started
Bring your Crate & Barrel program to a demo and we will walk through the documents, the 852 sell-through feed, the 4010 spec, and how managed onboarding gets you compliant from the first shipment.
