Skip to content

Performance Food Group (PFG) EDI
integration guide.

Plan your Performance Food Group (PFG) EDI integration using 5 listed document types across 2 channels. Compare channels, map business records and test the operational handoff.

Discuss Performance Food Group (PFG) EDI requirements Explore the Performance Food Group (PFG) catalog
Listed documents
5
Catalog reference entries
Listed channels
2
Performance Foodservice (via SPS Commerce) → Performance Foodservice (via iTrade) (ISA ID: EFSPFS)
Implementation
Plan
Map, validate and reconcile

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Implementation guide

Performance Food Group (PFG): document mapping and implementation plan

Performance Food Group (PFG) has 5 distinct document types listed in this catalog across 2 channels. Use the document-to-record plan below to scope your ERP, warehouse or transport integration. Catalog presence describes available reference material; your agreement determines the required messages and versions.

Business records, identifiers and acceptance tests
Document or decisionRecord and correlationAcceptance tests to agree
X12 855 Purchase Order AcknowledgmentListed on 2 channels: Performance Foodservice (via SPS Commerce), Performance Foodservice (via iTrade) (ISA ID: EFSPFS) purchase-order response

original purchase order, response revision and order line
  • Test a partially accepted order with a backordered line and retain both outcomes.
  • Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates.
X12 860 Purchase Order Change Request Buyer InitiatedListed on 1 channel: Performance Foodservice (via SPS Commerce) buyer order-change request

original purchase order, change revision and affected line
  • Apply a quantity reduction to the existing order instead of creating another order.
  • Test a cancellation arriving after allocation or shipment and route it to an exception owner.
X12 810 InvoiceListed on 2 channels: Performance Foodservice (via SPS Commerce), Performance Foodservice (via iTrade) (ISA ID: EFSPFS) accounts-receivable or accounts-payable invoice

invoice number, purchase order and invoice line
  • Reconcile line amounts, allowances, charges and tax to the invoice total.
  • Submit the same invoice twice and verify that it cannot create a second payable.
X12 850 Purchase OrderListed on 2 channels: Performance Foodservice (via SPS Commerce), Performance Foodservice (via iTrade) (ISA ID: EFSPFS) purchase order or sales order

buyer purchase order, order line and trading-party identifiers
  • Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit.
  • Resend one purchase order and confirm that only one sales order is created.
X12 856 Ship Notice ManifestListed on 1 channel: Performance Foodservice (via iTrade) (ISA ID: EFSPFS) shipment notice (ASN)

shipment, order, package and item references
  • Reconcile item quantities through shipment, order and packaging levels against the physical shipment.
  • Test split shipments for one purchase order and prevent the second ASN from replacing the first.

From business event to reconciled record

  1. Identify the exact trading relationship

    Choose among Performance Foodservice (via SPS Commerce), Performance Foodservice (via iTrade) (ISA ID: EFSPFS). Confirm the business unit and account before copying a mapping from another channel.

  2. Map business records and responses

    Start with purchase-order response, buyer order-change request, accounts-receivable or accounts-payable invoice. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.

  3. Prove the channel with representative cases

    Run a normal exchange and the document-specific exception cases below. Capture transport receipt, syntax validation and business processing as separate results. Agree the Performance Food Group (PFG) test/production handoff and retain the evidence for each approved message.

  4. Reconcile after cutover

    Compare source and destination counts using original purchase order, response revision and order line. Investigate missing responses, duplicates and rejected records with a named owner. Approve recovery behavior before enabling automatic retries.

Before approving production

  • Current X12 guide, release/version, required subset and sample files are recorded.
  • Sender/receiver identifiers, test endpoint and production endpoint are agreed with the channel owner.
  • Transport receipts, document acknowledgments and business responses have separate monitoring and escalation.
  • Duplicate handling, partial processing and reconciliation have passed with realistic source-system records.

Document catalog

