Manhattan Associates makes warehouse management software that large 3PLs and distribution centers run. AIMS360 connects to a warehouse on Manhattan by EDI, API or file transfer: ship orders out, shipment confirmations and receipts back, on one stock record.

Manhattan Associates makes the warehouse management software behind many large 3PLs and distribution centers. If your goods sit in a building that runs it, AIMS360 connects to that warehouse by EDI, API or file transfer. Orders go out, and shipments, receipts and stock come back to one record.
Yes. AIMS360 connects to 3PL warehouses and distribution centers that run Manhattan warehouse management software. The connection carries the AIMS360 warehouse document set: 940 ship orders and 943 inbound advice out, 945 shipment confirmations and 944 receipts back. It runs as X12 EDI, as files on a secure file site, or as API calls, whichever your warehouse supports.
Manhattan is software your warehouse runs, so the connection is set up per warehouse. AIMS360 builds it in house with your 3PL's team during implementation and maintains it after go-live. Every unit in that building sits on the same stock record as your other locations, by style, color and size.
| Topic | Detail |
|---|---|
| Who | Manhattan Associates describes itself as a global technology company that sells cloud-based software for supply chain, retail and omnichannel operations. |
| Platform | Manhattan Active is its current platform. It covers planning, orders, stores and warehouses. |
| How AIMS360 connects | X12 warehouse EDI, files on a secure file site, or API. The method is agreed with your warehouse. |
| Who builds it | AIMS360, in house, with your 3PL during implementation. AIMS360 maintains it after go-live. |
| Retailer EDI | Stays in AIMS360. The warehouse returns the 945 and AIMS360 builds the 856, the GS1-128 carton labels and the 810. |
The first row is from Manhattan Associates's own site, checked 18 November 2026.
The AIMS360 warehouse document set. Which ones your account uses is agreed with the warehouse during setup.
| Document | Direction | What it does |
|---|---|---|
| 832 style data | AIMS360 to warehouse | Sends new styles to the warehouse: description, UPC, unit of measure, cost and, if you choose, wholesale price. The warehouse needs the same UPC or style, color and size codes before any order file moves. |
| 940 ship order | AIMS360 to warehouse | Sends orders or pick tickets, your choice in system settings. Exported pick tickets move from Open to Packed, so nothing goes to the warehouse twice. |
| 943 inbound advice | AIMS360 to warehouse | Tells the warehouse what is coming: a vendor PO, a cut ticket or a customer return, so the dock knows what to expect. |
| 944 receipt | Warehouse to AIMS360 | What the warehouse counted in, by UPC or by style, color and size. It posts against the open purchase order or return, and the units become stock. |
| 945 shipment confirmation | Warehouse to AIMS360 | What shipped, with carrier and tracking. AIMS360 records the shipment, marks the pick ticket Shipped, and builds the invoice and, for EDI retailers, the 856 from it. |
| 947 stock adjustment | Warehouse to AIMS360 | Adjusts stock up or down for a miscount, damage or mislabel, with a posting date and a note on why. It corrects a gap; it does not overwrite the count. |
The numbers are shared warehouse vocabulary, not a promise of X12. In AIMS360 these messages travel as XML, CSV, tab delimited or Excel files on a file site the warehouse hosts or AIMS360 sets up, or as API calls for warehouses that work that way.
The same path for a retailer order, a Shopify order or a wholesale order.
From a retailer 850, Shopify, a B2B order or a marketplace. It allocates against one stock record by style, color and size, whichever warehouse holds the units.
By hand, in a batch, or automatically for Shopify orders. If you send pick tickets rather than orders, you decide exactly which units ship, and the warehouse cannot fill from stock you are holding for another account.
The ship order goes out with the ship-to, the carrier and the order references. The pick ticket moves from Open to Packed, which stops anyone exporting it twice.
The warehouse works the order in its own system and labels the cartons.
AIMS360 reads the carrier, matches each item by UPC or by style, color and size, and records the shipment. The pick ticket moves to Shipped.
The invoice is built from the shipment. For an EDI retailer, AIMS360 sends the 856 and the 810 from the same record. For Shopify, fulfillment and tracking go back to the store.
The warehouse keeps working in Manhattan. AIMS360 stays your inventory of record, and Manhattan records what is physically on the shelf. The connection keeps the two in step.
The warehouse does not handle your retailer EDI. AIMS360 takes the retailer order, sends the ship order to the warehouse, and sends the ASN and invoice from the shipment that comes back. See EDI retailers.
A new 3PL becomes another stocking location in AIMS360. Your styles, customers, retailer EDI and history stay where they are. See multi-warehouse.
Your AIMS360 implementation manager runs this with you and the warehouse.
Our implementation team confirms with the warehouse which documents it will exchange and how: files on a file site or API calls.
Add the warehouse as a location, point it at the file site or connection, and give your team the permissions they need.
The same UPC or style, color and size codes must exist on both sides before files move. AIMS360 can send new styles as an 832; some warehouses load item data themselves.
Each AIMS360 ship via code maps to the warehouse's carrier code, carrier name or shipping mode. On the way back, AIMS360 matches on the carrier code first, then the carrier name, then the service.
Decide what the 940 carries. Pick tickets give you control over exactly what ships. Change it later only after every exported pick ticket has shipped and its 945 is processed.
Run real orders out and shipment confirmations back, plus a receipt and a return, before a retailer order depends on it.
Orders route to the warehouse from AIMS360 and confirmations come back. Your implementation manager watches the first weeks with you.
Yes. AIMS360 connects to 3PL warehouses and distribution centers that run Manhattan warehouse management software, by X12 EDI, file transfer or API. Ship orders go out, and shipment confirmations and receipts come back to one stock record. See all 3PL integrations.
Yes. Each Manhattan site is configured its own way, so AIMS360 agrees the documents and formats with your 3PL, builds the connection in house and tests a full cycle before go-live. Book a demo and bring your warehouse's integration guide.
AIMS360. The warehouse returns the 945 with the shipment, and AIMS360 builds the 856, the carton labels and the 810 invoice from it. See EDI retailers.
Most 3PL connections move from scoping to go-live in weeks, not months. Lining up item codes with the warehouse is usually the longest step. Your implementation manager runs it with you and the 3PL.
AIMS360 builds and maintains 3PL connections in house. Whether it is included or an add-on depends on your plan; see pricing. Manhattan Associates and your 3PL bill their own services.
Bring a week of orders. We will show the ship order, the shipment confirmation and the retailer ASN running through AIMS360 on your styles.