Healthcare and Pharmaceutical integration

Illumina EDI integration

How EDI and API integration with Illumina typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Illumina.

At a glance

Illumina integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Illumina program or a customer relationship.

Illustration of a hospital building, a pill bottle and a medical cross, representing the healthcare and pharmaceutical industry that Illumina operates in.
Industry. Healthcare and Pharmaceutical: where Illumina operates.
Workflow diagram: your ERP and distribution systems exchange documents with Illumina through ECOM. You send 850, 860; you receive 855, 856, 810, 846; 997 acknowledgments go both ways. Your systems ERP · distribution · finance ECOM integration map · validate · connect · monitor Illumina 850 860 850 860 855 856 810 846 855 856 810 846 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Orders re-keyed by hand Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about Illumina

Tell us which documents you exchange with Illumina, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Illumina.

  • Review of Illumina's requirements with you, once you have them
  • EDI and API integration with your ERP and distribution systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
Illumina

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How Illumina integration fits your systems

Your systemsERP, distribution and accounting
ECOMMapping, validation, connectivity and monitoringAS2 or SFTP · EDI network (VAN) · API or web portal
IlluminaIts program, documents and requirements
  1. ConfirmConfirm your Illumina program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding Illumina integration

Who this is for: Laboratories, distributors and component suppliers that work with Illumina, and their order, inventory and finance teams.

Scope: Written for customers and distributors that buy from Illumina; 850 and 810 are named on Illumina's own EDI page, other documents are typical practice.

Illumina makes DNA sequencing and array technology. ECOM's directory lists it under genomics. Customers and suppliers of diagnostics and life sciences companies deal with reagents and instruments, lot and expiry information, cold-chain shipments and recurring orders.

Programs run by a diagnostics or life sciences company tend to add rules over time, so a setup that is easy to change and monitor is worth more than a one-time build. Illumina's own EDI or API specification is not part of this guide and no Illumina document was read: treat what follows as typical practice for a diagnostics or life sciences company, and confirm the documents, X12 version, delivery method and testing steps with Illumina.

ECOM maps the documents to your ERP and distribution systems, tests them with the trading partner, monitors every file after go-live and handles partner changes, as software, as a managed service or both.

Business scenarios

Where Illumina integration gets complicated

Typical requirements—confirm with your trading partner.

Cold-chain shipments

Temperature-sensitive shipments need accurate notices and clear exception handling.

How ECOM helps: ECOM builds the ship notice from your shipment data, checks it against the order and the label data before it is sent, and flags differences you can fix before the load leaves.

What you gain: Fewer receiving problems and compliance deductions caused by notices that do not match the load.

Reagents, lots and cold chain

Reagents and consumables are lot- and date-controlled and often cold-chain, so label, ship notice and storage data must agree.

How ECOM helps: ECOM maps item, price and pack data between your systems and Illumina's format and validates it before it is sent, so mismatches are caught on your side.

What you gain: Fewer rejections caused by data that does not match what Illumina has on file.

Instrument and consumable programs

Instruments and consumables may follow different order and billing rules.

How ECOM helps: ECOM maps invoice, payment and remittance data to your ERP or finance system and matches each document to the order or shipment it relates to, with differences listed for review.

What you gain: Faster reconciliation and cash application, and a clear trail for audit.

New product launch

A launch needs item, price and contract data in place across partners.

How ECOM helps: ECOM runs onboarding as a project: we confirm Illumina's requirements with you, map the documents, build the connection and run test cycles until Illumina accepts them.

What you gain: A shorter, more predictable path to the first accepted live document.

Workflows

Typical Illumina business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not Illumina's published process.

Order to cash

  1. 1Send 850 purchase order
  2. 2Receive 855 and 856
  3. 3Receive 810 invoice
  4. 4Reconcile payment

Standing orders

  1. 1Share forecast
  2. 2Send recurring orders
  3. 3Receive confirmation and ship notice
  4. 4Check lots and expiry at receipt

Documents and APIs

Illumina documents by program

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

DocumentNameDirectionProgramStatusPurpose
850 Purchase Order To Illumina Not stated General guidance Typically carries the order: items, quantities, prices, ship-to locations and requested dates.
855 Purchase Order Acknowledgment From Illumina Not stated General guidance Typically confirms an order, or reports changes to quantities, prices or dates.
856 Ship Notice/Manifest From Illumina Not stated General guidance Typically tells the receiver what is on each shipment, often with carton or pallet label details.
810 Invoice From Illumina Not stated General guidance Typically bills for what shipped, matched against the order.
846 Inventory Inquiry/Advice From Illumina Not stated General guidance Typically shares inventory positions or availability between the two sides.
860 Purchase Order Change Request - Buyer Initiated To Illumina Not stated General guidance Typically changes an order that is already placed.
997 Functional Acknowledgment Both directions Not stated General guidance Typically confirms that each file was received and could be read.

