A hardware co-op order looks like a contradiction: one buyer, one purchase order, and quantities destined for hundreds of independently owned storefronts. That structure — central buying for a member network — shapes every document in the flow. Ace Hardware buys centrally for thousands of independent stores; Do it Best aggregates member-store demand into its warehouse orders. Understanding how the aggregation works is most of what co-op EDI compliance means.
One PO line, many stores
Co-op 850 purchase orders lean heavily on SDQ segments: a single line item whose quantity is split across member stores and retail support centers (RSCs). Ace orders fan out to member stores and RSCs through SDQ detail; Do it Best warehouse orders carry the member-store split the same way. Your side of the contract is the explosion — unpacking each SDQ into real store-level allocations before anything gets picked. A system that reads only the line total will ship the right quantity to the wrong granularity.
Item identity is the second gate. Ace lines pair the Ace article number with the UPC, and a product cannot be ordered until it clears Ace's item setup. At Do it Best, your item numbers must match the current member catalog, or the invoice mismatches later. In both cases the cross-reference table is doing constant work.
The 832 carries the pricing truth
Co-ops run on the 832 Price/Sales Catalog more than almost any other retail channel. At Ace, the catalog feeds the retail support centers and member pricing, and there's a sequencing rule with teeth: publish catalog updates before they appear on any 810 invoice. Pack and inner-pack definitions in the 832 also determine how RSC orders break down, so an imprecise pack definition doesn't just misprice — it mis-ships.
The operational habit that keeps co-op relationships clean is treating the 832 as a living feed from your item master, not an annual project. Price change coming? Catalog first, invoice second, every time.
Cycles, ship windows, and the invoice match
Co-op warehouses order on cycles. Do it Best requested-ship dates follow its warehouse ordering calendar, and the penalty for missing a cycle is structural: you wait for the next one. DTM dates on co-op POs deserve the same respect a big-box ship window gets.
On the outbound side, Ace expects the 856 ASN before the RSC appointment, with an order→pack→item hierarchy — and mixed-SKU cartons get flagged at receiving. Then the invoice: Do it Best reconciles your 810 against the 856 as shipped before billing its members, so invoice lines must mirror the ship notice, not the order. The co-op is effectively auditing on behalf of its membership, which is why accuracy standards feel closer to a wholesaler's than a single chain's.
Setting up for the co-op channel
The hardware channel rarely stops at one partner — suppliers who crack a co-op often sell Menards and Tractor Supply too, and the same SDQ-and-catalog machinery carries over with partner-specific rules layered on top. EDISQ ships certified maps for each, with SDQ explosion, item cross-referencing, and catalog publication handled by the connector. The Ace Hardware requirements post covers that program's specifics document by document.
Cost-wise, the co-op channel fits a metered model naturally: catalog updates, cycle orders, ASNs, and invoices each count as one document against a ladder that begins after 25 free documents a month — $0.50 at the entry tier, easing to $0.10 at the top, billed on the marginal-bracket principle. EDISQ layers no mapping or setup cost on top and includes AS2, SFTP, and VAN connectivity; live trading runs on a $100/month Production minimum applied in full to usage, first live partner included. See pricing for the tier table.
FAQ
What is an SDQ segment?
A store-distribution segment on a PO line: one line item with quantities fanned across many destinations. Co-op orders use SDQ to carry member-store splits, and your system must explode them before allocation and picking.
Why is the 832 so important to co-ops?
The catalog feeds the co-op's support centers and member pricing. At Ace, updates must publish before they appear on any invoice, and pack definitions in the 832 drive how warehouse orders break down.
How is co-op EDI different from selling to a chain?
A co-op buys centrally on behalf of thousands of independently owned stores. Orders aggregate member demand with SDQ detail, warehouse cycles set the calendar, and the co-op reconciles your invoice before billing its members.