Ashley Stewart accepts the whole order or none of it. Answer with live inventory.

Ashley Stewart EDI is the electronic data interchange link a vendor runs to trade purchase orders, ship notices and invoices with Ashley Stewart, the plus-size women's apparel retailer founded in Brooklyn in 1991. In AIMS360 the flow runs on the 850 purchase order, 855 acknowledgment, 856 advance ship notice and 810 invoice, with the 860 purchase order change also required. Cartons need GS1-128 labels, and each carton on a small package shipment needs its own tracking number.

The core flow is the 850 purchase order in, then the 856 advance ship notice and 810 invoice back out. Two further documents are specifically required for this trading partner: the 855 purchase order acknowledgment and the 860 purchase order change. AIMS360 configures all of them as part of the trading partner setup rather than as add-ons.

Ashley Stewart accepts order-level status codes only on the 855, with no style or line item detail, and only two codes: AK to accept the order in full, and RJ to reject it if you disagree with any part of it. That makes the acknowledgment all or nothing. There is no partial accept, so you cannot confirm eight of ten styles and flag the rest. Your availability answer has to be right at the moment you acknowledge, which is why the acknowledgment should be driven by live inventory rather than by someone reading a spreadsheet.

Ashley Stewart accepts FOB code DF, meaning defined by buyer and seller, and it is the only option this trading partner accepts. It is set once on the customer's EDI configuration during setup. Worth noting because DF is an FOB term rather than a document type, and it is easy to misread as part of a transaction number.

Yes, for small package shipments. When shipping via carriers such as UPS or FedEx, a tracking number must be present for each carton within the shipment, at the carton level. AIMS360 captures tracking per carton as cartons are packed and carries it into the 856, so there is no need to modify the bill of lading number to use a lead tracking number.

Two things per carrier. A SCAC, the standard carrier alpha code, must be set up for every carrier used to ship to Ashley Stewart, and your carrier can supply it if you do not have it. An EDI transport method code is also required per carrier, most commonly M for motor carrier and P for small package. Both feed the ship notice, and both are configured once during setup.

Store and distribution center codes are loaded during setup, and can be added in bulk through a data import template rather than keyed one at a time. Once loaded, orders route to the correct store or DC automatically and the ship-to detail flows through to the ASN and the carton labels.

Yes. A packing rule can be configured for the trading partner so cartons are built consistently without deciding pack-out order by order. For an apparel vendor running deep size ranges that is where most of the packing time goes, and consistent cartons also make the ASN cleaner because the document is generated from the carton record.

No. AIMS360 includes managed EDI as part of the platform, so there is no separate EDI vendor to license, no per-document or kilocharacter fees and no middleware layer to reconcile. Purchase orders land directly against live inventory in the OMS and documents go back out to the retailer's spec from the same system.

Yes. Ashley Stewart orders, other retailer EDI programs, Shopify DTC and marketplace orders all allocate against one inventory pool with channel rules, so a wholesale purchase order and a strong DTC week cannot quietly sell the same units twice. With an all-or-nothing acknowledgment that single pool matters more than usual, because the accept decision depends on knowing real availability.