US Foods is one of the two national giants of American foodservice distribution, delivering to hundreds of thousands of restaurants, healthcare kitchens, and institutions from a network of distribution centers. For a food manufacturer, getting on the truck means becoming a compliant DC supplier — and US Foods runs that relationship on EDI.
The document set
US Foods trades the standard distributor chain over AS2:
- 850 Purchase Order in — DC-level replenishment orders, often high-frequency. PO numbers and buyer references must round-trip exactly on everything downstream.
- 856 Advance Ship Notice out — announcing the inbound shipment before it reaches the DC, with hierarchy and GS1-128/SSCC-18 serials matching the physical pallets and cases.
- 810 Invoice out — matched against the PO and the receipt. Price discrepancies against the agreed bracket or deal sheet are the classic short-pay trigger.
- 832 Price/Sales Catalog — item and price data published electronically. Foodservice runs on the 832 more than retail does; distributors sell from your data, so its accuracy is commercial, not just technical.
- 997 both directions, automatic.
Program details vary by category and division — confirm your exact required set and any additional documents in the onboarding packet US Foods issues.
Item data is the real requirement
Foodservice distribution amplifies a truth that retail lets you get away with: the item master is the product. US Foods sells your product to operators through its catalog, so pack-level GTINs, case counts, cube and weight, shelf life, and storage class all have to be right — and consistent across the 832, the 850 you accept, and the 810 you bill. Catch-weight items (proteins, cheese) add the wrinkle of billing by actual delivered weight rather than fixed case price; if that's your category, our catch-weight EDI guide covers how the documents carry it.
A practical rule: when an invoice disputes at a foodservice distributor, the root cause is usually item or price data that drifted between systems, not the invoice logic itself. Fix the master data once and the match rate follows.
Receiving compliance
DC receiving expects freight to be announced and labeled: the 856 transmitted before arrival, pallets and cases carrying GS1-128 labels whose SSCC-18 serials match the ASN's MAN segments. Appointment scheduling, pallet configuration, and date-code rules (foodservice DCs enforce minimum remaining shelf life on receipt) live in the routing guide — treat that document as binding and confirm the current version at onboarding, because specifics change and vary by facility.
The failure pattern to design against is the same as retail: ASNs generated by batch after the truck leaves, or labels printed from a different system than the ASN. Generate the 856 from ship-confirm, and allocate label and ASN serials from one source.
US Foods next to Sysco
Most food brands that supply US Foods also supply Sysco — the document chains are near-identical, and the differences live in companion-guide details: qualifiers, item-data expectations, division structures. Set them up on shared item cross-reference data and treat each as its own partner for testing. The same applies to regional players like Gordon Food Service. One clean item master, several sets of maps.
The path with EDISQ
US Foods is in EDISQ's partner network with certified maps: connectivity operated for you, 997s automatic, GS1-128 labels included with SSCC allocation shared between label and ASN, and validation against the companion guide before anything transmits. Pricing is per document — first 25 monthly free, then from 50¢ tapering with volume — with no setup or mapping fees. The realistic sequence: confirm your vendor number and onboarding packet with US Foods, load your item cross-reference, pass the test cycle, and parallel-run the first orders.
FAQ
Which EDI documents does US Foods use with suppliers?
The core chain: 850 purchase order in, 856 ASN and 810 invoice out, 997 acknowledgments both directions. Catalog and price data flows via the 832. Confirm the exact set for your program in your onboarding packet.
Does US Foods require ASNs?
Inbound freight to distribution centers is expected to be announced with an 856 before arrival, with GS1-128 pallet and case labeling. Verify the current labeling and timing rules in the routing guide you receive at onboarding.
What item data does US Foods expect?
Foodservice distributors run on rich item content — GTINs at each pack level, case and pallet configurations, catch weights where relevant, and accurate net/gross weights. Clean 832 catalog data prevents most downstream order and invoice mismatches.
How long does US Foods EDI onboarding take?
The EDI mapping and testing side typically takes days with certified maps. The overall calendar depends on US Foods' supplier setup and testing queue — plan weeks end to end and confirm dates with your onboarding contact.