Skip to main content

UNFI EDI: requirements and onboarding

Start UNFI integration with the purchasing entity and supplier policies that govern the order, then connect item, shipment and invoice evidence without mixing U.S., legacy or Canadian program requirements.

Quick answers

Can SignalEDI help me connect to UNFI?
SignalEDI helps prepare mappings, sample validation, and the workflow required for your UNFI program. Scope is confirmed during setup. Production connection requires the applicable partner approval; this guide is not evidence of a live connection or certification.
What determines the UNFI onboarding timeline?
The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule. Agree the schedule after requirements and testing scope are confirmed. This is not a guaranteed go-live date.
Which ERP systems can I use for UNFI?
Start with your existing system, its version, and the records you need to exchange. SignalEDI builds to your trading partner's requirement. Scope is confirmed during setup. Review the integration catalog for the specific connector and workflow before assuming production availability; an ERP name alone does not establish support for every edition or document.
Review integration scope

Plan the integration workflow

SignalEDI provides EDI integration preparation, document validation, and workflow visibility. Confirm connector, document, transport, and approval scope before production.

  1. 1. Your business system

    Identify the source records, system edition, data owner, and allowed access.

  2. 2. SignalEDI preparation

    Map and validate safe samples against the agreed requirements. Review errors and acknowledgements.

  3. 3. Partner testing and approval

    Complete the partner-controlled tests and retain permission before enabling live exchange.

Conceptual workflow only. A diagram or catalog listing does not establish certification or an active production connection.

Build your onboarding checklist

Download the onboarding worksheet (text)

Public sources reviewed 2026-11-09

What the public record confirms

  • UNFI's public purchase terms cover United Natural Foods and subsidiaries including SUPERVALU, while recognizing that an executed supplier agreement can prevail where terms conflict. The published terms direct invoice delivery through EDI or email as specified in supplier policies; they do not make email an unrestricted alternative for every supplier.
  • The public SVHarbor trading-partner page provides UNFI EDI support context. Its legacy SUPERVALU labeling is a reason to confirm the applicable business entity and account instructions, not to assume every UNFI operation uses the same identifiers or technical guide.
  • UNFI Canada publishes a separate EDI resource site and a December 2025 factsheet describing its onboarding process and an assigned start date. These are Canada-specific materials and should not be applied as a U.S. supplier mandate.
  • Sources were reviewed November 9, 2026. No authenticated supplier-specific mapping packet was reviewed. The recommendations below are preparation guidance, not a promise of SignalEDI certification, automatic approval or an existing live UNFI connection.

Document and workflow scope

Use the cited source boundaries below, then confirm your current assigned program: Exact specifications come from your partner packet. Treat this as a planning checklist, not a substitute for the current implementation guide.

  • Purchase-order and item data: identify the buying entity, supplier account, destination, PO and line references, product identifier, quantity and unit. Obtain the assigned version and document guide rather than inferring them from a legacy portal name.
  • Invoice records: confirm the permitted channel and fields under the current supplier policies. Reconcile ordered, shipped and billed quantities, units and prices, and preserve the supplier's original invoice identifier through rejection and correction handling.
  • Shipping and product-handling evidence: collect the applicable routing, receipt, shelf-life and product-change instructions. Decide which details belong in electronic documents and which require warehouse controls or separate records; an EDI map cannot prove physical product condition.
  • Acknowledgement and reconciliation data: obtain the required technical and application responses, then distinguish accepted documents, receiving differences and finance disputes. Maintain enough reference data to investigate the relationship without exposing unnecessary customer or supplier information.

Connectivity and testing requirements

Connectivity

Confirm whether the current UNFI program uses AS2, SFTP, VAN, or another named transport.

Onboarding window

Not verified on this page.

Certification focus

The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule.

  • UNFI's public purchase terms cover United Natural Foods and subsidiaries including SUPERVALU, while recognizing that an executed supplier agreement can prevail where terms conflict. The published terms direct invoice delivery through EDI or email as specified in supplier policies; they do not make email an unrestricted alternative for every supplier.
  • The public SVHarbor trading-partner page provides UNFI EDI support context. Its legacy SUPERVALU labeling is a reason to confirm the applicable business entity and account instructions, not to assume every UNFI operation uses the same identifiers or technical guide.
  • UNFI Canada publishes a separate EDI resource site and a December 2025 factsheet describing its onboarding process and an assigned start date. These are Canada-specific materials and should not be applied as a U.S. supplier mandate.
  • Sources were reviewed November 9, 2026. No authenticated supplier-specific mapping packet was reviewed. The recommendations below are preparation guidance, not a promise of SignalEDI certification, automatic approval or an existing live UNFI connection.

