Native Neiman Marcus EDI inside AIMS360: 850 orders with SKU capture, 856 ASNs with GS1 128 labels, 810 invoices, daily 846 inventory and 870 cancellations for drop ship.
Neiman Marcus EDI Integration
AIMS360 is a consumer brands ERP with Neiman Marcus EDI built in. One platform runs your inventory by style, color and size and exchanges every document Neiman Marcus requires: 850 purchase orders in, 856 ASNs with GS1 128 labels, 810 invoices, and for drop ship a daily 846 plus 870 cancellations. The Neiman Marcus SKU arrives on the order and comes back on everything you send. No separate EDI provider, and the connection is managed by our EDI team.
What system manages inventory and does EDI with Neiman Marcus? AIMS360. It runs your inventory and your Neiman Marcus EDI in one platform: native maps for the bulk and drop ship programs, the Neiman Marcus SKU captured from the 850 and returned on the 856 and 810, department number and merchandise type code printed on the GS1 128 carton label, a daily 846 built from one master stock record, and 870 cancellations on the four reason codes Neiman Marcus accepts. Drop ship runs through Dsco. 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.
Neiman Marcus EDI Documents
Each one is built from the same ERP records that run your inventory, warehouse and accounting, so what Neiman Marcus receives matches what shipped.
| Transaction | What it does for Neiman Marcus |
|---|---|
| EDI 850 purchase order | Neiman Marcus transmits the order and AIMS360 turns it into a sales order. On this partner the 850 also creates or updates the Neiman Marcus SKU against your style, which matters because that SKU has to come back on everything you send out. |
| EDI 856 ship notice (ASN) | Carton-level notice carrying the Neiman Marcus SKU and GS1 128 label data, transmitted at shipment close. |
| EDI 810 invoice | Bills Neiman Marcus electronically, carrying the same SKU reference the ASN used. |
| EDI 846 inventory | Required daily on the drop ship program. Available-to-sell comes from the master stock record rather than a separate feed somebody maintains by hand. |
| EDI 870 order status | How you cancel a drop ship line you cannot fill. Neiman Marcus accepts four reasons: discontinued item, cannot ship on time, out of stock, and bad address. |
| EDI 997 acknowledgment | Confirms each file arrived and parsed, tracked in both directions. |
Vendor Requirements
The details that decide whether your first shipment clears or your first invoice sits on hold.
| Requirement | What Neiman Marcus expects |
|---|---|
| The Neiman Marcus SKU | This is the one that catches brands out. Neiman Marcus issues its own SKU, it arrives on the 850, and it has to be returned on the 856 and the 810. AIMS360 captures it off the incoming order and attaches it to your style, so it comes back on the outbound documents without anyone copying numbers between screens. |
| Department codes on the label | Neiman Marcus sends a department number and a merchandise type code on the order, and both have to print on the carton label. The readable copy of the 850 is where you find them. |
| Store and DC numbers | Four digits. Neiman Marcus will send you the full store and distribution center list in a spreadsheet if you ask, which is the fastest way to load them. |
| Pickup confirmation on LTL | Ship less than truckload or full truckload and the pickup confirmation number goes in the PRO number field on the ASN. It can be applied to a batch of shipments at once rather than one at a time. |
| Small package shipments | Ship UPS or FedEx and the lead tracking number goes in the PRO number field instead. The bill of lading stays as it is. |
| Carrier codes | SCAC and transport code on every carrier, motor carrier or small package. Set up every carrier you might use before go-live, because you can ship with more than one and the options have to exist. |
| Vendor number | Issued by Neiman Marcus. Contact your buyer if you do not have one yet. |
Everything above comes from the vendor guide Neiman Marcus issues to your brand. Guides get revised, so check the current one before you build rather than trusting a table on a website, this one included.
Neiman Marcus EDI Workflow
One loop, one system. The retailer's SKU rides through it without anyone retyping a number.
| Step | What happens |
|---|---|
| 1. Order arrives | The 850 lands, becomes a sales order, and the Neiman Marcus SKU is captured against your style. |
| 2. Allocate | Units come off one stock record, so a drop ship order and a bulk PO cannot both claim the same unit. |
| 3. Pick, pack, ship | The built-in warehouse module picks and packs to your packing rule. Carton labels print with the department number and merchandise type code. |
| 4. Routing | For LTL, the pickup confirmation number goes onto the shipments as a batch rather than one by one. |
| 5. ASN | The 856 transmits at shipment close with the Neiman Marcus SKU on it. |
| 6. Invoice | The 810 bills against the same shipment, carrying the same SKU reference. |
| 7. Inventory and cancellations | The 846 goes daily on drop ship. Anything you cannot fill is cancelled on the 870 with one of the four accepted reasons. |
Native vs Bolted On
Short answer, no. The longer answer is about who carries the retailer's SKU.
The Neiman Marcus SKU is captured on the way in and returned on the way out because the order, the shipment and the invoice are the same record. There is no mapping table sitting in a spreadsheet and no second system to keep in step.
Our EDI team runs the connection, the maps and the test cycle with Neiman Marcus.
Put a separate EDI network in front of an ERP with no native EDI and the retailer's own SKU has to be carried across the seam on every document. That is a reconciliation job somebody owns forever.
When the SKU on the invoice does not match the SKU on the ASN, the invoice is the one that gets held.
Neiman Marcus Programs
Bulk and drop ship are set up differently, and the sister banners are set up differently again.
The main wholesale relationship: orders to a DC on the 850, 856 and 810, with department codes and merchandise type printed on the carton label and the Neiman Marcus SKU carried through.
Set up separately from bulk and run through Dsco. Ship via is left open on this program because the order itself tells you how to ship each one. Freight is collect or third party, tracking replaces the bill of lading number, and orders ship on the Neiman Marcus drop ship packing slip.
Two documents matter here that bulk does not need: a daily 846 and an 870 for cancellations.
On drop ship there is a quiet detail worth knowing. To mark a style discontinued on the 846 you send a future availability date of 31 December 2039. It is not intuitive and it is not something you will guess.
Neiman Marcus sits under Exemplar Luxury Group, which took that name in June 2026, alongside Saks Fifth Avenue and Bergdorf Goodman. Nothing merged on the EDI side. Each banner keeps its own vendor numbers, its own guide and its own trading partner setup, so being live with one of them does not put you live with the others.
One Stock Record
The 846 that Neiman Marcus reads every day is built from the same stock record your warehouse picks against. That is the whole argument for doing EDI inside the ERP rather than beside it.
| Situation | What AIMS360 does |
|---|---|
| Bulk and drop ship together | Both draw from one pool, so the daily 846 never advertises a unit that a bulk purchase order already committed. |
| More than one warehouse | Availability rolls up across locations, and each order carries the location it will actually ship from. |
| A 3PL holding stock | Integrated 3PL locations feed the same record, so the feed reflects what can genuinely be picked. |
| Selling the sister banners | Saks Fifth Avenue and Bergdorf Goodman read the same inventory from their own trading partner setups. |
Managed Onboarding
Our EDI team builds the connection and runs the test cycle with Neiman Marcus. You do not project-manage it.
| Stage | What we do |
|---|---|
| Before kickoff | Confirm whether you are approved for bulk, drop ship or both, and get the current vendor guide. |
| Setup | Build the customer account, the SKU handling, the department codes for the label, the store and DC cross reference, packing rules and carrier codes. |
| Store load | Import the store and DC list Neiman Marcus provides rather than typing several hundred locations. |
| Testing | Run each document through the test cycle, including the 870 reason codes if drop ship is in scope. |
| Go live | Watch the first live orders through to invoice and fix what the first real PO exposes. |
| After | Keep the maps current as the guide changes. |
We run emergency EDI support around the clock, because a held shipment is not a next-business-day problem.
Neiman Marcus EDI FAQ
The questions brands ask before go-live, and the ones that only come up after the first rejected invoice.
AIMS360. It is a consumer brands ERP with Neiman Marcus EDI built in: the 850, 856 and 810 for bulk, plus a daily 846 and an 870 for the drop ship program. Inventory, warehouse and EDI are one system, so the Neiman Marcus SKU captured on the incoming order is the same one returned on the ASN and the invoice. Our own EDI team runs the connection.
The most common cause is the Neiman Marcus SKU. That retailer issues its own SKU, sends it on the 850, and requires it back on the 856 and the 810. If your system does not capture it on the way in, it cannot return it on the way out. AIMS360 attaches it to your style as the order is processed, which is why it comes back without anyone maintaining a lookup table.
The bulk program runs on the 850 purchase order, 856 ship notice and 810 invoice. Drop ship adds two: an 846 inventory feed transmitted daily, and an 870 order status used to cancel lines you cannot fill.
On the 870. Neiman Marcus accepts four reasons: discontinued item, cannot ship on time, out of stock, and bad address. Send the status against the specific items in the order rather than the whole order, and leave only the lines you cannot ship on the transaction.
Send a future availability date of 31 December 2039 and the style is treated as discontinued. It is a convention rather than something you would work out from the specification, and it is the sort of detail that costs a brand a week when nobody has seen it before.
In the PRO number field. For less than truckload and full truckload shipments it is the pickup confirmation number; for UPS and FedEx shipments the lead tracking number goes in the same field and the bill of lading is left alone. It can be applied to a batch of shipments at once from shipment processing.
No, and assuming so causes real problems. Bergdorf Goodman puts the pickup confirmation number in the PUA/Load field rather than the PRO number field, and it is a separate trading partner with its own vendor number and its own guide. Same parent company, different setup.
No. The Neiman Marcus maps are native to AIMS360 and managed by our EDI team. Brands running a separate EDI network for other reasons can keep it, but Neiman Marcus does not require one, and every system between the order and the shipment is another place the retailer's SKU can get lost.
The department number and the merchandise type code, along with the usual GS1 128 carton data. Both values arrive on the purchase order and are set up against the account so they print automatically rather than being looked up per shipment.
Ask Neiman Marcus for it. They will provide the store and distribution center locations as a spreadsheet, which imports straight into AIMS360. Store and DC codes are four digits on this partner.
Yes. The carrier and service codes are cross referenced against Dsco's mapping guide, and those codes change, so the cross reference is built from the current guide rather than an old copy. We handle that mapping as part of onboarding.
Yes. Both sit under Exemplar Luxury Group, which took that name in June 2026, along with Bergdorf Goodman. For EDI it changes nothing: the banners kept separate vendor numbers, separate guides and separate trading partner setups, so you onboard to each one individually.
Yes. The same inventory record and the same warehouse feed Neiman Marcus, Saks, Bergdorf Goodman, Nordstrom, Macy's and the rest of the 350-plus retailers we connect to natively. There is no separate Neiman Marcus stock file to reconcile.
We do. The maps belong to us, so when Neiman Marcus revises its guide the work happens on our side rather than landing on your team as a project.
See AIMS360 capture the Neiman Marcus SKU on the order and carry it through to the invoice, from one inventory record.
