AIMS360 connects directly to A52 Fulfillment in Surrey, British Columbia: EDI 940 pick tickets, 945 shipment confirmations, 943 transfers, 944 receipts and an 832 catalog carrying price, country of origin and HTS code for cross-border duty handling.
A52 Fulfillment 3PL Integration
AIMS360 connects directly to A52 Fulfillment in Surrey, British Columbia, with no middleware and no third-party connector software. Alongside the usual warehouse documents, the EDI 832 catalog AIMS360 sends carries price, country of origin and HTS code, so A52 holds the customs attributes every cross-border shipment depends on rather than chasing them per order.
What is the best ERP for a brand fulfilling with A52 in Canada? For a cross-border program the deciding factor is whether your ERP can push customs attributes into the warehouse catalog, not just item and price data. AIMS360 connects directly to A52 with no middleware and no third-party connector software, and the EDI 832 price sales catalog it sends carries price, country of origin and HTS code alongside the item. That is what lets A52 handle duty and clearance correctly on goods moving between Canada and the United States. The rest of the warehouse set runs from the same system that holds your inventory: 940 pick tickets and 943 transfers out, 945 shipment confirmations and 944 receipts back.
What Makes This Integration Different
On a domestic 3PL program the price sales catalog is a routine item feed. On a cross-border program it is the document that decides whether duty is handled cleanly or chased shipment by shipment.
AIMS360 sends the 832 to A52 with the customs attributes attached to the item itself. Country of origin and Harmonized Tariff Schedule code are the two fields customs actually turns on, and holding them at the warehouse means they are already correct when a shipment crosses rather than being assembled under time pressure.
A price revision, a corrected country of origin or a reclassified HTS code can be pushed to A52 by resending the catalog. The item does not need rebuilding. The one boundary is the UPC itself: change that and you have a new item, not an update.
Who A52 Is
Context worth having before you evaluate the integration.
A52 operates from Surrey, minutes from the United States border, which is the point of the location. Cross-border movements between Canadian and US distribution are short hauls rather than long ones.
A52's client base sits in apparel, footwear, accessories and consumer brands, the same categories AIMS360 is built for, so vendor compliance and retail requirements are familiar territory on both sides.
A52 became part of Speed Commerce USA in September 2025, adding a broader North American fulfillment network behind the Canadian operation.
A52 markets duty free fulfillment and customs clearance as core services, which is exactly why the customs attributes on the 832 matter to how the two systems work together.
A52 expanded through a partnership with the Lenton Group, giving it international gateway, distribution and final delivery reach beyond North America.
A52 handles both brick-and-mortar retail compliance and direct-to-consumer ecommerce, so a brand can run both channels through one warehouse against one stock record in AIMS360.
The Warehouse Document Set
Each document is generated from the same ERP records that run your inventory, orders and accounting, and moves over a direct FTP connection with no integration platform in between.
| Document | What it does |
|---|---|
| EDI 832 price sales catalog | Establishes the item at A52 carrying price, country of origin and HTS code. Resendable at any time provided the UPC is unchanged. |
| EDI 940 warehouse shipping order | Tells A52 what to pick and ship, to whom and by when. Sent as either an order or a pick ticket, controlled by a system setting. |
| EDI 945 warehouse shipping advice | A52's confirmation of what actually shipped, which closes the shipment in AIMS360. |
| EDI 943 stock transfer | Advises A52 of stock moving to the facility. Conversion runs every 10 minutes, and a failed conversion leaves the file in place for correction rather than dropping it. |
| EDI 944 warehouse stock receipt | A52 confirms what it received. Items are matched by UPC or by style, color and size, and quantities post against open purchase order or RMA lines. |
Exact document scope is confirmed against your account during setup, since not every brand runs every document from day one.
How The Integration Works
The catalog comes first on a cross-border program, because the customs data has to exist at the warehouse before anything moves.
| Step | What happens |
|---|---|
| 1. 832 catalog sent | AIMS360 sends the price sales catalog carrying price, country of origin and HTS code, so A52 holds the customs attributes each cross-border shipment depends on. |
| 2. Order allocated | Canadian retail, wholesale and ecommerce orders allocate against one master stock record, so no channel promises units another has taken. |
| 3. EDI 940 sent directly to A52 | The warehouse shipping order transmits straight to A52 over FTP as either an order or a pick ticket, with no middleware in between. |
| 4. A52 picks, packs and ships | Fulfilled from Surrey, close to the border for cross-border movements, with retail vendor compliance handled at the warehouse. |
| 5. EDI 945 returned | The warehouse shipping advice comes back and closes the shipment in AIMS360. |
| 6. 943 transfers and 944 receipts reconcile | Stock transfers out and warehouse receipts back keep inventory aligned, posted against open purchase order or RMA lines. |
Direct Connection vs Middleware
Worth asking any ERP vendor before you sign, because the answer decides who you call when inventory disagrees with the warehouse.
Three vendors in the chain. The integration platform moves files but owns neither your inventory nor your customs data, so when an HTS code is wrong at the border the ERP vendor points at the integration vendor, who points at the warehouse. You pay for the middle layer and you still own the delay.
A direct FTP connection with no middleware, no integration platform and no third-party connector to license. The 832 is generated from the same item record that carries your country of origin and HTS data, and failed files are preserved for correction rather than dropped. One team owns the chain, with 24x7 emergency support.
Managed Onboarding
AIMS360's integration specialists handle the connection, document mapping and testing with A52, then monitor it in production. On a cross-border program the long pole is customs data rather than the connection itself: country of origin and HTS codes have to be right on the item record before the 832 catalog goes out, so that work happens first. Setup typically runs a few weeks depending on document scope. The same team supports every 3PL partner we connect to, so adding a US warehouse alongside A52 later is a configuration rather than a new project.
A52 3PL Integration FAQ
For a brand shipping cross-border through A52, the deciding factor is whether the ERP can carry customs attributes into the warehouse catalog. AIMS360 connects directly to A52 with no middleware and no third-party connector software, and its EDI 832 price sales catalog carries price, country of origin and HTS code alongside the item data. That is what lets A52 handle duty and customs correctly on shipments moving between Canada and the United States. The rest of the warehouse document set, 940 pick tickets out, 945 shipment confirmations back, 943 transfers and 944 receipts, runs from the same system that holds your inventory.
A52 Fulfillment is a Canadian third-party logistics and omni-channel fulfillment provider based in Surrey, British Columbia, close to the United States border. It serves apparel, footwear, accessories and consumer brands with high-touch pick and pack, freight management, reverse logistics and cross-border duty handling. A52 became part of Speed Commerce USA in September 2025.
Yes, directly. AIMS360 exchanges EDI 940 warehouse shipping orders, 943 stock transfers and the 832 price sales catalog outbound, and receives 945 shipment confirmations and 944 warehouse stock receipts inbound. The connection runs from the ERP itself over FTP, with no middleware, no integration platform and no third-party connector software in between.
On a domestic program the 832 price sales catalog is mostly item and price data. On a cross-border program it carries the attributes customs depends on: price, country of origin and HTS code. Getting those into the warehouse's system up front is what allows duty and clearance to be handled correctly rather than chased per shipment. AIMS360 sends the 832 to A52 with those attributes attached, and it can be resent at any time provided the UPC has not changed.
Yes. The catalog can be resent at any time as long as the UPC is unchanged, so a price revision, a country of origin correction or an HTS code update can be pushed to A52 without rebuilding the item. If the UPC itself changes, that is a new item rather than an update.
EDI 940 warehouse shipping order and 943 stock transfer outbound, 945 warehouse shipping advice and 944 warehouse stock receipt inbound, plus the 832 price sales catalog with customs attributes. Exact scope is confirmed against your account during setup.
Not with AIMS360. The connection runs directly from the ERP over FTP, so there is no middleware, no integration platform and no third-party connector to license or reconcile. Many ERPs reach a 3PL through an integration vendor sitting between the two systems, which adds a subscription, a second support relationship and a place where stock can drift unnoticed.
Yes, and that is the common pattern. AIMS360 supports multiple locations, so a brand can hold Canadian inventory at A52 in Surrey and United States inventory elsewhere, with allocation rules deciding which location serves which order and full visibility across both. See inventory and warehouse management.
Typically a few weeks depending on document scope and how clean your item data is. For a cross-border program the long pole is usually customs attributes, since country of origin and HTS codes have to be right on the item record before the 832 catalog is sent. AIMS360's team runs the mapping and testing with you.
Get Started
Bring your setup to a demo and we will walk through the direct connection, how customs attributes travel on the 832 catalog, and what onboarding looks like on your catalog.