Questions to resolve from the current buyer packet

  • Record the UNFI entity, country, supplier number and distribution locations in a scope worksheet. List current agreements and policies by revision. Resolve conflicts through the authorized business owner rather than assuming a public general term overrides the supplier's signed agreement.
  • Verify the current technical contact path and obtain the account-specific order, invoice and shipment requirements. Keep Canada resources in a separate section if the supplier operates in both countries, with independent identifiers, test evidence and launch decisions.
  • Review product identifiers and units with item-setup, warehouse and finance teams. Use representative cases, eaches and variable or changing pack information if applicable. Establish who can approve a mapping change and how old orders retain their original meaning.
  • Create an exception workflow for quantity differences between the supplier's shipment and the receiving record. Preserve the order, warehouse release, delivery evidence and invoice rather than changing one record until all totals happen to match.
  • Plan the cutover around actual open business documents. Reconcile POs already imported, goods in transit, invoices awaiting acceptance and unresolved deductions or disputes. Treat a partner-assigned activation event separately from a local adapter being ready to send.

How SignalEDI handles it

  • Prepare a versioned mapping and testing checklist from the requirements you provide.
  • Validate synthetic or scrubbed samples before partner testing.
  • Review acknowledgement and exception handling before production cutover. Scope is confirmed during setup.

Review mapping and validation in the self-serve workspace before partner testing. Developer quickstart

Pricing

SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.

Compare current plans

Practice the workflow before partner testing

These are recommended preparation exercises, not additional partner requirements or a customer success story. Use synthetic or scrubbed samples and adapt each exercise to the current guide assigned to your program.

Entity and country routing

Prepare a U.S. UNFI order, a Canadian order and a record carrying a legacy business label. Compare their supplier accounts, destinations and assigned guides before selecting a map. Include one missing country or entity field to exercise the unresolved case.

What a useful result looks like

Every record follows a verified account scope. The uncertain example is held for review instead of inheriting Canadian onboarding rules or legacy identifiers, and the configuration records the source of the routing decision.

Pack change and historical invoice

Create an order using one pack size, update the product master, then prepare an invoice for the original shipment. Include a similar product identifier and have warehouse and finance staff calculate the expected quantity and amount independently.

What a useful result looks like

The invoice retains the original order's commercial unit and price basis. A product-master update does not rewrite historical meaning, and ambiguous product matching is detected before a document is submitted.

Shipment versus receiving difference

Use a synthetic order whose supplier shipment quantity differs from the receiving quantity later reported. Assemble the PO, shipment record, delivery evidence and invoice. Walk through who investigates the discrepancy and what changes are permitted in each system.

What a useful result looks like

The records retain their distinct evidence rather than being forced to agree by silent edits. The exception has an owner and an explainable resolution path, with finance able to trace the effect of any correction.

Invoice correction after uncertain receipt

Simulate an invoice with a clear rejection and another with a lost response. Review the approved channel's status evidence before preparing a corrected invoice or retry. Repeat with an invoice that predates the provider cutover.

What a useful result looks like

The workflow distinguishes content correction from repeated transmission. Existing invoice identities and previous outcomes remain visible, and the new process cannot bill again merely because its local history starts after the original submission.

Common integration questions

Can I keep my existing ERP or accounting system?
Start with your existing system, its version, and the records you need to exchange. SignalEDI builds to your trading partner's requirement. Scope is confirmed during setup. Review the integration catalog for the specific connector and workflow before assuming production availability; an ERP name alone does not establish support for every edition or document.
Does validation mean my partner has approved production?
No. Passing document validation checks your sample against the configured rules. Partner certification, enrollment, transport approval, and permission to send live documents are separate steps controlled by the applicable partner program. Use synthetic or scrubbed samples while preparing and keep the approval evidence before switching to production.
Where can I see SignalEDI pricing?
SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.

Authoritative sources

Source review date: 2026-11-09. Links below establish only the facts described; your current buyer-issued materials remain authoritative for program-specific technical requirements.

UNFI questions

Can a UNFI supplier choose email instead of EDI for invoices?
Check the current agreement and supplier policies for the account. The public terms refer to EDI or email in the manner those policies specify; that is not blanket permission to switch channels. Record the approved method and exception process before configuring finance or sending any invoice.
Are UNFI Canada requirements the same as U.S. UNFI requirements?
Do not assume they are. The Canadian operation publishes its own EDI resources and onboarding information. Maintain a separate scope for each purchasing entity and country, even if the supplier shares an ERP. Confirm document guides, account identifiers, testing and activation with the applicable program.
What should UNFI invoice reconciliation prove?
A reviewer should be able to connect the invoice to the original PO and the goods shipped, then understand any receiving or pricing difference. Preserve source quantities, units and references. A delivered electronic message is one piece of evidence, not proof that receiving and payment reconciliation are complete.

Related EDI resources

Prepare your side for partner testing

SignalEDI can validate the documents and requirements your team controls. Partner approval follows the partner's schedule.

Connect now

Topics: UNFI EDI · UNFI supplier EDI · UNFI EDI requirements

© 2026 SignalEDI Inc. All rights reserved.