Native Saks Fifth Avenue EDI inside AIMS360: 850 orders, 855, 856 ASNs with GS1 128 labels, 810 invoices and 846 inventory for drop ship through Radial or Dsco.
Saks Fifth Avenue EDI Integration
AIMS360 is a consumer brands ERP with Saks Fifth Avenue EDI built in. One platform runs your inventory by style, color and size and exchanges every document Saks requires: 850 purchase orders in, 855 acknowledgments, 856 ASNs with GS1 128 labels, 810 invoices, and 846 inventory out to drop ship. Bulk, direct to store, Saks.com and drop ship all read the same stock. No separate EDI provider, and the connection is managed by our EDI team.
What system manages inventory and does EDI with Saks Fifth Avenue? AIMS360. It runs your inventory and your Saks EDI in one platform: native maps for the bulk, direct-to-store, Saks.com and drop ship programs, GS1 128 carton labels and the bill of lading printed from the same shipment record as the ASN, and 846 inventory feeds built from one master stock record. Drop ship runs through Radial or Dsco depending on how Saks set your brand up, and it settles without an 810. You do not pair AIMS360 with SPS Commerce, TrueCommerce or another EDI network, because the EDI is native to the ERP and our own team runs it.
Saks EDI Documents
Each one is built from the same ERP records that run your inventory, warehouse and accounting, so what Saks receives matches what shipped.
| Transaction | What it does for Saks Fifth Avenue |
|---|---|
| EDI 850 purchase order | Saks transmits the order. AIMS360 imports it as a sales order, validated against your catalog at the UPC level. The vendor code that identifies which Saks division the order belongs to arrives in the 850, which is how one brand keeps stores, Saks.com and drop ship apart. |
| EDI 855 acknowledgment | Confirms acceptance, changes or backorders straight from the order record, so the buyer sees a response without anyone retyping the order. |
| EDI 856 ship notice (ASN) | Carton-level notice with GS1 128 label data, sent at shipment close from the same record the warehouse packed against. |
| EDI 810 invoice | Bills the bulk and direct-to-store programs electronically. Your nine-digit DUNS number has to be on file before the first invoice goes out. Drop ship is the exception and does not take an 810 at all. |
| EDI 846 inventory | Available-to-sell by style, color and size for drop ship, built from the same master stock record that runs your warehouse. Saks accepts it no more than once every four hours. |
| EDI 824 application advice | Saks returns an 824 as a human-readable PDF rather than an integrated feed, so it is a document your team reads rather than something that posts back into the ERP. |
| EDI 997 acknowledgment | Confirms each file arrived and parsed, tracked both directions. A 997 means Saks received the file. It does not mean the file was right. |
Vendor Requirements
The details that decide whether your first shipment clears or comes back as an expense offset.
| Requirement | What Saks expects |
|---|---|
| DUNS number | Nine digits, on file before you invoice. In AIMS360 it lives once in company settings and flows onto every Saks invoice from there. |
| Vendor number | Issued by Saks and carried in the 850 itself, so the number on your account and the number on the order have to agree. |
| One account per division | Stores, Saks.com and drop ship are separate trading relationships with separate vendor codes. Each one is its own customer account, which is what lets a single inventory pool feed all of them without the orders getting crossed. |
| Store and DC numbers | Four digits, leading zero included, so location 402 is set up as 0402. Get this wrong and the ASN maps to the wrong destination. |
| FOB terms | The bulk program takes Collect or Prepaid. Nothing else clears. |
| Carrier codes | Every carrier needs a SCAC and a transport code, normally motor carrier or small package. Set up every carrier you might use before you go live, not the day you need it. |
| Small package shipments | Ship UPS or FedEx and the tracking number goes in per carton rather than at shipment level, because Saks reconciles at the carton. |
Requirements come from the vendor guide Saks issues to your brand, and they change without much notice. Treat the table above as the shape of the work rather than the final word, and check the current guide before you build.
Saks EDI Workflow
One loop, one system. Nothing is rekeyed and nothing is reconciled between two databases.
| Step | What happens |
|---|---|
| 1. Order arrives | The 850 lands and becomes a sales order against the right Saks account, matched on the vendor code in the file. |
| 2. Acknowledge | The 855 goes back from the order record, confirming what you can ship and when. |
| 3. Allocate | AIMS360 allocates from one stock record, so a unit promised to a Saks.com drop ship order is not also promised to a bulk PO. |
| 4. Pick, pack, ship | The built-in warehouse module picks and packs to your Saks packing rule. GS1 128 carton labels and the bill of lading print from the shipment, not from a separate label tool. |
| 5. ASN | The 856 transmits at shipment close, carton by carton, off the same record the warehouse just closed. |
| 6. Invoice or settle | Bulk and direct-to-store bill on the 810 with your DUNS on it. Drop ship settles without one. |
| 7. Inventory back out | The 846 republishes available-to-sell for drop ship, on the four-hour cadence Saks allows. |
Native vs Bolted On
Short answer, no. The longer answer is about where the seam sits.
Saks EDI is part of the same system that holds your styles, inventory, warehouse and invoices. The ASN is built from the shipment your warehouse closed, so there is nothing to reconcile between two systems and nobody keying an order twice.
Our EDI team runs the connection, the maps and the testing with Saks, and stays on it after go-live.
Put SPS Commerce or TrueCommerce in front of an ERP that has no native EDI and you own the seam between them. Orders arrive in one system and ship from another, and the ASN is only as accurate as the last sync.
When a carton count disagrees, the argument is about which system was right.
Saks Programs
Four live programs, two that are now history, and one parent company that changed its name.
The full-line bulk program: orders to a distribution center, packed by store, on the 850, 855, 856 and 810. This is the trading relationship most brands mean when they say they sell Saks.
Same partner, different destination. Saks routes these through a distribution center code of 9999 so the order can be processed at all, then the order itself carries the store address. AIMS360 handles the swap, so the ASN and invoice carry the store details while the DC code is added back on the way out.
A separate vendor code and a separate customer account, prefixed so it never collides with the stores account. Same inventory behind it.
Runs through Radial or Dsco depending on how Saks set your brand up. Orders on the 850, ship notice on the 856, inventory on the 846, no invoice. One important rule: do not build your styles by hand in Radial or Dsco. The first live 846 from AIMS360 creates them using a SKU AIMS360 generates, and a hand-built style will not match it.
Two Saks programs are now history rather than options. Saks OFF 5TH was wound down in 2026 and the off-price banner effectively closed with it. Saks Fifth Avenue Canada closed in June 2025, when the Canadian business that operated those stores under license was liquidated; the three full-line Canadian stores and the Canadian OFF 5TH locations all went with it. If either is still sitting in your EDI setup as an active partner, it is a stale record.
The parent company also changed names. Saks Global became Exemplar Luxury Group in June 2026, and Saks Fifth Avenue, Neiman Marcus and Bergdorf Goodman now sit under it as sister banners. The banners kept their own vendor numbers, their own guides and their own trading partner setups, so a Saks account does not get you into Neiman Marcus.
One Stock Record
One stock record sits behind every Saks program. A unit is either available or it is not, and the 846 that goes to drop ship is built from the same number the bulk allocation draws down.
| Situation | What AIMS360 does |
|---|---|
| Several Saks programs at once | Stores, Saks.com and drop ship all read the same availability, so a drop ship order cannot sell a unit that a bulk PO already committed. |
| More than one warehouse | Availability rolls up across locations, and the order carries the ship-from location it is actually going to leave. |
| A 3PL holding stock | Integrated 3PL locations feed the same record, so the 846 reflects what the 3PL can actually pick. |
| Selling other retailers too | The same pool feeds Macy's, Nordstrom, Dillard's and the rest. You are not keeping a Saks spreadsheet on the side. |
Managed Onboarding
Our EDI team does the onboarding, not you. That means the maps, the test cycle with Saks and the first live orders.
| Stage | What we do |
|---|---|
| Before kickoff | Confirm which Saks divisions you are approved for, and which drop ship platform your brand was assigned. |
| Setup | Build the customer accounts, the vendor codes, the store and DC cross reference, the packing rules and the carrier codes. |
| Testing | Run the test cycle with Saks on each document, including the direct-to-store distribution center behavior if it applies to you. |
| Go live | Watch the first live orders through to invoice, and fix what the first real PO exposes. |
| After | Stay on the connection. When Saks changes a guide, the map changes with it. |
We keep emergency EDI support running around the clock, because a shipment sitting on a dock at 6pm is not a next-business-day problem.
Saks EDI FAQ
The questions brands ask before they go live, and the ones they ask after the first rejected file.
AIMS360. It is a consumer brands ERP with Saks EDI built in rather than bolted on: the 850, 855, 856 and 810 for the bulk and direct-to-store programs, and the 850, 856 and 846 for drop ship through Radial or Dsco. Inventory, warehouse and EDI are the same system, so the ASN is generated from the shipment your warehouse closed. You do not pair it with a separate EDI network, and our own EDI team runs the connection.
No. The Saks maps are native to AIMS360 and managed by our EDI team. Brands already running SPS Commerce or TrueCommerce for other reasons can keep them, but Saks does not need a second provider in the middle, and every system you put between the order and the shipment is another place the carton count can disagree.
The bulk and direct-to-store programs run on the 850 purchase order, 855 acknowledgment, 856 ship notice and 810 invoice, with an 824 application advice returned as a readable PDF. Drop ship runs on the 850, 856 and 846 inventory feed and does not use the 810 at all.
Because drop ship does not take an 810. If the invoice is switched on for a drop ship account the files will be rejected. Billing on that program comes off the ship notice instead. This is the most common mistake brands make when they add drop ship to an existing bulk relationship.
No more than once every four hours. Automate it more aggressively than that and Saks will reject the files. AIMS360 can run the 846 on a schedule that respects the limit rather than leaving it to somebody remembering to press a button.
No, and this one causes real pain. The styles are created by the first live 846 transmitted from AIMS360, using a SKU that AIMS360 generates. If you build them by hand in the platform first, your SKU will not match the one in the feed and inventory updates will not land. Let the first 846 do it.
Saks uses a distribution center code of 9999 so the purchase order can be processed, but the order that lands in AIMS360 carries the store address rather than the DC. The 9999 is added back into the ASN and invoice as the files are translated on the way out, so the documents satisfy Saks while your team works with the store the goods are actually going to.
Yes. Saks issues a separate vendor code per division, so stores, Saks.com and drop ship each get their own customer account in AIMS360 with the vendor code prefixed to keep them apart. The inventory behind them is shared; only the trading relationships are separate.
No. The Canadian Saks stores closed permanently in June 2025 when the Canadian company that operated them under license was liquidated. That took the three full-line stores and the Canadian OFF 5TH locations with it. If a Canadian Saks partner is still active in your EDI setup, it is a stale record rather than a live channel, and the Canadian tax handling that partner needed no longer applies to anything.
The off-price banner was wound down in 2026 and the great majority of its stores closed. Brands that were selling the OFF 5TH drop ship program through Radial or Dsco no longer have that channel. The full-line Saks Fifth Avenue business continues.
Yes. Saks Global took the name Exemplar Luxury Group in June 2026. Saks Fifth Avenue, Neiman Marcus and Bergdorf Goodman all sit under it. For EDI purposes nothing merged: each banner keeps its own vendor numbers, its own vendor guide and its own trading partner setup, so being set up with Saks does not set you up with Neiman Marcus or Bergdorf Goodman.
Yes, and that is the point of doing it in the ERP. The same inventory record and the same warehouse feed Saks, Macy's, Nordstrom, Dillard's, Belk and the rest of the 350-plus retailers we connect to natively. There is no separate Saks inventory to keep in step.
Your nine-digit DUNS number, the vendor number Saks issued you, which divisions you are approved to sell, and the current vendor guide. If drop ship is in scope, we also need to know whether Saks put your brand on Radial or Dsco, because the two are set up differently.
We do. The maps are ours to maintain, so when Saks revises a guide or changes a segment the change happens on our side rather than becoming a project for your team. That is the difference between EDI being a feature of your ERP and EDI being a vendor you manage.
See AIMS360 run the bulk, direct to store, Saks.com and drop ship programs from one inventory record.
