EDI Requirements

Publix EDI Requirements

Publix is a Southeast grocery chain, and its EDI reflects grocery-industry roots: it runs the UCS grocery transaction sets (875 Grocery PO, 880 Grocery Invoice) in addition to standard X12 850/810, on ANSI X12. EDI is mandatory for product suppliers, with Direct Store Delivery (DSD) and import as separate supplier programs, and the Business Connection portal handling application, setup, and day-to-day compliance visibility. Which document flavor you use — grocery 875/880 vs. 850/810 — depends on the program you’re set up under, so confirm it during onboarding.

Required EDI documents

Document	Name	Notes
EDI 875	Grocery Products Purchase Order	grocery UCS variant of the 850; usage depends on program — confirm
EDI 880	Grocery Products Invoice	grocery UCS variant of the 810; usage depends on program — confirm
EDI 850	Purchase Order	X12 PO where the grocery 875 isn’t used
EDI 810	Invoice	X12 invoice where the grocery 880 isn’t used
EDI 856	Advance Ship Notice (ASN)	required for product suppliers; most compliance-sensitive
EDI 855	PO Acknowledgment	reported as used in some programs — confirm in your routing guide
EDI 860	PO Change
EDI 852	Product Activity Data	conditional
EDI 820	Payment Order / Remittance Advice	supporting
EDI 812	Credit/Debit Adjustment	deductions/chargebacks
EDI 894	Delivery/Return Base Record	DSD
EDI 895	Delivery/Return Acknowledgment/Adjustment	DSD
EDI 997	Functional Acknowledgment	reported as required for all transmissions

Labeling & packaging

GS1-128 (UCC-128) case/shipping labels with an SSCC-18 at the pallet level that must exactly match the 856 — standard grocery practice.
Perishable and short-shelf-life goods carry date coding (pack/production, sell-by, or use-by) per Publix’s product and category rules; grocery buyers hold suppliers to date-code and shelf-life minimums on receipt.
GS1-licensed GTIN/UPC required at the item level. Confirm exact label placement, pallet configuration, and date-code format against Publix’s current routing/supplier guide.

Connection & portal

ANSI X12; Publix’s grocery sets (875/880) trace to the UCS (Uniform Communication Standard) grocery subset of X12. EDIFACT and XML syntaxes are also reported as supported.
AS2 or a VAN for connectivity (SPS, Cleo, TrueCommerce and similar can broker it).
Business Connection is the vendor portal for the supplier application, EDI setup/testing, and compliance visibility — the documents still move over EDI.

Onboarding & testing

Publix doesn’t publish a fixed window and it’s largely partner-controlled — plan for roughly 6–12 weeks depending on program and provider. Sequence: apply and provide an EDI contact via Business Connection → choose AS2/VAN + provider → map and certify each transaction set in test → go live. Parallel paper invoicing is reported to run alongside EDI during the testing period at Publix’s discretion.

Compliance & chargebacks

• EDI is mandatory for product suppliers; late shipments, ASN/label errors, and invoice mismatches trigger deductions. Specific penalty amounts are not publicly published — treat any figure as reported and confirm in your vendor agreement.
• Fill-rate / on-time delivery expectations apply as in any grocery program; confirm current thresholds and any OTIF-style measurement against Publix’s routing guide rather than assuming a number.
• The routing/supplier guide (label placement, pallet/carton specs, date coding, appointment and delivery rules) is the source of truth — confirm the current version before shipping.

Worth knowing

• Grocery UCS vs. plain X12: Publix uses the grocery-industry 875/880 in addition to 850/810. Which set applies depends on your program — a real difference from general-merchandise retailers that only use 850/810.
• Distinct supplier programs — product suppliers, Direct Store Delivery (DSD), and import — carry different document sets (DSD adds the 894/895 delivery/return pair). Confirm which applies to you.
• FSMA Section 204 food-traceability adds Key Data Elements for foods on the FDA Food Traceability List — confirm the current federal compliance date and how Publix wants KDEs carried (on the 856 or otherwise).

How EndlessEDI helps with Publix

Publix runs grocery UCS (875/880) next to 850/810 and books deductions on the 812. EndlessEDI maps whichever set your program uses, carries perishable date codes and FSMA 204 KDEs on the 856, and reconciles PO, ASN, and invoice so the 812 has nothing to catch.

Explore EndlessEDI

Publix EDI FAQ

Does Publix use grocery EDI 875/880 or standard 850/810?

Both are in play. Publix is a grocery retailer and supports the UCS grocery transaction sets — 875 (Grocery PO) and 880 (Grocery Invoice) — alongside standard X12 850 and 810. Which set you exchange depends on the supplier program you’re onboarded under, so confirm it during EDI setup via Business Connection.

What is Publix Business Connection?

It’s Publix’s vendor portal — where you apply to become a supplier, provide your EDI contact, run setup and testing, and get compliance visibility. It works alongside EDI rather than replacing it.

Does Publix have EDI chargebacks?

Yes — late shipments, ASN and label errors, and invoice mismatches trigger deductions, typically carried on the 812. Publix doesn’t publish specific penalty amounts, so treat any dollar or percentage figure as reported and confirm the current schedule in your vendor agreement and routing guide.

EDI requirements and penalty schedules change and vary by program. Figures marked “reported” come from third-party sources, not the retailer’s published fee schedule — always confirm against the retailer’s current routing guide and your vendor agreement.