To start and identify an interchange of zero or more functional groups and interchange-related control segments
Harbor Foods X12 879 Price Information
X12 879 (Price Information) is the EDI transaction exchanged between Harbor Foods (Harbor Wholesale Foods (via SPS Commerce)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 16
- Loops
- 3
- X12 879
- All partners ↗
Transaction context
Where 879 Price Information fits on Harbor Wholesale Foods (via SPS Commerce)
- Harbor Foods channels
- 1 of 1
- Trading partners
- 2
- Channels
- 2
1 of Harbor Foods's 1 channel carries 879
partners across the Stacksync network trade 879
channels network-wide carry 879
Most common alongside 879
On SPS Commerce, 879 runs on 1 channel.
The 879 carries item cost data between grocery trading partners: original prices for new items, changes to existing prices, and confirmations that pricing was received. Buyers load it into their cost files ahead of orders so later invoices match on price, which reduces deductions and invoice-matching disputes. It follows UCS grocery guidelines; general merchandise retailers typically carry the same data on an 832 Price/Sales Catalog. A supplier, manufacturer, or broker sends the 879 to a retailer, distributor, or buying organization, which confirms receipt with a 997 Functional Acknowledgment.
When it fires: A supplier creates a new item or approves a cost change in its ERP and must publish the price and its effective date to buyers before orders and invoices reference it.
Common 879 rejection causes
- Effective-date violations: receivers enforce pricing calendars. DeCA, for example, rejects an 879 whose cost effective date is in the past, misses the submission cutoff, or does not fall on the 1st or 16th of the month (error codes 0600F, 0601F).
- Item identification failures: the unit UPC is not in the receiver's catalog or the item is not authorized under the vendor's contract (DeCA codes 0606F, 0609F).
- Case-level pricing sent without the required case pack or case UPC when the unit basis is CA, or a unit basis other than CA or EA (DeCA codes 0607F, 0608F, 0626F).
- Duplicate price changes for the same item, party, location, and start date within a transaction set or working set are rejected (DeCA code 0616F).
Specification summary
X12 879 Price Information at the element level
The X12 879 specification defines 20 segments carrying 67 data elements, 38 of which are mandatory.
- Segments
- 20
- Data elements
- 67
- Mandatory elements
- 38
| Segment | Elements | Mandatory |
|---|---|---|
| G91 | 1 | 1 |
| N1 | 4 | 1 |
| G61 | 4 | 2 |
| NTE | 2 | 1 |
| G36 | 2 | 2 |
| G69 | 1 | 1 |
| G43 | 3 | 1 |
| G46 | 5 | 2 |
| G40 | 5 | 1 |
Key identifiers in 879
- Change Type Code
- Entity Identifier Code
- Contact Function Code
- Name
- Description
- Price List Number
- Date
- Free-form Description
Full segment guideline — 16 segments 3 loops · X12 879 Price Information
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To enable the supplier/broker to change pricing information
N1 Loop Repeat: 999
To identify a party by type of organization, name, and code
To identify a person or office to whom communications should be directed
To transmit information in a free-form format, if necessary, for comment or special instruction
To provide price list references and descriptions
To specify pertinent dates and times
G28 Loop Repeat: 100
To provide basic product identification information
To specify packing details of the items shipped
To describe an item in free-form format
To specify the geographic area in which a promotion or price is in effect
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify unit amount and method of payment for a charge/allowance for a line item
G40 Loop Repeat: 100
To provide a vendor's pricing structure associated with a specific line item
Trading partners
5+ 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.
PU Purchase Order PU Purchase Order Change Request Buyer Initiated PU Purchase Order Acknowledgment SH Ship Notice Manifest IN Invoice
No trading partner matches your search.
Browse the full directory
Harbor Foods Harbor Wholesale Foods (via SPS Commerce) EDI 879 FAQ
Common questions about 879 Price Information on the Harbor Wholesale Foods (via SPS Commerce) channel.
What is X12 879 Price Information?
X12 879 (Price Information) is the EDI transaction set used to exchange price information data. Harbor Foods's Harbor Wholesale Foods (via SPS Commerce) channel requires it from trading partners.
Does Harbor Foods Harbor Wholesale Foods (via SPS Commerce) require 879 for trading partners?
Yes, Harbor Foods (Harbor Wholesale Foods (via SPS Commerce)) supports X12 879 Price Information. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Harbor Foods 879 with Stacksync?
Most companies go live with Harbor Foods 879 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 879 on Harbor Wholesale Foods (via SPS Commerce)?
On Harbor Wholesale Foods (via SPS Commerce), X12 879 is typically exchanged alongside 850 Purchase Order, 855 Purchase Order Acknowledgment, 856 Ship Notice Manifest, 810 Invoice. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Harbor Foods EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
