Gordon Food Service is North America's largest family-operated broadline distributor — a Michigan-based operation supplying restaurants, schools, and healthcare kitchens across the eastern half of the US and Canada, plus its own GFS retail stores. For a food manufacturer, Gordon Food Service is a classic foodservice DC relationship: high-frequency replenishment, exacting item data, and an EDI chain that runs the whole rhythm.
The document set
GFS trades the standard distributor chain over direct SFTP (not AS2 — GFS's vendor EDI runs on a dedicated SFTP exchange, assigned per-vendor account credentials, not the AS2 handshake used by many retailers):
- 850 Purchase Order in — DC replenishment orders, often frequent and time-sensitive; foodservice runs leaner DC inventory than retail, so PO turnaround expectations are short.
- 855 Purchase Order Acknowledgment out — GFS's program confirms the PO itself, not just a 997 functional receipt.
- 856 Advance Ship Notice out — announcing inbound freight before arrival, hierarchy matching the physical pallet build, SSCC-18 serials in MAN segments matching the GS1-128 labels.
- 810 Invoice out — matched against PO and receipt; bracket pricing and deal-sheet references must be exact.
- 832 Price/Sales Catalog where the program calls for electronic item and price publication (confirm whether your program uses it — it isn't part of GFS's core four).
- 997 both directions, automatic.
As with all distributor programs, the exact required set varies by category and division — confirm in the onboarding packet, and treat the current routing guide as the authority where anything here differs.
Foodservice item data: the hidden requirement
Distributors sell your product sight-unseen from your data, which promotes the item master from housekeeping to commercial infrastructure. GFS expects pack-level GTINs, accurate case and pallet configuration, net and gross weights, storage class, and shelf life — consistent across catalog, order, ASN, and invoice. Two foodservice-specific wrinkles deserve attention:
- Catch weights. Proteins, cheese, and other variable-weight items bill by actual delivered weight, not fixed case price. The ASN and invoice carry actual weights per unit; the conventions are well-trodden but partner-specific, and our catch-weight EDI guide covers the mechanics.
- Shelf life at receipt. Foodservice DCs enforce minimum remaining shelf life on inbound product. That's an operational rotation discipline, but your ASN's date data has to be accurate for receiving to go smoothly.
When invoices dispute at a foodservice distributor, the root cause is nearly always item or price data drift, not document syntax. Clean master data buys you a clean match rate.
Receiving compliance
The DC pattern is the familiar one: announce before arrival, label to GS1-128 with SSCC-18, hit the appointment. The design rules that keep you off deduction reports at US Foods and Sysco apply unchanged at GFS — fire the 856 from ship-confirm rather than batch, allocate label and ASN serials from a single source, and validate documents against the companion guide before transmission. Suppliers who serve multiple broadliners should build once and map per partner: one item master, one shipping process, several sets of qualifiers and tests.
Setting up with EDISQ
Gordon Food Service is in the EDISQ partner catalog, connected over the direct SFTP exchange GFS operates for its vendors — we handle the connection, the file handling, and the 997 acknowledgment cadence as part of the service. GS1-128 labels are included free with SSCC-18 allocation shared between the label and the 856 — structural label-ASN parity.
The sequence: GFS assigns a vendor code and a 6-digit account number (request both, along with the EDI onboarding packet, from IT.EDI.US.Customer@gfs.com — Canada: it.edi.canada@gfs.com), item cross-reference loaded (with catch-weight conventions confirmed once the companion guide is in hand), test cycle passed, first orders parallel-run. Pricing follows the standard ladder: first 25 documents monthly free, then per-document from 50¢ tapering with volume, no partner-specific fees on the Self-Serve plan.
FAQ
Which EDI documents does Gordon Food Service use with suppliers?
The standard distributor chain: 850 purchase order in, 856 ASN and 810 invoice out, 997 acknowledgments both directions. Catalog data may flow via the 832. Confirm your program's exact set in the onboarding materials GFS provides.
Is Gordon Food Service the same as GFS Marketplace stores?
GFS runs both broadline distribution to foodservice operators and its retail store network. Suppliers serve both through the same distribution relationship — one item master, one EDI setup, confirmed at onboarding.
Does GFS handle catch-weight products via EDI?
Foodservice distributors trade catch-weight items routinely — proteins and cheese billed by actual weight. The 856 and 810 carry actual weights per shipping unit; confirm the specific segment conventions in the companion guide.
How long does GFS EDI onboarding take?
Days of EDI work with certified maps; the end-to-end calendar depends on GFS vendor setup and test scheduling — typically weeks. Confirm dates with your onboarding contact.