To start and identify an interchange of zero or more functional groups and interchange-related control segments
Harbor Foods X12 879 Price Information
Plan X12 879 Price Information for Harbor Foods / Harbor Wholesale Foods (via SPS Commerce). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 16
- Loops
- 3
- X12 879
- Partner references ↗
Implementation guide
Harbor Foods / Harbor Wholesale Foods (via SPS Commerce): 879 mapping and validation
X12 879 Price Information is used when grocery or product pricing is distributed. Preserve item, price type and effective period so the price information in your business system stays connected to the original document.
This document is listed for Harbor Foods / Harbor Wholesale Foods (via SPS Commerce). Confirm the version, required fields and responses that apply to your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | price information item, price type and effective period |
|
| Update the receiving system | Processing the price information ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the price information Original document reference and matching response |
|
The document reference includes 16 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when grocery or product pricing is distributed. Name the operational owner of the price information and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map item, price type and effective period. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Harbor Foods guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic price information data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful price information processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 879 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic price information data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out price information without processing it twice.
Transaction context
Where 879 Price Information fits on Harbor Wholesale Foods (via SPS Commerce)
- Harbor Foods channels
- 1 of 1
1 of Harbor Foods's 1 channel list 879
- Trading partners
- 2
partner references list 879
- Channels
- 2
channel entries list 879
Frequently listed alongside 879
The directory associates SPS Commerce and 879 with 1 channel.
Document structure
X12 879 Price Information at the element level
The X12 879 reference contains 20 segment entries and 67 data elements; 38 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Segment reference — 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
Related references
Other transactions in Harbor Wholesale Foods (via SPS Commerce)
Other EDI documents listed on this channel.
Purchase Order X12 850 Purchase Order Change Request Buyer Initiated X12 860 Purchase Order Acknowledgment X12 855 Ship Notice Manifest X12 856 Invoice X12 810
No references match your search.
Showing 5 of 5 references
Browse the full directoryHarbor Foods / Harbor Wholesale Foods (via SPS Commerce) EDI 879 questions
Common questions about 879 Price Information on the Harbor Wholesale Foods (via SPS Commerce) channel.
What is X12 879 Price Information used for?
879 is used when grocery or product pricing is distributed. It carries information for the price information. Match it to your business system using item, price type and effective period.
Is 879 required for Harbor Foods / Harbor Wholesale Foods (via SPS Commerce)?
879 is listed for Harbor Foods / Harbor Wholesale Foods (via SPS Commerce). Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 879?
Start with item, price type and effective period and the target price information. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 879 error handling?
Keep promotional and regular prices distinct. Test overlapping effective dates and resolve which price is valid for the order date. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 879 relate to other EDI messages?
Keep 879 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the price information workflow; confirm any required companion messages with your partner.
Connect Harbor Foods EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
