Native Stitch Fix EDI inside AIMS360: 850 orders, 855 acknowledgments back within 24 hours, 856 ASNs for facility and customer shipments, 810 invoices and automated 846 feeds.
Stitch Fix EDI Integration
AIMS360 is a consumer brands ERP with Stitch Fix EDI built in. One platform runs your inventory by style, color and size and handles what Stitch Fix asks for: 850 purchase orders in, an 855 acknowledgment back inside 24 hours on every order, 856 ASNs that differ depending on whether the goods go to a facility or a client, 810 invoices, and an 846 inventory feed that can run on a schedule. No separate EDI provider, and the connection is managed by our EDI team.
What system manages inventory and does EDI with Stitch Fix? AIMS360. It runs your inventory and your Stitch Fix EDI in one platform: native maps for the 850, 855, 856, 810 and 846, with the 855 acknowledgment generated from the order record so it goes back inside the 24 hour window Stitch Fix requires on every purchase order. Carton weights are captured by the warehouse module as cartons close, which matters because weight per carton is mandatory on every Stitch Fix shipment. The ASN carries a bill of lading and carrier reference for shipments into a Stitch Fix facility, or a tracking number per carton for shipments going to a client. You do not pair AIMS360 with SPS Commerce, TrueCommerce or another EDI network.
Stitch Fix EDI Documents
Built from the same ERP records that run your inventory, warehouse and accounting, so the acknowledgment, the ASN and the invoice all describe the same order.
| Transaction | What it does for Stitch Fix |
|---|---|
| EDI 850 purchase order | Stitch Fix transmits the order and AIMS360 imports it as a sales order, validated against your catalog at the UPC level. |
| EDI 855 acknowledgment | Required back within 24 hours on every single purchase order. Not on the ones with problems, on all of them. It confirms receipt, any changes, whether you accept the content and whether you can hit the requested ship date. |
| EDI 856 ship notice (ASN) | Carton-level notice with UCC 128 label data. What has to be on it depends on whether the shipment is going to a facility or to a customer. |
| EDI 810 invoice | Bills Stitch Fix electronically from the same shipment the ASN was built from. |
| EDI 846 inventory | Available-to-sell from the master stock record. AIMS360 can run it on an automated schedule rather than leaving it to somebody to remember. |
| EDI 860 purchase order change | Stitch Fix sends one, but it arrives as a document to read rather than something that posts itself into the open order, so a change is reviewed by a person before it is applied. |
Vendor Requirements
Two of these are stricter than most department stores, and one is a dependency that can move your go-live date.
| Requirement | What Stitch Fix expects |
|---|---|
| 855 within 24 hours | Every purchase order gets an acknowledgment back inside a day. This is the requirement that most often trips up a brand used to acknowledging only exceptions. |
| A reason on every rejection | Cancel a whole order or a single line and a note explaining why has to go with it. A silent rejection is not acceptable. |
| Weight per carton | Mandatory on every shipment, whichever way it is going. Not estimated at shipment level, recorded per carton. |
| Shipping to a facility | A bill of lading number is required, plus the carrier's reference number, which maps to the PRO number field. |
| Shipping to a customer | A tracking number is required against every carton rather than one for the shipment. |
| Branded packing slip on direct to consumer | Stitch Fix requires its own branded packing slip in customer shipments. Confirm with your Stitch Fix contact and with our EDI team how that is produced for your specific program before you commit to a go-live date, because it is a genuine dependency rather than a formality. |
| Vendor number | Issued by Stitch Fix. Contact your buyer if you do not have one. |
Stitch Fix is an invitation-based brand partner program and it does not publish a public vendor guide. Everything above comes from the requirements issued to brands we have onboarded, and it can change, so work from the guide Stitch Fix gave you.
Stitch Fix EDI Workflow
One loop, one system, and an acknowledgment that does not depend on anyone remembering.
| Step | What happens |
|---|---|
| 1. Order arrives | The 850 lands and becomes a sales order, validated against your catalog. |
| 2. Acknowledge within 24 hours | The 855 goes back from the order record confirming receipt, acceptance and the ship date. Anything rejected carries a reason. |
| 3. Allocate | Units come off one stock record, so a Stitch Fix order and everything else you sell cannot claim the same unit. |
| 4. Pick, pack, ship | The built-in warehouse module picks and packs to your Stitch Fix packing rule. Carton weights are captured as cartons are closed rather than estimated afterwards. |
| 5. ASN | The 856 transmits at shipment close, carrying a bill of lading and carrier reference for facility shipments, or a tracking number per carton for customer shipments. |
| 6. Invoice | The 810 bills against the same shipment record. |
| 7. Inventory | The 846 publishes available-to-sell, on an automated schedule if you want it. |
Native vs Bolted On
Short answer, no. On a 24 hour clock the longer answer is worth reading.
A 24 hour acknowledgment window is only a problem if acknowledging is a manual job in a second system. When the 855 comes off the order record, it goes back without anyone remembering to send it.
Carton weights are captured by the warehouse module as cartons close, so the mandatory weight is real data rather than a number somebody filled in.
Split the order across two systems and every one of Stitch Fix's requirements becomes a handoff: acknowledge in one place, weigh in another, transmit from a third.
The 24 hour clock does not care which system was late.
Shipment Flows
Stitch Fix buys from brands and then puts the merchandise in front of individual clients through its styling service, so as a vendor you are shipping into two quite different flows.
Bulk goods to a distribution center or store location. Bill of lading number and the carrier's reference number both required on the ASN, weight recorded per carton.
Goods going to the end customer. A tracking number is required on every carton, weight per carton is still mandatory, and Stitch Fix's branded packing slip goes in the box. Confirm the packing slip arrangement for your program before you set a go-live date.
One practical note on the 846: automating it is the difference between a feed that reflects reality and one that reflects whenever somebody last thought about it. On a partner that decides what to show a client based on what you say is available, a stale feed costs you orders you would have filled.
One Stock Record
Stitch Fix picks what to send a client from what it believes is available. The 846 is therefore not a housekeeping document, it is the thing that decides whether your styles get into a box.
| Situation | What AIMS360 does |
|---|---|
| Keeping the 846 current | Available-to-sell is published from the master stock record on an automated schedule, so the feed moves when the stock moves. |
| More than one warehouse | Availability rolls up across locations, and the order carries the location it will ship from. |
| A 3PL holding stock | Integrated 3PL locations feed the same record, so the feed reflects what can genuinely be picked. |
| Selling other retailers too | The same pool feeds Nordstrom, Macy's, Saks and the rest, so nothing is reserved for Stitch Fix that another channel has already sold. |
Managed Onboarding
Our EDI team builds the connection and tests it with Stitch Fix. The two things to settle early are the acknowledgment cadence and the packing slip.
| Stage | What we do |
|---|---|
| Before kickoff | Confirm your vendor number, get the current requirements from Stitch Fix, and establish which shipment flows are in scope. |
| Packing slip | Settle how the branded packing slip is produced for direct to consumer shipments before dates get committed. This is the dependency most likely to move a go-live. |
| Setup | Build the customer account, the packing rules, carton weight capture, carrier codes and the store and DC cross reference. |
| Acknowledgment | Set up the 855 so it goes back inside the window without being a manual task. |
| Testing | Test the 850, 855, 856, 810 and 846 end to end, including both shipment flows. |
| Go live | Watch the first live orders through to invoice. |
| After | Keep the maps current and the 846 schedule honest. |
We run emergency EDI support around the clock, which is what a 24 hour acknowledgment window actually needs behind it.
Stitch Fix EDI FAQ
Stitch Fix does not publish a vendor guide, so these are the things brands find out the hard way.
AIMS360. It is a consumer brands ERP with Stitch Fix EDI built in: the 850 purchase order in, an 855 acknowledgment back within 24 hours, 856 ship notices, 810 invoices and an 846 inventory feed. Inventory, warehouse and EDI are the same system, so the ASN and the carton weights come from the shipment your warehouse actually closed. Our own EDI team runs the connection.
Within 24 hours of receiving the purchase order, on every order rather than just the ones with problems. If you reject a whole order or a single line, a note with the reason has to go with it. When the 855 is generated from the order record it goes back inside the window without depending on someone remembering.
The 850 purchase order, 855 acknowledgment, 856 ship notice, 810 invoice and 846 inventory feed. Stitch Fix also sends an 860 purchase order change, which arrives as a document to review rather than something that applies itself to the open order.
It depends where the goods are going. Shipments to a Stitch Fix distribution center or store need a bill of lading number plus the carrier's reference number, which maps to the PRO number field. Shipments going to a customer need a tracking number against every carton. Weight per carton is mandatory either way.
Yes, for direct to consumer shipments. It is a genuine dependency rather than a formality, so settle how it will be produced for your program with your Stitch Fix contact and our EDI team before you commit to a go-live date. It is the item most likely to move a launch.
Yes, and it is worth doing. Stitch Fix decides what to put in front of a client based on what it believes is available, so a feed that only updates when someone remembers costs you orders you could have filled. AIMS360 publishes available-to-sell from the master stock record on a schedule.
Through Stitch Fix. It is an invitation-based program rather than an open application, so the relationship starts with their buying team, not with an EDI setup. Once you have the vendor number and the requirements, that is the point where we come in.
No. Unlike most department stores, Stitch Fix does not publish its requirements openly, so the guide issued to your brand is the only authoritative source. That is worth knowing before you go looking for a routing guide that does not exist.
No. The maps are native to AIMS360 and managed by our EDI team. A 24 hour acknowledgment requirement and mandatory per-carton weights are precisely the things that suffer when the order lives in one system and the shipment in another.
As cartons are closed in the warehouse module, so the weight on the ASN is the weight of the carton rather than a figure entered later to satisfy the file. That distinction matters when a retailer audits.
Yes. The same inventory record and the same warehouse feed Stitch Fix, Nordstrom, Macy's, Saks and the rest of the 350-plus retailers we connect to natively. There is no separate Stitch Fix stock file to keep in step.
We do. The maps belong to us, so when the requirements change the work happens on our side rather than becoming a project for your team.
See AIMS360 acknowledge inside the window, weigh every carton, and keep the 846 honest.
