Healthcare and Pharmaceutical integration

Boston Scientific EDI integration

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

At a glance

Boston Scientific integration, in three pictures

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

Illustration of a hospital building, a pill bottle and a medical cross, representing the healthcare and pharmaceutical industry that Boston Scientific operates in.
Industry. Healthcare and Pharmaceutical: where Boston Scientific operates.
Workflow diagram: your ERP and distribution systems exchange documents with Boston Scientific through ECOM. You send 850, 867, 844; you receive 855, 856, 810, 846; 997 acknowledgments go both ways. Your systems ERP · distribution · finance ECOM integration map · validate · connect · monitor Boston Scientific 850 867 844 850 867 844 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 Boston Scientific

Tell us which documents you exchange with Boston Scientific, 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 Boston Scientific.

  • Review of Boston Scientific'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
Boston Scientific

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 Boston Scientific integration fits your systems

Your systemsERP, distribution and accounting
ECOMMapping, validation, connectivity and monitoringAS2 or SFTP · EDI network (VAN) · API or web portal
Boston ScientificIts program, documents and requirements
  1. ConfirmConfirm your Boston Scientific 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 Boston Scientific integration

Who this is for: Distributors, hospitals, group purchasing organizations and component suppliers that work with Boston Scientific, and their order and finance teams.

Scope: This guide describes typical practice for this kind of trading relationship; Boston Scientific's own program details are confirmed during onboarding.

Boston Scientific makes medical devices. ECOM's directory lists it under medical devices. Distributors and hospitals that buy from medical device makers, and the suppliers behind them, deal with item master accuracy, lot and serial data, contract pricing and consignment programs.

With a medical device or supply company, lot, contract and product identifiers have to match across orders, shipments and invoices, or documents are rejected. Boston Scientific's own EDI or API specification is not part of this guide and no Boston Scientific document was read: treat what follows as typical practice for a medical device or supply company, and confirm the documents, X12 version, delivery method and testing steps with Boston Scientific.

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 Boston Scientific integration gets complicated

Typical requirements—confirm with your trading partner.

Lot and serial tracking

Some products are tracked by lot or serial number for recalls and records.

How ECOM helps: ECOM connects shipment and status documents to your ERP, WMS or TMS and shows where each one stands, so late or missing messages are seen early.

What you gain: Teams see current status, and fewer shipments are held up by missing documents.

Item identifiers, lots and consignment

Medical products carry item identifiers, lot or serial data and often move under consignment or contract pricing.

How ECOM helps: ECOM maps item, price and pack data between your systems and Boston Scientific'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 Boston Scientific has on file.

Recalls and holds

A recall or hold needs lot data to reach every document and system quickly.

How ECOM helps: ECOM monitors each document and acknowledgment, flags rejected, late or mismatched ones and routes each exception to a named owner with the document history attached.

What you gain: Problems are corrected before they turn into deductions, write-offs or delayed payment.

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 Boston Scientific's requirements with you, map the documents, build the connection and run test cycles until Boston Scientific accepts them.

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

Workflows

Typical Boston Scientific business workflows

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

Order to cash

  1. 1Place 850 order
  2. 2Receive 855 and 856
  3. 3Receive goods and 810
  4. 4Reconcile and pay

Contract pricing

  1. 1Share price data
  2. 2Report sales with 867
  3. 3Request credit with 844
  4. 4Reconcile credits

Documents and APIs

Boston Scientific documents by program

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

DocumentNameDirectionProgramStatusPurpose
850 Purchase Order To Boston Scientific Not stated General guidance Typically carries the order: items, quantities, prices, ship-to locations and requested dates.
855 Purchase Order Acknowledgment From Boston Scientific Not stated General guidance Typically confirms an order, or reports changes to quantities, prices or dates.
856 Ship Notice/Manifest From Boston Scientific Not stated General guidance Typically tells the receiver what is on each shipment, often with carton or pallet label details.
810 Invoice From Boston Scientific Not stated General guidance Typically bills for what shipped, matched against the order.
846 Inventory Inquiry/Advice From Boston Scientific Not stated General guidance Typically shares inventory positions or availability between the two sides.
867 Product Transfer and Resale Report To Boston Scientific Not stated General guidance Typically reports product sold or transferred, so the maker can reconcile pricing and credits.
844 Product Transfer Account Adjustment To Boston Scientific Not stated General guidance Typically requests a credit or adjustment, such as a contract-price chargeback.
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

  • Item data

    Identifiers and pack levels must match. Confirm how it applies with Boston Scientific.

  • Lot and serial data

    Errors complicate traceability. Details depend on your agreement with Boston Scientific.

  • Contract pricing

    Price differences cause credits. Ask Boston Scientific how this applies to your program.

  • Consignment

    Consigned stock needs usage reports and invoices that reconcile.

  • Program-specific details

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

Automation options for Boston Scientific 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. Boston Scientific 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 Boston Scientific documents to your ERP

ECOM connects the documents you exchange with Boston Scientific 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

Medical Devices and Supplies

See how ECOM supports medical device makers and their channels.

Industry

Healthcare

See how ECOM supports healthcare and life sciences trading partners.

Service

Fully Managed EDI

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

General EDI flow

How EDI with Boston Scientific typically works

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

  1. 850 Purchase Order

    From you to Boston Scientific

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

  2. 855 Purchase Order Acknowledgment

    From Boston Scientific to you

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

  3. 856 Ship Notice/Manifest

    From Boston Scientific to you

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

  4. 810 Invoice

    From Boston Scientific to you

    Typically bills for what shipped, matched against the order.

  5. 846 Inventory Inquiry/Advice

    From Boston Scientific to you

    Typically shares inventory positions or availability between the two sides.

  6. 867 Product Transfer and Resale Report

    From you to Boston Scientific

    Typically reports product sold or transferred, so the maker can reconcile pricing and credits.

  7. 844 Product Transfer Account Adjustment

    From you to Boston Scientific

    Typically requests a credit or adjustment, such as a contract-price chargeback.

  8. 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 Boston Scientific program

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

  • Review Boston Scientific's requirements

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

    Request a requirements review
  • Connect Boston Scientific 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 Boston Scientific document, then go live with monitoring from the first file.

    Plan testing and certification

Boston Scientific integration FAQs

Does Boston Scientific use EDI?

Medical device and supply companies commonly use EDI with distributors and suppliers. This page does not include Boston Scientific's requirements.

Does EDI cover unique device identifiers?

EDI can carry item identifiers. Regulatory obligations are the company's own.

Which EDI documents are typical for a medical device or supply company?

Typical documents are 850, 855, 856, 810, 846, 867, 844, 997. That is general practice, not Boston Scientific's published list.

How does onboarding with Boston Scientific 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 Boston Scientific's requirements, test cycles and your ERP.

Does this guide mean Boston Scientific endorses ECOM?

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

Sources and accuracy

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

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

Request Boston Scientific integration assistance

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