When a retailer runs its vendor program on SPS Commerce, AIMS360 connects to SPS for that retailer and your team keeps working inside AIMS360.
EDI network · SPS Commerce
AIMS360 is a consumer brands ERP with native EDI to 350+ retailers, and most of them connect to AIMS360 directly. A handful run their vendor programs on the SPS Commerce network. For those retailers AIMS360 connects to SPS: purchase orders land in AIMS360 as orders, and acknowledgments, ship notices, carton labels and invoices go back out from the same records. The connection is managed by our EDI team.
Does AIMS360 integrate with SPS Commerce? Yes. When a retailer runs its vendor program on the SPS Commerce network, AIMS360 connects to SPS for that retailer, and your team keeps working inside AIMS360. Orders, ship notices, labels and invoices come from the same AIMS360 records as every other retailer, and retailers that are not on SPS connect through AIMS360's native EDI.
How it works
SPS is the network the retailer chose. AIMS360 is where the order, the inventory and the shipment live.
| Step | What happens in AIMS360 |
|---|---|
| Purchase order in | The retailer sends its 850 purchase order over the SPS network, and it lands in AIMS360 as a sales order with the store, distribution center, ship window and cancel date on it. An 860 change updates the same order. |
| Acknowledgment | The 855 goes back from the order record, so what you confirm is what you can ship. |
| Allocate and pick | Stock is allocated and picked in AIMS360's warehouse management, or released to your 3PL, against one inventory record shared with every other channel. |
| Labels and ASN | Carton labels print from the packing, UCC-128 with the SSCC-18 for most programs and Interleaved 2 of 5 where the retailer asks for it, and the 856 ship notice is built from the same cartons. |
| Invoice | The 810 is generated from the shipment, so quantities and prices match the ship notice and the PO. |
| Adjustments | 812 credits and debits, 864 text messages and 852 product activity post in AIMS360, where your team can see them and work chargebacks. |
| Acknowledgments | 997s go both ways on every document. |
Retailers on SPS
These are the retailer programs AIMS360 documents as running on SPS. Each has its own page with the full requirements.
| Retailer | What runs over SPS | The detail vendors miss |
|---|---|---|
| Dollar Tree | Merchandise EDI: 850 in; 855, 856 and 810 out; 812 and 864 posted | The 16 digit PO number has to survive to the invoice, and cartons carry Interleaved 2 of 5 labels. |
| Family Dollar | Supplier onboarding and EDI: 850 and 860 in; 855, 856 and 810 out; 812, 864 and 852 posted | Its own company since July 2025, with your vendor number where the map expects it. |
| Scheels | The vendor program: 850 and 860 in; 855, 856 and 810 out; 812 posted | One PO per carton, UCC-128 labels with the SSCC-18, and scheels.com drop ship from the same shipment record. |
| PacSun | 850 in; 856 and 810 out | Orders arrive in GTIN-14, converted to your UPC, and every ship notice needs the PRO number, SCAC and transport code. One DC, in Groveport, Ohio. |
| Academy Sports + Outdoors | Vendor EDI onboarding and certification | New vendors are referred to SPS after receiving a vendor number. Whether SPS is also the production network for every vendor is not published, so get it in writing. |
| Urban Outfitters and Anthropologie | Bulk wholesale EDI, with the Tradestone portal alongside | Dropship runs on Rithum-DSCO and the marketplace on Mirakl. AIMS360 runs all three from one stock record. |
Retailers change networks. Check the onboarding packet you receive with your vendor number, and see every retailer AIMS360 trades EDI with.
Documents
Which documents a program uses, and the version and segment rules inside them, come from that retailer's SPS program.
| Document | Direction | What it does |
|---|---|---|
| 850 purchase order | In | The order, with ship-to stores or DC, ship window and cancel date. |
| 860 PO change | In | Quantity, date or line changes applied to the existing order. |
| 855 acknowledgment | Out | Confirms what you will ship against the PO. |
| 856 ship notice | Out | Carton-level detail matching the labels on the boxes. |
| 810 invoice | Out | Billed from the shipment, matching the ship notice and the PO. |
| 812 credit and debit | In | Deductions and adjustments posted against the invoice. |
| 864 text message | In | Rejections and notices from the retailer. |
| 852 product activity | In | Sales and inventory data where the program sends it. |
| 997 acknowledgment | Both | Confirms each document was received. |
The honest answer
For a retailer that runs its program on SPS, the retailer decides that, not your ERP. Onboarding and certification for those programs go through SPS, and any SPS account, testing or fees are between you and SPS under SPS's own terms. No ERP vendor can remove that step, and AIMS360 does not claim to.
What AIMS360 changes is everything around it: which system builds the documents, holds the carton data and prints the labels. On AIMS360 that is the ERP your team already works in, with no connector to maintain between an ERP and a separate EDI subscription, and no per-transaction EDI fees from AIMS360.
Certification through SPS as the program requires. Orders, labels, ship notices and invoices are built in AIMS360 and exchanged over the SPS network.
AIMS360 connects the retailer through its native EDI, with retailer-specific maps, chargeback management and 24x7 emergency EDI support.
If you are weighing SPS as your EDI provider for all of your retailers, the full comparison is on AIMS360 vs SPS Commerce.
Getting live
Six steps from vendor number to live orders.
The retailer sets you up as a vendor and points you to its SPS program. Share the onboarding packet with AIMS360 so the setup starts from the retailer's own requirements.
Registration, testing and certification follow the retailer's SPS requirements. That step belongs to the retailer's program, whichever ERP you use.
The AIMS360 EDI team configures the documents and segment rules the program uses against your customers, styles, UPCs and ship-to locations.
Carton label format and pack rules from the retailer's guide are set on the customer, so the label and the ship notice come from the same carton.
Test purchase orders run through AIMS360, and the acknowledgments, labels, ship notices and invoices they produce are checked against the program before live orders arrive.
Live orders flow into AIMS360, the EDI team keeps the connection current, and 24x7 emergency EDI support covers critical issues.
Already on SPS
Many brands put every retailer on SPS because their previous ERP had no EDI of its own. On AIMS360 that changes. Retailers that run their programs on SPS stay connected through SPS, and every other retailer can move to AIMS360's native EDI, so the SPS relationship covers only the programs that require it.
The move is planned retailer by retailer, so nothing is cut over blind. The switching steps are on AIMS360 vs SPS Commerce.
FAQ
Yes. When a retailer runs its vendor program on the SPS Commerce network, AIMS360 connects to SPS for that retailer and your team keeps working inside AIMS360. Purchase orders land as orders, and acknowledgments, ship notices, carton labels and invoices go back out from the same AIMS360 records. The connection is managed by the AIMS360 EDI team.
AIMS360 EDI is built in-house and native to the ERP. It connects 350+ retailers with retailer-specific maps, chargeback management, UCC-128 labels and 24x7 emergency EDI support, with no per-transaction EDI fees. Those retailers do not need SPS or any other EDI provider.
The retailer programs AIMS360 documents as running on SPS are Dollar Tree, Family Dollar, Scheels, PacSun, Academy Sports + Outdoors for onboarding and certification, and the bulk wholesale program at Urban Outfitters and Anthropologie. Retailers change networks, so confirm in the onboarding packet that comes with your vendor number.
The retailer's program decides that. Onboarding and certification for those programs go through SPS, and any SPS account, testing or fees are between you and SPS under SPS's own terms. What AIMS360 changes is which system builds the documents, holds the carton data and prints the labels.
It depends on the program. The 850 purchase order and 860 change come in; the 855 acknowledgment, 856 ship notice and 810 invoice go out; 812 adjustments, 864 text messages and 852 product activity are posted in AIMS360; and 997 acknowledgments go both ways, with carton labels printed from the same packing as the ship notice.
No. Orders, labels, ship notices and invoices are handled in AIMS360, the same way as every other retailer. Onboarding and certification steps set by the retailer's SPS program may involve SPS directly.
Some retailer programs offer SPS's Fulfillment web portal to vendors who want to receive orders and send ship notices and invoices without integrating anything. It works at low volume, but every order is keyed twice, once in the portal and once in your own system. With AIMS360 connected, the documents come from the records your team already keeps.
Yes. Retailers that run their programs on SPS stay on SPS, and every other retailer runs on AIMS360's native EDI, all from one stock record and one set of customer records.
No. AIMS360 has no per-transaction, per-document or VAN fees on its side. Any charges from SPS for a retailer's program are set by SPS under its own terms.
AIMS360 provides 24x7 emergency EDI support with about a one hour average resolution on critical items, whichever network the retailer uses.
