Manufacturing integration

SunOpta EDI integration

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

At a glance

SunOpta integration, in three pictures

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

Illustration of a factory with a conveyor carrying boxes, representing the manufacturing industry that SunOpta operates in.
Industry. Manufacturing: where SunOpta operates.
Workflow diagram: your ERP and warehouse systems exchange documents with SunOpta through ECOM. You send 855, 856, 810; you receive 850; 997 acknowledgments go both ways. Your systems ERP · warehouse · finance ECOM integration map · validate · connect · monitor SunOpta 855 856 810 855 856 810 850 850 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 SunOpta

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

  • Review of SunOpta's requirements with you, once you have them
  • EDI and API integration with your ERP and warehouse 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
SunOpta

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

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

Who this is for: Suppliers that supply SunOpta, and the retailers and foodservice buyers that buy from it, plus their order, warehouse and finance teams.

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

SunOpta is a North American maker of plant-based foods and beverages, producing much of it for customers and retail brands. Dairy and chilled products are short-dated and temperature controlled, so orders, ship notices and invoices have to reflect exactly what shipped, with lot and date data and tight delivery windows.

Co-packed and private-label plant-based drinks ship to retailers and brand owners, so documents follow each customer program rather than one house standard. In this kind of program the points that usually matter are short shelf life, cold-chain delivery windows, lot and date codes and retailer fill-rate scoring. SunOpta's own EDI or API specification is not part of this guide and no SunOpta document was read, so treat the document list and workflows below as typical practice for this type of company and confirm the documents, X12 version, delivery method and testing steps with SunOpta before you build.

ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications, and then monitors every file after go-live and handles partner changes, as software, as a managed service or both.

Business scenarios

Where SunOpta integration gets complicated

Typical requirements—confirm with your trading partner.

Working with SunOpta

Co-packed and private-label plant-based drinks ship to retailers and brand owners, so documents follow each customer program rather than one house standard.

How ECOM helps: ECOM connects orders, acknowledgments, ship notices and invoices to your ERP and warehouse systems and flags late or missing documents early.

What you gain: Fewer missed delivery windows and fill-rate penalties.

Lot, date and traceability

Retail and foodservice customers expect lot and best-by data on shipment documents and labels.

How ECOM helps: ECOM builds the ship notice from your shipment data and checks it against the order and label data before it is sent.

What you gain: Fewer receiving problems and recall-trace gaps.

Milk, ingredient and packaging supply

Milk, cultures, packaging and film arrive on a schedule and must be received against plan.

How ECOM helps: ECOM connects supplier orders, ship notices and invoices to your ERP so inbound deliveries are visible against the production plan.

What you gain: Fewer plant stoppages caused by late or unmatched deliveries.

Workflows

Typical SunOpta business workflows

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

Retailer orders

  1. 1Receive 850 order
  2. 2Confirm with 855
  3. 3Ship with lot and date
  4. 4Send 856 and 810

Supply side

  1. 1Receive PO or schedule
  2. 2Confirm supply
  3. 3Ship with lot data
  4. 4Invoice with 810

Documents and APIs

SunOpta documents by program

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

