i2i Fulfillment runs distribution centers near Vancouver and near Toronto, and the AIMS360 connection is multi warehouse aware: courier lists and on hand inventory are maintained per distribution center, not pooled into one number. No EDI capability is needed at the warehouse. AIMS360 does the EDI.
Most warehouse integrations treat a 3PL as one place. i2i runs two distribution centers, one near Vancouver and one near Toronto, and the AIMS360 connection knows the difference. Courier lists and on hand inventory are maintained per distribution center rather than pooled into a single number, which is what stops an Ontario order being promised against stock sitting in British Columbia.
The AIMS360 connection to i2i is multi distribution center aware. Both the courier list and the on hand inventory position are maintained per facility, so AIMS360 knows not only that you have 40 units at i2i but that 25 are in Delta and 15 are in Mississauga, and it knows which carriers each building can actually tender to.
Pooling those numbers is the common shortcut and it produces two failures that are expensive and slow to diagnose.
A pooled number lets an Ontario order allocate against units sitting in British Columbia. It ships eventually, on cross country freight you did not price, or it does not ship at all and somebody discovers why on the phone.
Courier availability differs by facility. A pooled carrier list produces labels a warehouse cannot tender, which becomes a held order and a call rather than a shipment.
Inventory templates decide what each location can sell, routing picks the facility that can serve the order, and the courier list applied is the one belonging to that building.
The same model covers your own warehouse, your retail stores, another 3PL and a showroom. Adding a facility is adding a location, not adding a system.
For a brand selling across Canada this is the difference between coast to coast coverage and a single warehouse pretending to be one. West coast orders ship from Delta, eastern orders ship from Mississauga, and the customer sees a normal delivery window rather than a transcontinental one.
Retailer EDI and warehouse integration are two different jobs, and only one of them has to be EDI. AIMS360 performs the retailer side itself: the 850 comes in, and the 855, 856 and 810 go back on that retailer's routing guide spec, with no separate EDI provider or translator in between. The warehouse connection is separate and runs on whatever that warehouse can actually do.
We name warehouse messages with the familiar numbers, 940 for a ship order, 945 for a shipment confirmation, 943 and 944 for inbound advice and receipt, because that is the shared vocabulary of the industry. It is not a statement about file format. Across our partner base those messages travel as API calls, CSV files, tab delimited files and XML, and several of our busiest warehouse connections exchange no X12 at all while their retailers still receive conformant advance ship notices.
The practical consequence: you do not have to rule out a warehouse because it has no EDI department, and you do not have to buy an EDI subscription alongside the ERP.
The full warehouse document set runs in both directions over file exchange, against i2i's own platform. The distinguishing part is not the list, it is that inventory and courier data are held per facility rather than merged.
| Message | Direction | What it carries |
|---|---|---|
| 832 | AIMS360 to warehouse | The product catalog. Style, color, size, UPC and description, so receiving is not guessing at a SKU |
| 940 | AIMS360 to warehouse | The ship order, carrying the pick number, the customer purchase order and the fulfilling facility |
| 943 | AIMS360 to warehouse | Inbound advice, per facility, so each building knows what is arriving at it rather than at the company |
| 944 | Warehouse to AIMS360 | The receipt, posting against the open purchase order or return line at the receiving location |
| 945 | Warehouse to AIMS360 | Shipment confirmation with carton detail, weights and tracking. The carton structure is what lets AIMS360 generate the retailer 856 |
| 947 | Warehouse to AIMS360 | Inventory adjustment against the location that holds the stock |
| 846 | Warehouse to AIMS360 | The inventory snapshot, so each facility's position can be reconciled rather than trusted |
Last reviewed 15 August 2026 by the AIMS360 integrations team.
Integration status reviewed against the AIMS360 production configuration for this partner. Company facts checked against i2i.ca in August 2026 and attributed to the publisher rather than stated as our own.
Attributed to their own site rather than repeated as fact, including the parts that will not suit every brand.
| What they publish | Detail |
|---|---|
| Company | i2i Fulfillment, described as a division of i to i logistics inc., founded 2004 |
| Facilities | Two Canadian distribution centers: Delta, British Columbia, serving the Vancouver area, and Mississauga, Ontario, serving the Toronto area |
| Coverage | Canada only. They publish no United States facility |
| Services | Pick and pack, dropship, business to business and business to consumer, rush orders, retailer compliance, quality assurance, freight management, inventory management, reverse logistics including returns, recalls and repackaging into kits |
| Warehouse system | Their own platform, IBIS, which they expand as Internet Based Inventory System |
| Accuracy | 99.97 percent, their claim, not independently verified |
| Regulated handling | Health Canada licensed for pharmaceuticals, medical devices and nutraceuticals, working to GMP standards |
| Integration approach | They describe IBIS connecting to systems from spreadsheets up to SAP, plus Shopify, WooCommerce and BigCommerce, with EDI connectivity available directly or through IT partners |
| Apparel handling | Not published. Garment on hanger, poly bagging, ticketing, steaming and pressing do not appear anywhere on their site. The industries they publish are healthcare and omnichannel retail |
| Not published | Square footage, staff count, client count, named carriers and named retailer compliance programs |
The regulated handling is worth reading as a positive rather than a curiosity. A warehouse licensed by Health Canada and working to GMP standards is a warehouse that has been audited on lot control, segregation and record keeping by someone other than its customers. That discipline shows up in inventory accuracy whatever the product is.
They do not publish apparel specific handling. No garment on hanger, no ticketing, no steaming or pressing. If your product ships on hangers or needs retailer ticketing done at the warehouse, ask them directly rather than assuming, and look at a warehouse that publishes those explicitly. Our Jet Distribution page covers one that does.
Canada only. Both facilities are Canadian. A brand needing United States fulfillment will be pairing them with a second warehouse, which the multi location model handles, but it is a second contract rather than one.
Cancelling a released pick ticket is a manual step. Once an order has gone to the warehouse, pulling it back is a conversation rather than a button. That is true of most warehouses on our list.
Yes. The full warehouse document set runs in both directions, and the connection is multi distribution center aware: courier lists and on hand inventory are maintained per facility rather than pooled, so AIMS360 knows which of i2i's two buildings holds the stock and which carriers that building can tender to.
No. AIMS360 performs the retailer EDI itself, so the 850 comes in and the 855, 856 and 810 go back on the retailer's routing guide spec regardless of what the warehouse can do. The warehouse connection is separate and runs on whatever that warehouse supports: API, CSV, tab delimited, XML, flat file, or real X12. Several of our busiest warehouse connections exchange no X12 at all, and there is no separate EDI provider to buy because AIMS360 is the EDI.
Because a pooled number lets an order allocate against stock in the wrong building. In Canada that means an Ontario order promised against units in British Columbia, which ships on cross country freight you did not price or does not ship at all. Courier availability also differs by facility, so a pooled carrier list produces labels a warehouse cannot tender. Holding stock and couriers per location lets routing pick the building that can actually serve the order.
Yes, and that is the common setup, because both i2i facilities are Canadian. In AIMS360 every location is a warehouse on the same stock record, including your own building, your retail stores and each 3PL. Inventory templates decide what each location can sell and routing decides where an order ships from, so adding a US warehouse alongside i2i is adding a location rather than adding a system.
They do not publish either. Their site names healthcare and omnichannel retail as the industries they serve, and describes pick and pack, retailer compliance, quality assurance and reverse logistics, but no garment on hanger, ticketing, steaming or pressing. If your product needs that handling at the warehouse, ask them directly rather than assuming, or look at a warehouse that publishes it.
More than you would expect. Health Canada licensing and GMP standards mean the facility has been audited by an outside body on lot control, segregation and record keeping. Those are the same disciplines that produce accurate inventory counts and clean receiving, whatever is in the carton. It is not a substitute for apparel handling capability, but it is a reasonable signal about how the building is run.
Bring orders going to both coasts. We will show you each facility holding its own position, routing picking the right building, and the courier list following the location rather than the company.
