X12

Inbound

Wayfair LLC X12 310 Freight Receipt and Invoice (Ocean)

Wayfair

The EDI 310 (Freight Receipt and Invoice (Ocean)) document is used by Wayfair LLC for electronic data interchange. It enables automated processing and compliance with Wayfair LLC's trading partner requirements.

24segments

6loops

10mandatory

Book a demo

← All Wayfair LLC transactions

Schema Reference

24 segments · X12 310 Freight Receipt and Invoice (Ocean)

ISA01 Authorization Information Qualifier

M ID 2-2

ISA02 Authorization Information

M AN 10-10

ISA03 Security Information Qualifier

M ID 2-2

ISA04 Security Information

M AN 10-10

ISA05 Interchange ID Qualifier

M ID 2-2

ISA06 Interchange Sender ID

M AN 15-15

ISA07 Interchange ID Qualifier

M ID 2-2

ISA08 Interchange Receiver ID

M AN 15-15

ISA09 Interchange Date

M DT 6-6

ISA10 Interchange Time

M TM 4-4

ISA11 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator ISA12 Interchange Control Version Number

M ID 5-5

ISA13 Interchange Control Number

M N0 9-9

ISA14 Acknowledgment Requested

M ID 1-1

ISA15 Usage Indicator

M ID 1-1

GS01 Functional Identifier Code

M ID 2-2

GS02 Application Sender's Code

M AN 2-15

GS03 Application Receiver's Code

M AN 2-15

GS04 Date

M DT 8-8

GS05 Time

M TM 4-8

GS06 Group Control Number

M N0 1-9

GS07 Responsible Agency Code

M ID 1-2

GS08 Version / Release / Industry Identifier Code

M AN 1-12

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

B301 Shipment Qualifier

O ID 1-1

B302 Invoice Number

M AN 1-22

B303 Shipment Identification Number

O AN 1-30

B304 Shipment Method of Payment

M ID 2-2

B306 Date

M DT 8-8

B307 Net Amount Due

M N2 1-12

B309 Delivery Date

C DT 8-8

B310 Date/Time Qualifier

C ID 3-3

B311 Standard Carrier Alpha Code

M ID 2-4

B313 Tariff Service Code

O ID 2-2

B2A01 Transaction Set Purpose Code

M ID 2-2

Y601 Authority Identifier Code

O ID 2-2

Y602 Authority

M AN 1-20

Y603 Authorization Date

M DT 8-8

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-50

V102 Vessel Name

C AN 2-28

V104 Flight/Voyage Number

O AN 2-10

C301 Currency Code

M ID 3-3

Y201 Number of Containers

M N0 1-4

Y204 Equipment Type

M ID 4-4

Y206 Intermodal Service Code

O ID 1-2

N1 Loop Repeat: 10

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

C ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

C ID 2-3

G6101 Contact Function Code

M ID 2-2

G6102 Name

M AN 1-60

G6103 Communication Number Qualifier

C ID 2-2

G6104 Communication Number

C AN 1-256

R4 Loop Repeat: 20

R401 Port or Terminal Function Code

M ID 1-1

R402 Location Qualifier

C ID 1-2

R403 Location Identifier

C AN 1-30

R404 Port Name

O AN 2-24

R405 Country Code

O ID 2-3

R408 State or Province Code

O ID 2-2

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

R201 Standard Carrier Alpha Code

M ID 2-4

R202 Routing Sequence Code

M ID 1-2

LX Loop Repeat: 999

LX01 Assigned Number

M N0 1-6

N7 Loop Repeat: 999

N701 Equipment Initial

O AN 1-4

N702 Equipment Number

M AN 1-10

N703 Weight

C R 1-10

N704 Weight Qualifier

C ID 1-2

N708 Volume

C R 1-8

N709 Volume Unit Qualifier

C ID 1-1

N717 Weight Unit Code

O ID 1-1

N722 Equipment Type

O ID 4-4

L0 Loop Repeat: 120

L001 Lading Line Item Number

O N0 1-3

L004 Weight

C R 1-10

L005 Weight Qualifier

C ID 1-2

L006 Volume

C R 1-8

L007 Volume Unit Qualifier

C ID 1-1

L008 Lading Quantity

C N0 1-7

L009 Packaging Form Code

C ID 3-3

L011 Weight Unit Code

O ID 1-1

L501 Lading Line Item Number

O N0 1-3

L502 Lading Description

O AN 1-50

L301 Weight

C R 1-10

L302 Weight Qualifier

C ID 1-2

L305 Charge

O N2 1-12

L309 Volume

C R 1-8

L310 Volume Unit Qualifier

C ID 1-1

L311 Lading Quantity

O N0 1-7

L312 Weight Unit Code

O ID 1-1

L1 Loop Repeat: 20

L101 Lading Line Item Number

O N0 1-3

L102 Freight Rate

C R 1-9

L103 Rate/Value Qualifier

C ID 2-2

L104 Charge

C N2 1-12

L108 Special Charge or Allowance Code

O ID 3-3

L111 Charge Method of Payment

O ID 1-1

L112 Special Charge Description

O AN 2-25

L117 Billed/Rated-as Quantity

C R 1-11

L118 Billed/Rated-as Qualifier

C ID 2-2

L120 Currency Code

O ID 3-3

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

How It Works

Automating Wayfair LLC EDI 310

Stacksync validates, transforms, and delivers your 310 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate

Transform

Route

Monitor

Stacksync processes Wayfair LLC EDI 310 (Freight Receipt and Invoice (Ocean)) documents automatically — syncing data to your system in real time with no manual intervention required.

Wayfair LLC EDI 310 FAQ

Common questions about 310 Freight Receipt and Invoice (Ocean) transactions with Wayfair LLC.

What is a Wayfair LLC EDI 310 Freight Receipt and Invoice (Ocean)?

The Wayfair LLC EDI 310 Freight Receipt and Invoice (Ocean) is an X12 transaction set used to exchange Freight Receipt and Invoice (Ocean) data electronically between trading partners. As a inbound document, it standardizes the communication of Freight Receipt and Invoice (Ocean) information between Wayfair LLC and their suppliers, carriers, or partners. Stacksync processes Wayfair LLC 310 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Wayfair LLC's requirements in real time.

How does Stacksync automate Wayfair LLC EDI 310 Freight Receipt and Invoice (Ocean) transactions?

Stacksync handles Wayfair LLC EDI 310 Freight Receipt and Invoice (Ocean) transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 310 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Wayfair LLC 310 document meets their specific formatting requirements before transmission or after receipt.

What are common Wayfair LLC EDI 310 errors and how do I fix them?

Common errors in Wayfair LLC EDI 310 Freight Receipt and Invoice (Ocean) transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Wayfair LLC 310 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

How long does it take to set up Wayfair LLC EDI 310 with Stacksync?

Most Wayfair LLC EDI 310 Freight Receipt and Invoice (Ocean) integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Wayfair LLC's 310 format and your system, running test transactions, and completing Wayfair LLC's certification process if required. Stacksync includes pre-built mappings for Wayfair LLC's most common 310 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize Wayfair LLC EDI 310 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Wayfair LLC EDI 310 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Wayfair LLC updates their 310 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate Wayfair LLC EDI?