DocumentNameDirectionProgramStatusPurpose
850 Purchase Order To SunOpta If you buy from SunOpta General guidance Typically carries the order: items, quantities, prices, ship-to locations and requested dates.
855 Purchase Order Acknowledgment From SunOpta If you buy from SunOpta General guidance Typically confirms an order, or reports changes to quantities, prices or dates.
856 Ship Notice/Manifest From SunOpta If you buy from SunOpta General guidance Typically tells the receiver what is on each shipment, often with carton or pallet label details.
810 Invoice From SunOpta If you buy from SunOpta General guidance Typically bills for what shipped, matched against the order.
846 Inventory Inquiry/Advice From SunOpta If you buy from SunOpta General guidance Typically shares inventory positions or availability between the two sides.
852 Product Activity Data To SunOpta If you buy from SunOpta General guidance Typically reports sales or stock movement by item and location, where a program uses it.
820 Payment Order/Remittance Advice To SunOpta If you buy from SunOpta General guidance Typically explains what a payment covers, so cash can be applied to the right invoices and deductions.
997 Functional Acknowledgment Both directions If you buy from SunOpta General guidance Typically confirms that each file was received and could be read.
850 Purchase Order From SunOpta If you supply SunOpta General guidance Typically carries the order: items, quantities, prices, ship-to locations and requested dates.
855 Purchase Order Acknowledgment To SunOpta If you supply SunOpta General guidance Typically confirms an order, or reports changes to quantities, prices or dates.
856 Ship Notice/Manifest To SunOpta If you supply SunOpta General guidance Typically tells the receiver what is on each shipment, often with carton or pallet label details.
810 Invoice To SunOpta If you supply SunOpta General guidance Typically bills for what shipped, matched against the order.
997 Functional Acknowledgment Both directions If you supply SunOpta 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

  • Cold-chain delivery

    Delivery windows and temperature requirements drive documents and appointments.

  • Lot and date accuracy

    Dates and lots on ship notices must match the product delivered.

  • Fill-rate scoring

    Retailers measure on-time and in-full; short ships cost money.

  • Private-label and brand programs

    Different customers can require different label and document rules.

  • Program-specific details

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

Automation options for SunOpta suppliers

Four ways to automate. One foundation.

ECOM helps you automate them, meet SunOpta's labeling and ship notice requirements, and see what needs action. SunOpta 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 SunOpta documents to your ERP

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

Food and Beverage

See how ECOM supports EDI for food and beverage suppliers and buyers.

Service

Fully Managed EDI

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

Zero Trust for EDI and file transfer

Zero Trust EDI and MFT for your SunOpta connection

Exchanges with SunOpta move business documents between your systems and an outside party. A Zero Trust design assumes no connection, file or user is safe by default.

  • Authentication

    Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.

    Business outcome: A lost or reused credential affects one partner, not all of them.

  • Least privilege

    Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.

    Business outcome: A mistake or compromise in one account stays limited to what that account could reach.

  • Isolation

    Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.

    Business outcome: Outside connections do not land directly on your internal systems.

  • Encryption

    Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.

    Business outcome: Less exposure if a file is intercepted or a file store is reached.

  • Certificate and key management

    Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.

    Business outcome: Fewer outages caused by an expired certificate or key.

  • Monitoring and access controls

    Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.

    Business outcome: Late, missing or failed files are noticed early, before they hold up payment, shipping or reporting.

  • Audit trail

    Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.

    Business outcome: You can answer who sent what and when, for your own audits and partner reviews.

What this means for your data

Partner access

Each trading partner connects with its own identity and a limited scope, and any connection can be reviewed or removed on its own.

File and document handling

Documents are verified when they arrive and every transfer is logged.

Exceptions

Late, missing or rejected files raise an alert and go to a named owner.

Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. SunOpta may set its own security requirements, which come first.

General EDI flow

How EDI with SunOpta typically works

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

  1. 850 Purchase Order

    From SunOpta to you

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

  2. 855 Purchase Order Acknowledgment

    From you to SunOpta

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

  3. 856 Ship Notice/Manifest

    From you to SunOpta

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

  4. 810 Invoice

    From you to SunOpta

    Typically bills for what shipped, matched against the order.

  5. 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 SunOpta program

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

  • Review SunOpta's requirements

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

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

    Plan testing and certification
  • Shipping labels and ASNs

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

    Review shipping compliance

SunOpta integration FAQs

Does SunOpta use EDI?

Companies of this type commonly exchange EDI or APIs with suppliers and customers. This page does not include SunOpta's requirements.

Are you supplying SunOpta or buying from it?

The documents differ. Suppliers usually receive orders or schedules and send ship notices and invoices; buyers usually send orders and receive acknowledgments, ship notices and invoices. This page shows both views.

What is different about working with SunOpta?

Co-packed and private-label plant-based drinks ship to retailers and brand owners, so documents follow each customer program rather than one house standard.

Which EDI documents are typical for this kind of company?

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

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

Does this guide mean SunOpta endorses ECOM?

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

Sources and accuracy

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

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

Request SunOpta integration assistance

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