Distribution integration

Henry Schein EDI for suppliers

A guide for suppliers to Henry Schein: verified company facts, what Henry Schein publishes about EDI, the documents healthcare and laboratory distributors typically exchange, and what is still to confirm.

Overview

Understanding Henry Schein integration

Who this is for: Manufacturers and suppliers of medical, dental and laboratory products that sell through Henry Schein, and their EDI, order management and finance teams.

Henry Schein, Inc. distributes dental and medical supplies. Its website is henryschein.com.

Henry Schein does not publish supplier EDI requirements on its public website: we found no supplier EDI specification, implementation guide or onboarding page when we checked on 7 November 2026. Suppliers usually receive a distributor's requirements during setup, from its purchasing or EDI team, and they can differ by program, division and region.

Healthcare and laboratory distributors commonly send purchase orders by EDI and expect an order acknowledgment, an advance ship notice and an invoice in return. Product data carries extra weight: GTINs, lot numbers and expiration dates support receiving and traceability. Manufacturers that sell on contract pricing often exchange sales reports and chargeback documents with distributors as well. The documents, flow and connection options on this page describe that general practice. They are not Henry Schein's published requirements; confirm each one with Henry Schein before you build maps or test.

Workflows

Typical Henry Schein business workflows

General guidance: typical flows in this industry, not Henry Schein's published process.

Typical order to invoice

  1. 1Receive 850 purchase order
  2. 2Send 855 acknowledgment
  3. 3Ship with lot and expiry
  4. 4Send 856 ship notice
  5. 5Send 810 invoice

Documents and APIs

Henry Schein documents by program

General guidance. We could not verify Henry Schein's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Henry Schein's confirmed requirements. Confirm the list, versions and programs with Henry Schein.

DocumentNameDirectionProgramStatusPurpose
850 Purchase Order From Henry Schein Not stated General guidance Typically how the distributor orders for its distribution centers.
855 Purchase Order Acknowledgment To Henry Schein Not stated General guidance Typically confirms quantities, prices and ship dates.
856 Ship Notice/Manifest To Henry Schein Not stated General guidance Typically lists what is on each shipment, with lot and expiration details.
810 Invoice To Henry Schein Not stated General guidance Typically bills for what shipped, against the purchase order.
867 Product Transfer and Resale Report From Henry Schein Not stated General guidance Often used to report sales of the manufacturer's products under contract pricing.
844 Product Transfer Account Adjustment From Henry Schein Not stated General guidance Often used by distributors to claim contract-price chargebacks.
849 Response to Product Transfer Account Adjustment To Henry Schein Not stated General guidance Often used by the manufacturer to accept or reject each chargeback line.

Connectivity

How companies connect

  • AS2 or SFTP

    Many distributors exchange EDI files directly over AS2 or SFTP. Confirm which methods Henry Schein accepts.

    General guidance

  • EDI network (VAN)

    Many suppliers connect through a value-added network that delivers files to and from the distributor.

    General guidance

  • Supplier web portal

    Some distributors offer a supplier portal for orders, invoices or onboarding; a login is usually required.

    General guidance

Challenges

Common integration challenges

  • Lot and expiration data

    Lot numbers and expiration dates must be correct on labels and ship notices for receiving and traceability.

  • Contract pricing

    Chargebacks and sales reports must reconcile with the contracts that set the prices.

  • Product identifiers

    GTINs and item records must match what the distributor has on file.

  • Requirements not public

    Henry Schein does not publish its supplier EDI requirements, so the document set and rules must be confirmed with Henry Schein before work starts.

Automation options for Henry Schein suppliers

Four ways to automate. One foundation.

ECOM helps you automate them, meet Henry Schein's labeling and ship notice requirements, and see what needs action. Henry Schein sets its program's rules; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Connect Henry Schein documents to your ERP

ECOM connects the documents Henry Schein asks for with your ERP and warehouse systems, so orders post without re-keying and ship notices and invoices come from the data you already hold.

Industry

Healthcare

See how ECOM supports EDI for healthcare suppliers.

Industry

Pharmaceuticals

See how ECOM supports pharmaceutical and medical supply chains.

Service

Fully Managed EDI

Have ECOM run your EDI connections, monitoring and partner changes.

General EDI flow

How EDI with Henry Schein typically works

This page does not include Henry Schein's EDI specification, so here is the general flow most buyers and suppliers follow. It describes common industry practice, not Henry Schein's requirements: the documents, their order and the timing vary by partner and program.

  1. 850 Purchase order

    From Henry Schein

    The buyer sends the order: items, quantities, prices, ship-to and requested dates.

  2. 855 Order acknowledgment

    From you to Henry Schein

    You confirm, change or reject the order, where the partner asks for it.

  3. 856 Advance ship notice

    From you to Henry Schein

    You tell the buyer what is on the shipment, with the carton and label details the buyer needs to receive it.

  4. 810 Invoice

    From you to Henry Schein

    You bill for what shipped, in the format the buyer's payables system expects.

  5. 997 Functional acknowledgment

    Both directions

    Each side confirms that every file it received was readable. A rejected file is corrected and resent.

From first contact to live orders

  1. Get the specification

    Ask Henry Schein for its EDI or API specification, usually through its supplier portal or onboarding contact.

  2. Choose the connection

    Agree how files move: AS2, SFTP, a VAN or an API, and how each side identifies itself.

  3. Map to your systems

    Map each document between the partner's format and your ERP, warehouse or order system.

  4. Test and certify

    Exchange test documents until the partner accepts them. Many partners require this before the first live order.

  5. Go live and monitor

    Start with live orders and watch every document, so a rejection is fixed before it becomes a late shipment or a deduction.

Need the specification?

Some trading partners keep their EDI and API specifications private and share them only with authorized suppliers, for security reasons. You are welcome to contact ECOM. We will see whether we can share the specification with you; each request is reviewed case by case, and sharing depends on the partner's rules. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your Henry Schein program

Each request goes to an ECOM EDI specialist with Henry Schein's name attached, so the reply starts from your program.

  • Review Henry Schein's requirements

    Send us Henry Schein's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect Henry Schein to your ERP

    Orders in, ship notices and invoices out, from the ERP and warehouse systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each Henry Schein document, then go live with monitoring from the first file.

    Plan testing and certification
  • Shipping labels and ASNs

    Labels and ship notices that match Henry Schein's rules, to help avoid receiving problems and compliance deductions.

    Review shipping compliance

Henry Schein integration FAQs

Does Henry Schein publish supplier EDI requirements?

We found no supplier EDI specification or onboarding page on Henry Schein's public website when we checked on 7 November 2026. Suppliers usually receive the requirements from Henry Schein during setup.

Which EDI documents do suppliers to Henry Schein usually exchange?

Suppliers to healthcare and laboratory distributors typically exchange the 850, 855, 856, 810, 867, 844, 849 documents listed on this page. That is general practice, not Henry Schein's published list; confirm the set with Henry Schein.

What is not yet known about EDI with Henry Schein?

Which EDI documents Henry Schein requires, the X12 version, the connection method, the testing steps and any labeling or compliance rules were not found in public sources.

Can ECOM help suppliers set up EDI with Henry Schein?

Yes. Once Henry Schein provides its requirements, ECOM can map, test and run the documents with your ERP. This page is an integration guide and does not indicate a partnership with Henry Schein.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. Henry Schein sets its own requirements and can change them at any time; your Henry Schein implementation guide, supplier portal or account contact is the authoritative source for your program.

Request Henry Schein integration assistance

Tell us about your Henry Schein program, documents and ERP. We will outline the connection, mapping and testing plan.