a2b Fulfillment runs four warehouses across Georgia, Utah, Pennsylvania and South Carolina, and the AIMS360 connection carries the full warehouse document set with the file transfer hosted by AIMS360. Matching is UPC based, which is fast and unforgiving, so this page covers both.
The full warehouse document set is live with a2b, and the file transfer between you and them is hosted by AIMS360. There is no SFTP server for your team to stand up, pay for, secure or patch, and no third party in the middle billing you monthly for moving files. Matching is UPC based, which is fast and completely unforgiving, so this page covers that too.
On this connection the SFTP sits on our side. You do not stand up a server, you do not buy a managed file transfer subscription, and you do not add a third party to the chain who has to be called when a file does not arrive. Documents move between AIMS360 and a2b on infrastructure we run.
This sounds administrative until you price the alternative. A brand hosting its own transfer inherits a small permanent job: credentials to rotate, certificates to renew, disk to monitor, access to review, and someone to call at 6pm when a file is stuck. None of that is fulfillment work and none of it makes you money, but it all has to be somebody's responsibility, and on a small team that somebody is usually the person you would rather have looking at inventory.
It also removes an argument. When transfer sits with a third party, a missing file starts a conversation about whose side it failed on. Here there are two parties, and one of them is us.
Warehouse integrations match on something. Some use style, color and size. This one uses the UPC as the key that ties an AIMS360 item to a a2b item, on every document in both directions.
UPC matching is the cleaner design when the data is clean. It is one field rather than three, it is the same code printed on the physical label, and it is what a scanner reads in the building, so there is no translation between what the system thinks and what the picker sees.
The trade is that it is unforgiving, and the failure modes are worth knowing before implementation rather than during it.
A style without a UPC has no key. It cannot be matched, so it cannot be received or shipped through the integration until one is assigned.
Two items sharing a code will match to whichever the system finds. That does not error, it just quietly puts the wrong goods in a carton. Duplicates are the single thing to clean before go live.
Retiring a style and reassigning its UPC to a new one is common and it breaks matching against anything still open on the old code.
Run a duplicate check and a missing UPC report before implementation starts. It is an afternoon of work that removes most of the exceptions you would otherwise meet in week three.
Worth saying plainly: this is a shared responsibility, not a warehouse problem or an ERP problem. Any brand selling through retail already needs clean UPCs, because retailers reject on them too. A UPC based warehouse integration just makes the consequence arrive sooner.
The full warehouse document set runs in both directions over hosted file transfer.
| Message | Direction | What it carries |
|---|---|---|
| 832 | AIMS360 to warehouse | The product catalog, including the UPC that everything else matches on |
| 940 | AIMS360 to warehouse | The ship order, serving as order or pick ticket depending on a system setting, with the pick number, the customer purchase order and the fulfilling warehouse |
| 943 | AIMS360 to warehouse | Inbound advice. What is arriving from production or another location and what to expect on the container |
| 944 | Warehouse to AIMS360 | The receipt, posting against the open purchase order or return line |
| 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 for damages, cycle count corrections and found stock |
| 846 | Warehouse to AIMS360 | The inventory snapshot, so each warehouse position can be reconciled rather than trusted |
Because a2b publishes four warehouses, the multi location behavior matters as much as the document list. In AIMS360 each building is its own warehouse on the same stock record, so inventory templates decide what each can sell and routing decides where an order ships from. A Utah order does not get promised against Georgia stock because the two were added together into one number.
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 a2bfulfillment.com in August 2026 and attributed to the publisher rather than stated as our own.
Start with the part that is always true. Your 3PL does not need to support EDI. AIMS360 performs the retailer side itself, so the 850 comes in and the 855, 856 and 810 go back on the retailer's routing guide spec, with no separate EDI provider or translator to buy. The warehouse connection is a different job and runs on whatever the warehouse can do. Several of our busiest warehouse connections exchange no X12 at all.
a2b is one of the warehouses where you have a genuine choice, because they publish retailer EDI capability of their own along with routing guide work and chargeback defense. So the question stops being can it be done and becomes where should it sit.
Our answer, and we would give it the same way if it went against us: keep retailer EDI in AIMS360 in almost every case. The retailer documents are tied to the order book, the invoice and the customer record, all of which live in the ERP. Splitting them means the 856 is produced by a party that does not hold the invoice, and it means a routing guide change has to reach two organizations. One system owning every retailer document gives you one place to look and one party accountable when a chargeback lands.
The case for the other side is a small team plus a warehouse that already runs it well, which is a legitimate trade rather than a mistake. If you go that way, put the owner of routing guide updates and chargeback liability in the contract. Our Fashion Logistics page describes a live connection running exactly that split.
Attributed to their own site rather than repeated as fact.
| What they publish | Detail |
|---|---|
| Company | a2b Fulfillment, headquartered in Greensboro, Georgia, which they market as Atlanta. Their site dates the business to 2001, though outside records disagree, so treat the founding year as approximate |
| Facilities | Four warehouses: Greensboro Georgia at 180,000 square feet, Ogden Utah at 240,000, Hanover Township Pennsylvania near Wilkes-Barre at 260,000, and Graniteville South Carolina at 294,500. Their figures |
| Coverage | Southeast, Northeast and Mountain West. Two coasts are not covered, so a west coast consumer base still ships from Utah rather than California |
| Channels | Direct to consumer, retail business to business, dropship, and marketplace connections including Walmart, Amazon, eBay, Faire and Newegg |
| Retail compliance | They publish EDI connectivity with major retailers, retailer specific standard operating procedures, an EDI portal for invoices, and describe long experience navigating routing guides and defending chargebacks |
| Value added | Kitting and assembly, returns and reverse logistics, product refurbishment, and influencer kits |
| Customer care | They run a contact center, which is unusual for a 3PL and worth asking about if you are considering outsourcing consumer support alongside fulfillment |
| Technology | They describe an enterprise class warehouse system without naming a vendor, plus in house order and transport management, voice picking, and their own reporting platform |
| Apparel handling | They publish an apparel and footwear page covering picking, packing, returns and slotting. Garment on hanger, poly bagging, ticketing, steaming and pressing are not published |
| Affiliations | Sedex, WERC, the Southeastern Warehouse Association, and founding membership of PDMI. No SOC, ISO, C-TPAT or FDA certification is published |
| Not published | Staff count, client count, named carriers and named retailer clients |
A naming note, because the term is crowded. This is a2b Fulfillment in Georgia. It is unrelated to A2B Australia, the transport and payments business, to A2B Tracking Solutions in defense, and to the European A2B freight operators.
No apparel finishing is published. If your product ships on hangers, or needs retailer ticketing, steaming or pressing done at the warehouse, ask directly rather than assuming. Their apparel page covers picking, packing and returns, not finishing. Our Jet Distribution page covers a warehouse that publishes the finishing work.
Clean your UPCs first. Matching is UPC based, so duplicates and missing codes become exceptions on day one. This is the single most useful thing you can do before implementation starts.
No formal certifications are published. They list memberships and affiliations rather than SOC, ISO, C-TPAT or FDA registration. If your retailers or your category require a specific certification, confirm it in writing rather than inferring it from membership logos.
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 is live in both directions: catalog, ship orders and inbound advice going out, and receipts, shipment confirmations, inventory adjustments and inventory snapshots coming back. The file transfer is hosted by AIMS360, so there is no server for your team to run, and matching between the two systems is UPC based.
Not on this connection. AIMS360 hosts the file transfer, which removes the credentials, certificates, monitoring and access reviews that come with running your own, and removes a third party from the chain when a file does not arrive. It is worth asking every ERP and every warehouse who hosts the transfer and who is called when it fails, because the answer is often a managed file transfer subscription nobody mentioned during the demo.
It means the UPC is the key that ties an item in AIMS360 to the same item at the warehouse, on every document in both directions. It is clean, because it is one field rather than a style, color and size combination, and it is the same code the scanner reads in the building. The trade is that it is unforgiving. A style with no UPC cannot be matched at all, and two items sharing a UPC will match to whichever the system finds first, which does not error, it just ships the wrong goods. Run a duplicate and missing UPC check before implementation starts.
Keep it in the ERP in almost every case. Retailer documents are tied to the order book, the invoice and the customer record, which all live in AIMS360, so splitting them means the advance ship notice is produced by a party that does not hold the invoice and a routing guide change has to reach two organizations. a2b publishes retailer EDI capability of its own, so you have a real choice here rather than a default. If you do leave it with the warehouse, name the owner of routing guide updates and chargeback liability in the contract.
Yes, and you should think of it that way from the start. a2b publishes four buildings in Georgia, Utah, Pennsylvania and South Carolina. In AIMS360 each is its own warehouse on the same stock record, so inventory templates decide what each can sell and routing decides where an order ships from. That is what stops a Utah order being promised against Georgia stock because the two were added together into a single number.
They do not publish either. Their apparel and footwear page covers picking, packing, returns and slotting, but garment on hanger, poly bagging, ticketing, steaming and pressing do not appear on their site. If your product needs finishing at the warehouse, ask them directly rather than assuming, or look at a warehouse that publishes that work explicitly.
Before anything else, we will run a duplicate and missing UPC check against your catalog and show you what would have failed on day one. It is the cheapest hour in any warehouse implementation.