EDI documents listed for Performance Food Group (PFG)

8 transactions across 2 channels.

Document flow

Example document relationships for Performance Food Group (PFG)

Where each document sits in its trading cycle, based on the 5 document types listed for Performance Food Group (PFG) across 2 channels. These are example relationships; the trading agreement determines the required sequence.

  • 810 Invoice — is listed on 2 of Performance Food Group (PFG)'s 2 channels
  • 850 Purchase Order — is listed on 2 of Performance Food Group (PFG)'s 2 channels
  • 855 Purchase Order Acknowledgment — is listed on 2 of Performance Food Group (PFG)'s 2 channels
  • 856 Ship Notice Manifest — is listed on 1 of Performance Food Group (PFG)'s 2 channels
  • 860 Purchase Order Change Request Buyer Initiated — is listed on 1 of Performance Food Group (PFG)'s 2 channels

Network context

Performance Food Group (PFG) channel references for SPS Commerce and iTrade

These network names are derived from the listed Performance Food Group (PFG) channels. Confirm routing, enrollment and contractual requirements for your account before selecting a connection method.

iTrade

3 channels · 3 trading partners in the catalog

Performance Food Group (PFG) channel on this network: Performance Foodservice (via iTrade) (ISA ID: EFSPFS)

Most frequently listed documents
  • 810 3 ch
  • 850 3 ch
  • 855 3 ch
  • 856 3 ch
  • 860 1 ch
Also listed with iTrade
LEGACY EDI MIGRATION FUND

Still with a legacy EDI vendor? We cover the buyout.

Stacksync buys back your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. No migration cost, no overlap billing.

Check your eligibility for the EDI migration fund
Migrate from SPS Commerce
Migrate from Cleo
Migrate from TrueCommerce
Migrate from OpenText
SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Trading partners

0+ trading partners.
And every channel covered.

We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.

The Home Depot Walmart Nordstrom JCPenney Target Sprouts Farmers Market Ulta Beauty Macy's Lowe's AGCO Your Agriculture Company Mountain High Outfitters Rivian Automotive, Inc PetSmart Bealls Inc. Sysco Tepperman's Kroger Modernized Systems Williams Sonoma Evereve.com Shamrock Foods Chewy
Browse the full directory

FAQ

Performance Food Group (PFG) EDI questions

Which EDI documents are listed for Performance Food Group (PFG)?

X12 855 Purchase Order Acknowledgment; X12 860 Purchase Order Change Request Buyer Initiated; X12 810 Invoice; X12 850 Purchase Order; X12 856 Ship Notice Manifest. These are catalog listings. Confirm the required subset, direction and version for your trading agreement.

How should I choose the Performance Food Group (PFG) EDI channel?

This catalog lists 2 channels for Performance Food Group (PFG), including Performance Foodservice (via SPS Commerce), Performance Foodservice (via iTrade) (ISA ID: EFSPFS). Match the channel to your actual trading relationship and compare its document list before reusing a mapping.

Which identifiers should the Performance Food Group (PFG) mapping preserve?

For X12 855 Purchase Order Acknowledgment, plan around original purchase order, response revision and order line. For X12 860 Purchase Order Change Request Buyer Initiated, use original purchase order, change revision and affected line. Confirm field locations, qualifiers and allowed values in the applicable guide; these are business-level mapping recommendations.

Does a successful EDI receipt mean Performance Food Group (PFG) accepted the business document?

Track three outcomes separately: transport receipt, syntax or implementation validation, and business processing. An AS2 MDN acknowledges the transport exchange; an X12 997 or 999 concerns technical validation. The agreed business response or reconciliation confirms whether the order, shipment or invoice was processed.

What should be tested before launching Performance Food Group (PFG) EDI?

Test a partially accepted order with a backordered line and retain both outcomes. Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates. Also test missing responses and recovery after a destination failure. Confirm partner approval and named exception owners before choosing a production date.

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own