To start and identify an interchange of zero or more functional groups and interchange-related control segments
Wayfair LLC X12 310 Freight Receipt and Invoice (Ocean)
Plan X12 310 Freight Receipt and Invoice (Ocean) for Wayfair LLC / Wayfair. Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 24
- Loops
- 6
- X12 310
- Partner references ↗
Implementation guide
Wayfair LLC / Wayfair: 310 mapping and validation
X12 310 Freight Receipt and Invoice (Ocean) is used when ocean shipment charges are ready to bill. Preserve carrier invoice, bill of lading and container references so the ocean-freight payable in your business system stays connected to the original document.
This document is listed for Wayfair LLC / Wayfair. 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 | ocean-freight payable carrier invoice, bill of lading and container references |
|
| Update the receiving system | Processing the ocean-freight payable ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the ocean-freight payable Original document reference and matching response |
|
The document reference includes 24 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 ocean shipment charges are ready to bill. Name the operational owner of the ocean-freight payable and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map carrier invoice, bill of lading and container references. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Wayfair LLC guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic ocean-freight payable 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 ocean-freight payable processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 310 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic ocean-freight payable 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 ocean-freight payable without processing it twice.
Transaction context
Where 310 Freight Receipt and Invoice (Ocean) fits on Wayfair
- Wayfair LLC channels
- 1 of 1
1 of Wayfair LLC's 1 channel list 310
- Trading partners
- 4
partner references list 310
- Channels
- 5
channel entries list 310
Frequently listed alongside 310
Document structure
X12 310 Freight Receipt and Invoice (Ocean) at the element level
The X12 310 reference contains 75 segment entries and 489 data elements; 78 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 75
- Data elements
- 489
- Mandatory elements
- 78
| Segment | Elements | Mandatory |
|---|---|---|
| B3 | 14 | 5 |
| B2A | 2 | 1 |
| Y6 | 3 | 2 |
| G3 | 6 | 1 |
| N9 | 6 | 1 |
| M0 | 4 | 1 |
| M1 | 12 | 1 |
| C2 | 7 | 3 |
| C3 | 4 | 1 |
| Y2 | 10 | 2 |
| N1 | 6 | 1 |
| N2 | 2 | 1 |
Key identifiers in 310
- Invoice Number
- Shipment Method of Payment
- Date
- Net Amount Due
- Standard Carrier Alpha Code
- Transaction Set Purpose Code
- Authority
- Authorization Date
Segment reference — 24 segments 6 loops · X12 310 Freight Receipt and Invoice (Ocean)
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 transmit basic data relating to the carrier's invoice
To allow for positive identification of transaction set purpose
To specify the authority for authorizing an action and the date authentication is made
To transmit identifying information as specified by the Reference Identification Qualifier
To provide vessel details and voyage number
To specify the currency being used in the transaction set
To specify container information and transportation service to be used
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
To identify a person or office to whom communications should be directed
R4 Loop Repeat: 20
Contractual or operational port or point relevant to the movement of the cargo
To specify pertinent dates and times
To specify carrier and routing sequences and details
LX Loop Repeat: 999
To reference a line number in a transaction set
N7 Loop Repeat: 999
To identify the equipment
L0 Loop Repeat: 120
To specify quantity, weight, volume, and type of service for a line item including applicable \"quantity/rate-as\" data
To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items
L1 Loop Repeat: 20
To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements
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 the line item in terms of description, quantity, packaging, and marks and numbers
Related references
Other transactions in Wayfair
Other EDI documents listed on this channel.
Warehouse Inventory Adjustment Advice X12 947 Ship Notice Manifest X12 856 Purchase Order Change Acknowledgment Request Seller Initiated X12 865 Purchase Order X12 850 Purchase Order Change Request Buyer Initiated X12 860 Inventory Inquiry Advice X12 846 Invoice X12 810 Purchase Order Acknowledgment X12 855
No references match your search.
Showing 8 of 8 references
Browse the full directoryWayfair LLC / Wayfair EDI 310 questions
Common questions about 310 Freight Receipt and Invoice (Ocean) on the Wayfair channel.
What is X12 310 Freight Receipt and Invoice (Ocean) used for?
310 is used when ocean shipment charges are ready to bill. It carries information for the ocean-freight payable. Match it to your business system using carrier invoice, bill of lading and container references.
Is 310 required for Wayfair LLC / Wayfair?
310 is listed for Wayfair LLC / Wayfair. Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 310?
Start with carrier invoice, bill of lading and container references and the target ocean-freight payable. 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 310 error handling?
Reconcile charges for multiple containers to the bill total. Distinguish an additional charge from a replacement invoice for the same voyage. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 310 relate to other EDI messages?
Keep 310 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the ocean-freight payable workflow; confirm any required companion messages with your partner.
Connect Wayfair LLC 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.
