Skip to content

Piggly Wiggly EDI
integration guide.

Plan your Piggly Wiggly EDI integration using 2 listed document types across 2 channels. Compare channels, map business records and test the operational handoff.

Book an EDI demo Explore EDI documents
Listed documents
2
Partner document references
Listed channels
2
Piggly Wiggly Midwest (via Edict Systems) → Piggly Wiggly Alabama DC (via Edict Systems)
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

Piggly Wiggly: EDI implementation plan

Build a reliable EDI workflow for Piggly Wiggly. Use 2 document types across 2 channels to plan record mapping, prevent duplicate processing and reconcile results in your business systems.

The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
X12 875 Grocery Products Purchase OrderListed on 2 channels: Piggly Wiggly Midwest (via Edict Systems), Piggly Wiggly Alabama DC (via Edict Systems) grocery purchase order

purchase order, item and pack or unit basis
  • Test catch-weight or variable-quantity items using the units agreed in the partner guide.
  • Separate case quantities from each quantities during sales-order creation.
X12 880 Grocery Products InvoiceListed on 2 channels: Piggly Wiggly Midwest (via Edict Systems), Piggly Wiggly Alabama DC (via Edict Systems) grocery invoice

invoice, grocery order and item
  • Reconcile quantity units and allowances before posting the invoice.
  • Test a duplicate invoice while keeping an authorized correction traceable.

Implementation steps

  1. Choose the trading account and channel

    Choose among Piggly Wiggly Midwest (via Edict Systems), Piggly Wiggly Alabama DC (via Edict Systems). Confirm the business unit and account before copying a mapping from another channel.

  2. Map records and assign owners

    Start with grocery purchase order, grocery 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. Test a complete exchange

    Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Piggly Wiggly production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using purchase order, item and pack or unit basis. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.

Go-live checklist

  • The required X12 documents, versions and sample files are agreed.
  • Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
  • Delivery receipts, document validation and business responses have monitoring and a named owner.
  • Tests cover duplicates, partial processing and reconciliation with realistic business records.

Document catalog

EDI documents listed for Piggly Wiggly

4 transactions across 2 channels.

Document flow

Example document relationships for Piggly Wiggly

Where each document sits in its trading cycle, based on the 2 document types listed for Piggly Wiggly across 2 channels. These are example relationships; the trading agreement determines the required sequence.

  • 875 Grocery Products Purchase Order — is listed on 2 of Piggly Wiggly's 2 channels
  • 880 Grocery Products Invoice — is listed on 2 of Piggly Wiggly's 2 channels

Network context

Piggly Wiggly channel references for Edict Systems

These network names are derived from the listed Piggly Wiggly channels. Confirm routing, enrollment and contractual requirements for your account before selecting a connection method.

Edict Systems

5 channels · 4 trading partners in the catalog

Piggly Wiggly channels on this network: Piggly Wiggly Midwest (via Edict Systems), Piggly Wiggly Alabama DC (via Edict Systems)

Most frequently listed documents
  • 875 5 ch
  • 880 5 ch
  • 855 2 ch
  • 856 1 ch
Also listed with Edict Systems
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 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more

Related references

Partners with related document listings

Compare document requirements for similar business processes.

Sprouts Farmers Market 19 docs · 2 channels Kroger 11 docs · 2 channels Kroger Modernized Systems 10 docs · 1 channel Wakefern 10 docs · 2 channels Core-Mark (via SPS Commerce) 9 docs · 1 channel HEB (Here Everything's Better) 9 docs · 1 channel Albertsons (Safeway) 9 docs · 2 channels Stater Bros. Markets 6 docs · 1 channel McLane Company, Inc. 6 docs · 1 channel Meijer 6 docs · 2 channels Associated Wholesale Grocers (AWG) 6 docs · 1 channel Certco Inc. 4 docs · 1 channel URM Stores 4 docs · 1 channel Merchant Distributors 3 docs · 1 channel SpartanNash 3 docs · 1 channel Spartan Nash (dba Nash Finch) 3 docs · 1 channel Ingles Markets Inc 3 docs · 1 channel Harris Teeter 3 docs · 1 channel Bozzuto’s Inc. 3 docs · 1 channel Schnucks 3 docs · 1 channel Affiliated Foods Inc. 3 docs · 1 channel

Showing 21 of 33 references

Browse the full directory

FAQ

Piggly Wiggly EDI questions

Which EDI documents are listed for Piggly Wiggly?

X12 875 Grocery Products Purchase Order; X12 880 Grocery Products Invoice. Confirm which documents, directions and versions apply to your account.

How should I choose the Piggly Wiggly EDI channel?

The directory lists 2 channels for Piggly Wiggly, including Piggly Wiggly Midwest (via Edict Systems), Piggly Wiggly Alabama DC (via Edict Systems). Match the channel to your actual trading relationship and compare its document list before reusing a mapping.

Which identifiers should the Piggly Wiggly mapping preserve?

For X12 875 Grocery Products Purchase Order, plan around purchase order, item and pack or unit basis. For X12 880 Grocery Products Invoice, use invoice, grocery order and item. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean Piggly Wiggly accepted the business document?

Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.

What should be tested before launching Piggly Wiggly EDI?

Test catch-weight or variable-quantity items using the units agreed in the partner guide. Separate case quantities from each quantities during sales-order creation. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

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 Get started