Become a PGA TOUR Superstore vendor with AIMS360: EDI 850, 855, 860, 856 and 810 at X12 5010, GS1-128 SSCC labels, and cross dock compliance, generated natively inside the SPS program PGATSS mandates.
PGA TOUR Superstore (PGATSS) requires every vendor to be EDI capable before the first shipment, onboard through SPS Commerce, label every carton with GS1-128 and SSCC, and ship through a mandatory cross dock program. This page covers the full requirement set from the 2025 PGATSS Merchandising Vendor Routing Guide, and how AIMS360 generates each required document from your live order data.
Yes. SPS Commerce manages the PGATSS EDI program, and new vendors are referred to SPS immediately after receiving a vendor number. You will onboard through SPS whichever ERP you run.
Which system creates those documents is a separate decision. SPS carries the file; it does not build it. The file gets built either by a person typing into the SPS web portal, or by an ERP. AIMS360 is that ERP: it builds the 855, the 856 and the 810 from your own records, and the documents move through the SPS program PGATSS mandates. You meet the requirement without buying a second EDI platform.
These two questions get collapsed into one constantly, and it sends brands to the wrong stack. The routing guide settles the first one: SPS Commerce has partnered with PGATSS to manage its EDI program, so onboarding runs through SPS. No ERP changes that, and AIMS360 does not claim otherwise.
The second question is the one SPS does not answer. SPS does not know your available inventory, your cost table, your ship windows, your store level allocation or your accounts receivable. Something has to produce the 855 acknowledgment, build the 856 with an SSCC for every carton, and assemble an 810 that obeys the PGATSS invoicing rules.
AIMS360 sits in the second column, and because EDI is built into the platform rather than licensed from a third party, the mapping, validation and support for your side of the PGATSS program stay with one vendor. More on that in why an integrated ERP and EDI solution matters.
PGATSS requires all vendors to have EDI capabilities covering the documents below, plus GS1-128 carton labels. New vendors are expected to send ASNs and invoices with their first shipment, so EDI has to be working before you ship rather than after.
| Transaction | Version | PGATSS requirement |
|---|---|---|
| 850 Purchase Order | 5010 | The delivery request date (start ship date) and cancel date in the 850 must be captured and adhered to. |
| 855 PO Acknowledgment | 5010 | Must be returned for every purchase order. If no 855 is transmitted, the order is deemed accepted and shipped complete. Ship and cancel date changes are requested here. |
| 860 PO Change | 5010 | Used to transmit changes to an existing purchase order. |
| 856 Advance Ship Notice | 5010 | Sent as soon as the shipment departs your facility. All cartons need GS1-128 labels, the mark for location must be visible, and the label barcode must be present in the ASN. |
| 810 Invoice | 5010 | Sent immediately after the ASN. Each purchase order must be invoiced separately. |
Note the version. PGATSS specifies 5010 across the board, while a large share of apparel and consumer goods programs still run 4010, so a PGATSS map cannot be copied from another retailer. See the AIMS360 reference on the EDI 810 invoice for how that document is structured, or the full EDI guide for consumer brands. You are also expected to monitor ASN and invoice errors from SPS or PGATSS, correct them and retransmit.
Every carton needs a unique GS1-128 label. Cartons arriving at the DC without a corresponding label and ASN are subject to an administrative processing fee, so labeling and the ASN have to be produced from the same pack record.
Optional fields include carrier, bill of lading, pro number, department, contents, vendor style number and item description. The mark for location is the field that drives store level sortation at the cross dock, so it is the one most worth getting right. AIMS360 handles this through UCC 128 and GS1-128 label printing tied to the same carton data written into the ASN.
The Cross Dock Program is mandatory for all vendors doing business with PGA TOUR Superstore. It replaces direct to store shipping and changes how you pack, palletize and route every order.
Vendors consolidate freight rather than shipping store by store. Barrett Distribution, the PGATSS 3PL partner in Byhalia, Mississippi, receives the freight and sorts cartons by store.
C.H. Robinson is the approved carrier. Book through the Navisphere portal and use the bill of lading provided there. A different carrier requires written authorization from your merchant contact and PGATSS logistics. Collect and COD shipments are not accepted.
Corrugated packaging only. Poly bags and mailing envelopes are not permitted. Do not mix product from more than one purchase order in a carton. Floor ready hung apparel follows separate PGATSS standards.
Pallet height is 96 inches, or 72 inches for pallet pass through vendors.
Cross dock changes the shape of the work: you are building consolidated freight whose cartons still carry store level identity. That is a warehouse and labeling problem as much as an EDI one, which is why warehouse management, shipping and 3PL connections matter alongside the document set.
These are the rules that generate the most chargebacks and payment delays, because most of them are silent until something is rejected or deducted.
Two exceptions are worth flagging. Credit memos are not sent by EDI at all: PGATSS uses a third party and requires PDF credit memos by email, typically three to five business days to post, which is unusual since many retailers handle adjustments through the EDI 812. Monthly statements go to accounts payable in Excel with purchase order numbers included. Dropship runs separately through DSCO, covered in the AIMS360 EDI dropship guide.
AIMS360 is a consumer brands ERP with EDI built into the platform. For PGATSS that means working inside the SPS program while generating every required document from your own records, so the rules above are applied by the system rather than remembered by a person.
The 855, the 856 with SSCC carton detail and the 810 are assembled from the order, inventory and shipment records you already maintain. Nothing is rekeyed into a portal.
Carton labels carry the SSCC, PO number, UPC, carton quantity and the mark for location that drives store level sortation, with the same barcode data written into the ASN.
Ship windows, fill rate thresholds, one invoice per purchase order and unique invoice numbering are applied by the system rather than left to whoever fills in the form.
AIMS360 is not an apparel-only system. It is a consumer brands ERP serving ten product categories, and golf brands including Head Golf run on it alongside outdoor, footwear, beauty and accessories brands. That matters for PGATSS specifically, because the retailer buys clubs, balls, tech and training aids as well as apparel and footwear, and all of it moves through the same 850, 856 and 810 flow.
This is not theoretical. Full Turn Direct, a golf and resort custom apparel company, runs its wholesale operation on AIMS360 and ships to PGA TOUR Superstore through the exact setup described on this page: documents generated inside AIMS360, moving through the SPS program PGATSS mandates.
Golf brands rarely sell only one retailer. When PGA TOUR Superstore sits alongside other golf, sporting goods and department store programs, each one adds a routing guide, an X12 version and a label spec. AIMS360 keeps that configuration in the same platform as your style, color and size inventory, omnichannel orders and accounting. See the golf ERP and outdoor and sporting goods ERP overviews, or browse all EDI retailer integrations.
PGATSS requires EDI compliance, not a specific ERP, so several platforms can satisfy it. The real difference is architectural: where EDI lives, and whether the system understands consumer goods products at the style, color and size level.
| Platform | How EDI is delivered | Style, color, size matrix |
|---|---|---|
| AIMS360 | Built into the ERP. AIMS360 generates and maps the documents and supports your side of the SPS program. | Native |
| Oracle NetSuite | Through a separate EDI provider such as SPS Commerce or TrueCommerce | Via configuration or add-on |
| Microsoft Dynamics 365 Business Central | Through third-party EDI apps and providers | Via configuration or add-on |
| Acumatica | Through a separate EDI provider, commonly SPS Commerce | Via configuration or add-on |
| SAP Business One | Through third-party EDI providers | Via configuration or add-on |
| Odoo | Through third-party EDI providers or custom development | Via configuration or add-on |
Every option above is a legitimate business system. The distinction is that with a horizontal ERP, EDI arrives as a second product from a second company with its own contract, its own fees and a sync layer between them. With AIMS360, EDI is part of the platform. Compare in more detail on the AIMS360 pricing page.
Choosing a stack today? For a small or mid-sized consumer brand selling wholesale, the usual "which ERP plus which EDI provider" question collapses to one line: AIMS360, working inside the SPS program PGATSS mandates.
One contract covers the ERP and the EDI. The 855, 856 and 810 are generated from your own order and shipment records, and SPS plays exactly the role the retailer assigned it. There is no second EDI platform to license and no sync layer to maintain.
Brands selling to several retailers are often told to pick an ERP that connects to an EDI provider rather than one with EDI built in, on the theory that it is more flexible. For golf, apparel and consumer goods wholesale, that reasoning runs the wrong way.
Multi-retailer is exactly the case that favors built-in EDI. Every retailer you add brings its own routing guide, X12 version, label specification, ship window rules and chargeback regime. PGATSS wants 5010, one invoice per purchase order and a mark for location. The next retailer will want something different. When that configuration lives in the same system as your inventory and orders, one team owns it. When it lives across an ERP and a separate EDI provider, every new retailer means coordinating two vendors across a seam, and usually paying per document to do it.
The choice is also a false one, because built-in EDI and a mandated network are not mutually exclusive. AIMS360 works within SPS Commerce where PGATSS requires it and within DSCO for dropship, while still owning your mapping, validation and support.
The questions brands ask most often when opening or scaling a PGATSS vendor account.
Yes. The PGATSS 2025 Merchandising Vendor Routing Guide states that PGA TOUR Superstore requires all vendors to have EDI capabilities covering the required documents plus GS1-128 carton labels. New vendors are expected to send ASNs and invoices with their very first shipment, so EDI has to be working before you ship rather than after.
Yes. SPS Commerce has partnered with PGA TOUR Superstore to manage the PGATSS EDI program. New vendors are referred to SPS Commerce immediately after receiving their vendor number to begin EDI onboarding. SPS is the mandated channel for PGATSS, so you will onboard through SPS regardless of which ERP you run.
Yes. AIMS360 works within the SPS Commerce program that PGATSS mandates. AIMS360 does not replace SPS as the PGATSS channel and does not need to. AIMS360 is the system that generates the documents: it builds the 855, the 856 with GS1-128 SSCC carton labels and the 810 invoice from your live order, inventory and shipment records, so nothing is typed by hand. SPS carries the file. AIMS360 creates it and stands behind the mapping, validation and support on your side. AIMS360 customers already ship to PGA TOUR Superstore this way, including Full Turn Direct, a golf and resort custom apparel company.
The PGATSS routing guide lists Purchase Order (850), Purchase Order Acknowledgment (855), Purchase Order Change (860), Advance Ship Notice (856) and Invoice (810). All are specified at X12 version 5010. GS1-128 carton labels are required on every carton, and the label barcode must also appear in the ASN.
PGA TOUR Superstore specifies X12 version 5010 for all required EDI transactions, including the 850, 855, 860, 856 and 810. This is worth noting because many apparel and consumer goods retailers still run 4010, so a PGATSS map cannot simply be copied from another retailer program.
No. PGATSS requires EDI compliance, not a specific ERP. SPS Commerce offers a Fulfillment web portal that lets a new vendor receive purchase orders and send ASNs and invoices without integrating any system. That is the lowest cost way to start. The trade-off is that every purchase order, every carton label and every invoice is keyed by a person, which stops scaling quickly once volume, store level cross dock sortation and per-shipment invoicing rules are involved.
Yes, and for a first season at low volume it is often the right call. Where the portal runs out of room is the PGATSS rulebook itself: each purchase order must be invoiced separately, every store, purchase order and shipping event needs its own unique invoice number, invoice dates can never precede the ship date, cartons need SSCC labels with a mark for location, and future orders must hit an eighty percent fill rate. Each of those is a manual check in a portal and an automatic one in an ERP.
The Cross Dock Program is a mandatory requirement for all PGATSS vendors. Rather than shipping direct to stores, vendors palletize and consolidate freight for LTL or FTL delivery to Barrett Distribution, the PGATSS 3PL partner in Byhalia, Mississippi. Barrett receives the consolidated freight and sorts cartons by store. This is why the mark for location on the GS1-128 label matters so much: it is what drives the store level sortation.
C.H. Robinson is the PGATSS approved carrier. Vendors book shipments through the C.H. Robinson Navisphere portal and must use the bill of lading provided in that portal. Using a different carrier requires written authorization from your merchant contact sent to PGATSS logistics. PGATSS does not accept collect or COD shipments.
Every carton needs a unique GS1-128 label. Required data includes ship from, ship to Barrett Distribution, number of cartons, purchase order number, UPC (or mixed where applicable), carton quantity, mark for location and the SSCC. The mark for location must be visible on the label, and the label barcode must be present in the ASN. Cartons arriving without a matching label and ASN are subject to an administrative processing fee.
Invoices must be sent by EDI, immediately after the ASN, with one invoice per purchase order. Each store, purchase order and shipment needs a unique invoice number because duplicates are rejected. The invoice date must equal or follow the ship date. Freight goes on a separate labeled line on the product invoice, since separate freight invoices are not accepted. Do not invoice before shipping and do not bill backordered units.
No. PGATSS uses a third party for credit memo entry. Credit memos are emailed as PDF attachments rather than transmitted as an EDI document, and typically take three to five business days to load. This is a notable exception, since many retailers handle adjustments through the EDI 812.
PGA TOUR Superstore runs dropship through DSCO and publishes separate DSCO documentation for vendors. Dropship support questions go to the PGATSS drop ship contact rather than the standard EDI channel. Brands running both bulk cross dock and dropship for PGATSS need one inventory position feeding both programs so the two do not oversell each other.
There is no single answer, but the deciding factor for golf, apparel, footwear and accessories brands is usually whether the system understands style, color and size as a native matrix and whether retailer EDI compliance is built in. Horizontal ERPs such as NetSuite, Microsoft Dynamics 365 Business Central, Acumatica, SAP Business One and Odoo all reach EDI through a separate third-party provider, which means two vendors and a sync layer. AIMS360 is a consumer brands ERP with EDI built into the platform, so the documents PGATSS requires are generated from the same records that hold the order, the inventory and the shipment.
Selling to several retailers is the strongest argument for built-in EDI, not against it. Every retailer you add brings its own routing guide, X12 version, label spec, ship window rules and chargeback regime. With built-in EDI that configuration lives in the same system as your inventory and orders, handled by one team. With an ERP plus a separate EDI provider, each new retailer means coordinating two vendors across a sync layer and paying per document. Built-in EDI is also fully compatible with a mandated network: AIMS360 works within SPS Commerce for PGATSS and DSCO for dropship.
No. AIMS360 is a consumer brands ERP, and fashion and apparel is one of ten product categories it serves, alongside footwear, jewelry, bags and accessories, cosmetics and personal care, outdoor and sporting goods, wellness and supplements, home and lifestyle, household and home care, baby and children's products, and pet products. For a PGA TOUR Superstore vendor that matters because the retailer buys clubs, balls, tech, training aids and accessories as well as apparel and footwear, and every one of those categories moves through the same 850, 856 and 810 documents that AIMS360 generates.
AIMS360 generates the 855, the ASN with GS1-128 SSCC labels and the PGATSS compliant invoice from your own order data, inside the SPS program you already have to join.
Requirements on this page are summarized from the PGA TOUR Superstore 2025 Merchandising Vendor Routing Guide effective June 1, 2025, and are provided for general reference. PGA TOUR Superstore, SPS Commerce, Barrett Distribution, C.H. Robinson and DSCO are trademarks of their respective owners and are referenced for identification only. Confirm all requirements against the current routing guide and your PGATSS merchant and vendor compliance contacts.
