Packiyo is a warehouse management system built for 3PLs and ecommerce brands, with an open API. Its larger customers ship more than 70,000 orders a day across several warehouses. AIMS360 connects to warehouses running it, by API.
Packiyo is not a 3PL. It is the warehouse management system a 3PL, or a brand's own warehouse, runs on the floor: bins, picking, packing, lots and billing. When the warehouse holding your goods runs Packiyo, AIMS360 connects to it by API, so orders leave your ERP and the shipments come back to it.
Yes. AIMS360 connects to warehouses running Packiyo, and the connection is live. It runs on the API rail rather than by file: the order goes to the warehouse as an API call instead of a 940, and the shipment comes back with carrier and tracking instead of a 945. AIMS360 records the shipment, invoices from it and builds any retailer ship notice from it.
Packiyo is software, so the company you contract with is the warehouse that runs it. Returns are received in Packiyo and closed in AIMS360 on the RMA. Which events your account exchanges is agreed with the warehouse during setup.
A warehouse system, not a warehouse. These are Packiyo's published facts, dated.
| Topic | Packiyo |
|---|---|
| What it is | A warehouse management system built for 3PLs and ecommerce brands, sold by Packiyo Inc. |
| Scale | Its larger customers ship more than 70,000 orders a day across several warehouses; its smallest ship about 100 a day. |
| Inventory | Multi-location and bin-level tracking, lot and batch tracking, and expiration management. |
| For 3PLs | Built-in 3PL billing automation and reporting the warehouse can share with the brands it serves. |
| Connections | An open API, plus native connections to Shopify, Amazon, Walmart, TikTok Shop and the major carriers, and EDI and wholesale setup. |
| Returns | Lists reverse logistics among its inventory features. |
From Packiyo's own site, checked November 3, 2026. The order volumes are Packiyo's figures.
The same events as the warehouse document set, carried by API.
| What moves | Direction | On the API rail | What AIMS360 does with it |
|---|---|---|---|
| Orders or pick tickets | AIMS360 to the warehouse | An order push, the API version of a 940 | Sends allocated orders. Exported pick tickets move from Open to Packed so nothing goes twice. |
| Shipment confirmations | Warehouse to AIMS360 | A shipment update, the API version of a 945 | Records what shipped with carrier and tracking, invoices from it, and builds the retailer 856 or the Shopify tracking update. |
| Inventory | Warehouse to AIMS360 | An inventory update | Keeps the stock at that warehouse in step with what Packiyo shows on the shelf. |
| Returns | Received in Packiyo | Not part of the API connection | You issue and process the RMA in AIMS360, which restocks the goods and issues the credit. |
| Item data | Both sides | Agreed at setup | The same UPC or style, color and size codes must exist in Packiyo and AIMS360 before orders move. |
The business logic in AIMS360 is the same whether a warehouse sends files or API calls. On the API rail, events post back as they happen rather than on a file schedule. See the AIMS360 API.
The ERP is the record of what you own. The WMS is the record of where it sits.
| Job | AIMS360 | Warehouse on Packiyo |
|---|---|---|
| Styles, UPCs and costs | Owns them. The style master is authored once here. | Gets them before the first order and receives goods against them. |
| Orders and allocation | Owns them, across wholesale, EDI, Shopify and marketplaces. | Gets orders that are already allocated and ready to pick. |
| Pick, pack and ship | Sends the instruction, the carrier and the references. | Owns the work on the floor: bins, pickers, cartons and labels. |
| Retailer EDI documents | Owns them. The 850 in; the 856 and 810 out, built from the shipment. | Supplies the carton and tracking detail the documents are built from. |
| Inventory of record | Owns it, across every location, including the Packiyo warehouse and your own warehouse. | Records what is physically on its shelves and reports changes back. |
| Invoicing and receivables | Owns them. The invoice comes from what shipped. | Bills you for storage and handling under your contract. |
Your AIMS360 implementation manager runs this with you and the warehouse.
The warehouse running Packiyo provides API access for your account. Your implementation manager confirms which events it will exchange: orders, shipments and inventory.
Add the Packiyo warehouse as a warehouse 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 shipments back, check the inventory at the warehouse matches AIMS360, and close one return on an RMA before a retailer order depends on it.
Orders route to the Packiyo warehouse from AIMS360 and confirmations come back. Your implementation manager watches the first weeks with you.
Yes. AIMS360 connects to warehouses running the Packiyo WMS, by API. Orders go out, and shipments with carrier and tracking come back, along with inventory updates, onto one stock record by style, color and size.
No. Packiyo is warehouse management software. Your contract is with the warehouse that runs it, and that warehouse provides the API access AIMS360 connects through.
No, it runs on the API rail. The events are the same ones a 940 and 945 carry, sent as API calls instead of files. Retailer EDI stays in AIMS360 either way.
Returns are received in Packiyo and closed in AIMS360. You issue the RMA in AIMS360, the warehouse tells you what came back, and processing the RMA restocks the goods and issues the credit. See returns management.
AIMS360. The shipment confirmation comes back from Packiyo, and AIMS360 builds the 856 and 810 from it, so the warehouse never handles a retailer document.
No. The AIMS360 WMS runs your own building. Packiyo runs the 3PL's building. Both can be live at once as stocking locations on the same record.
Packiyo tracks lots, batches and expiration dates. Confirm during setup which of those fields the warehouse will send back, because AIMS360 can only record what the warehouse returns.
Most 3PL connections move from scoping to go-live in weeks rather than months. Getting API access and lining up item codes are usually the longest steps.
AIMS360 builds and maintains 3PL connections in house. Whether it is included or an add-on depends on your plan; see pricing. The warehouse bills its own services; Packiyo licenses its software to the warehouse.
Name the warehouse. We will show how orders, shipments and stock move between it and AIMS360, on your styles.