Thermo Fisher Scientific Inc. EDI 856 ASN Integration

Schema Reference

20 segments · X12 856 Ship Notice/Manifest

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 Interchange Control Standards Identifier

M ID 1-1

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

BSN01 Transaction Set Purpose Code

M ID 2-2

BSN02 Shipment Identification

M AN 2-30

BSN03 Date

M DT 8-8

BSN04 Time

M TM 4-8

BSN05 Hierarchical Structure Code

O ID 4-4

HL Loop Repeat: 200,000

HL01 Hierarchical ID Number

M AN 1-12

HL02 Hierarchical Parent ID Number

O AN 1-12

HL03 Hierarchical Level Code

M ID 1-2

HL04 Hierarchical Child Code

O ID 1-1

LIN01 Assigned Identification

O AN 1-20

LIN02 Product/Service ID Qualifier

M ID 2-2

LIN03 Product/Service ID

M AN 1-48

LIN04 Product/Service ID Qualifier

C ID 2-2

LIN05 Product/Service ID

C AN 1-48

SN101 Assigned Identification

O AN 1-20

SN102 Number of Units Shipped

M R 1-10

SN103 Unit or Basis for Measurement Code

M ID 2-2

SLN01 Assigned Identification

M AN 1-20

SLN02 Assigned Identification

O AN 1-20

SLN03 Relationship Code

M ID 1-1

SLN09 Product/Service ID Qualifier

C ID 2-2

SLN10 Product/Service ID

C AN 1-48

PRF01 Purchase Order Number

M AN 1-22

PID01 Item Description Type

M ID 1-1

PID02 Product/Process Characteristic Code

O ID 2-3

PID03 Agency Qualifier Code

C ID 2-2

PID05 Description

C AN 1-80

TD501 Routing Sequence Code

O ID 1-2

TD502 Identification Code Qualifier

C ID 1-2

TD503 Identification Code

C AN 2-80

TD504 Transportation Method/Type Code

C ID 1-2

TD505 Routing

C AN 1-35

REF01 Reference Identification Qualifier

M ID 2-3

REF02 Reference Identification

C AN 1-30

MAN01 Marks and Numbers Qualifier

M ID 1-2

MAN02 Marks and Numbers

M AN 1-48

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

DTM03 Time

C TM 4-8

DTM04 Time Code

O ID 2-2

N1 Loop Repeat: 200

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

N202 Name

O 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

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

N405 Location Qualifier

C ID 1-2

N406 Location Identifier

O AN 1-30

CTT01 Number of Line Items

M N0 1-6

CTT02 Hash Total

O R 1-10

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Automating Thermo Fisher Scientific Inc. EDI 856

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

Validate

Transform

Route

Monitor

Stacksync builds and transmits 856 ASNs automatically when shipments are created in your WMS. Carton contents, pallet labels, SSCC-18 codes, and tracking numbers are pulled from your warehouse data — eliminating manual EDI entry.

Business unit variations

Fisher Scientific (CA) (ISA ID: 247192180IBMP)

Thermo Fisher Scientific Inc. EDI 856 FAQ

Common questions about 856 Ship Notice/Manifest transactions with Thermo Fisher Scientific Inc..

How long does it take to set up Thermo Fisher Scientific Inc. EDI with Stacksync?

Most suppliers are fully connected and processing live Thermo Fisher Scientific Inc. 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 Thermo Fisher Scientific Inc.?

No. Stacksync handles the entire EDI transport layer. We connect directly to Thermo Fisher Scientific Inc.'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 Thermo Fisher Scientific Inc. 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 Thermo Fisher Scientific Inc.?

Stacksync supports all EDI document types required by Thermo Fisher Scientific Inc. — 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 Thermo Fisher Scientific Inc. 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 Thermo Fisher Scientific Inc.'s EDI network and your system in real time.

What happens when Thermo Fisher Scientific Inc. updates their EDI specifications?

Stacksync monitors Thermo Fisher Scientific Inc.'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.