Connectivity

How companies connect

  • AS2 or SFTP

    Many companies exchange EDI files directly over AS2 or SFTP.

    General guidance

  • EDI network (VAN)

    Many suppliers connect through a value-added network that delivers files to and from the partner and keeps an audit trail.

    General guidance

  • API or web portal

    Some programs use REST or SOAP APIs, a supplier portal or a cloud EDI service for some documents. A login is usually required for portals.

    General guidance

Challenges

Common integration challenges

  • Lot and expiry

    Errors cause holds and returns. Confirm how it applies with Illumina.

  • Cold chain

    Exceptions need clear reporting. Details depend on your agreement with Illumina.

  • Standing orders

    Recurring orders need accurate updates. Ask Illumina how this applies to your program.

  • Item data

    Identifiers must match. Requirements vary by program.

  • Program-specific details

    The documents, identifiers, versions and test steps for your program are set by Illumina. ECOM works from them during mapping and testing.

Automation options for Illumina customers

Four ways to automate. One foundation.

ECOM helps you automate the orders you send and the acknowledgments, ship notices and invoices you receive, connect them to your systems, and see what needs action. Illumina sets its own requirements; ECOM reviews them with you and confirms which options fit.

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 Illumina documents to your ERP

ECOM connects the documents you exchange with Illumina to 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 healthcare and life sciences trading partners.

Solution

Supply Chain Visibility

See orders, shipments and exceptions across your trading partners in one view.

Service

Fully Managed EDI

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

General EDI flow

How EDI with Illumina typically works

The documents, their order and the timing are Illumina's to set; this is the general sequence most programs of this kind follow.

  1. 850 Purchase Order

    From you to Illumina

    Typically carries the order: items, quantities, prices, ship-to locations and requested dates.

  2. 855 Purchase Order Acknowledgment

    From Illumina to you

    Typically confirms an order, or reports changes to quantities, prices or dates.

  3. 856 Ship Notice/Manifest

    From Illumina to you

    Typically tells the receiver what is on each shipment, often with carton or pallet label details.

  4. 810 Invoice

    From Illumina to you

    Typically bills for what shipped, matched against the order.

  5. 846 Inventory Inquiry/Advice

    From Illumina to you

    Typically shares inventory positions or availability between the two sides.

  6. 860 Purchase Order Change Request - Buyer Initiated

    From you to Illumina

    Typically changes an order that is already placed.

  7. 997 Functional Acknowledgment

    Both directions

    Typically confirms that each file was received and could be read.

Need help with the specification?

Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your Illumina program

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

  • Review Illumina's requirements

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

    Request a requirements review
  • Connect Illumina to your ERP

    The documents you exchange, in and out of the ERP and operating systems you already run.

    Discuss ERP integration
  • Testing and certification

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

    Plan testing and certification

Illumina integration FAQs

Does Illumina use EDI?

Diagnostics and life sciences companies commonly use EDI with distributors and suppliers. This page does not include Illumina's requirements.

Can ECOM help with recurring orders?

Yes. ECOM maps orders, acknowledgments, ship notices and invoices between the partner's format and your ERP and monitors each file.

Which EDI documents are typical for a diagnostics or life sciences company?

Typical documents are 850, 855, 856, 810, 846, 860, 997. That is general practice, not Illumina's published list.

How does onboarding with Illumina usually work?

Typically you get the specification from the trading partner, agree the connection, map to your systems, test until the partner accepts the documents, then go live with monitoring. Timing depends on Illumina's requirements, test cycles and your ERP.

Does this guide mean Illumina endorses ECOM?

No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by Illumina.

Sources and accuracy

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

  • ASC X12: transaction set reference (standards body) Standards reference
  • Illumina: company description Background, not checked against a company source The one-sentence description of Illumina comes from general public knowledge and was not checked against Illumina's own website for this page.
  • Illumina: no company document read Background, not checked against a company source No Illumina supplier, customer or integration document was read for this page. Everything shown is typical practice for this type of company.

Request Illumina integration assistance

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