Starbucks Coffee Company EDI 211 Motor Carrier Bill of Lading

Schema Reference

19 segments · X12 211 Motor Carrier Bill of Lading

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 Interchange 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

BOL01 Standard Carrier Alpha Code

M ID 2-4

BOL02 Shipment Method of Payment

M ID 2-2

BOL03 Shipment Identification Number

M AN 1-30

BOL04 Date

M DT 8-8

B2A01 Transaction Set Purpose Code

M ID 2-2

L1101 Reference Identification

C AN 1-50

L1102 Reference Identification Qualifier

C ID 2-3

G6201 Date Qualifier

C ID 2-2

G6202 Date

C DT 8-8

G6203 Time Qualifier

C ID 1-2

G6204 Time

C TM 4-8

G6205 Time Code

O ID 2-2

AT501 Special Handling Code

C ID 2-3

AT502 Special Services Code

C ID 2-10

AT503 Special Handling Description

C AN 2-30

AT504 Unit or Basis for Measurement Code

C ID 2-2

AT505 Temperature

C R 1-4

AT506 Temperature

C R 1-4

K101 Free-form Information

M AN 1-30

N1 Loop Repeat: 10

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N201 Name

M 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

N405 Location Qualifier

C ID 1-2

N406 Location Identifier

O AN 1-30

N407 Country Subdivision Code

C ID 1-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

AT1 Loop Repeat: 9,999

AT101 Lading Line Item Number

M N0 1-3

AT2 Loop Repeat: 1

AT201 Lading Quantity

C N0 1-7

AT202 Packaging Form Code

C ID 3-3

AT203 Weight Qualifier

M ID 1-2

AT204 Weight Unit Code

M ID 1-1

AT205 Weight

M R 1-10

AT206 Lading Quantity

C N0 1-7

AT207 Packaging Form Code

C ID 3-3

AT209 Commodity Code

O AN 1-30

MAN01 Marks and Numbers Qualifier

M ID 1-2

MAN02 Marks and Numbers

M AN 1-48

OID02 Purchase Order Number

C AN 1-22

OID04 Packaging Form Code

C ID 3-3

OID05 Quantity

C R 1-15

OID11 Reference Identification

O AN 1-50

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Automating Starbucks Coffee Company EDI 211

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

Validate

Transform

Route

Monitor

Stacksync processes Starbucks Coffee Company EDI 211 (Motor Carrier Bill of Lading) documents automatically — syncing data to your system in real time with no manual intervention required.

Starbucks Coffee Company EDI 211 FAQ

Common questions about 211 Motor Carrier Bill of Lading transactions with Starbucks Coffee Company.

How long does it take to set up Starbucks Coffee Company EDI with Stacksync?

Most suppliers are fully connected and processing live Starbucks Coffee Company EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Starbucks Coffee Company?

No. Stacksync handles the entire EDI transport layer. We connect directly to Starbucks Coffee Company's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Starbucks Coffee Company compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Starbucks Coffee Company?

Stacksync supports all EDI document types required by Starbucks Coffee Company — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Starbucks Coffee Company EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Starbucks Coffee Company's EDI network and your system in real time.

What happens when Starbucks Coffee Company updates their EDI specifications?

Stacksync monitors Starbucks Coffee Company's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.