Manufacturing integration

Unilever US EDI integration

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

At a glance

Unilever US integration, in three pictures

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

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

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

  • Review of Unilever US'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
Unilever US

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

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

Who this is for: Materials, packaging and logistics suppliers that supply Unilever US, and the retailers, distributors and online sellers that buy from it.

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

Unilever US is the U.S. arm of Unilever, a consumer goods company in food, beauty and home care. ECOM's directory lists it under consumer goods. Consumer products manufacturers buy materials and packaging on one side and sell through retailers, distributors and online channels on the other.

In practice, the hard part of working with a consumer products manufacturer is keeping orders, shipments and invoices consistent with each other. Unilever US's own EDI or API specification is not part of this guide and no Unilever US document was read: treat what follows as typical practice for a consumer products manufacturer, and confirm the documents, X12 version, delivery method and testing steps with Unilever US.

ECOM maps the documents to your ERP and warehouse 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 Unilever US integration gets complicated

Typical requirements—confirm with your trading partner.

Seasonal demand and promotions

Volumes shift with seasons and promotions. Forecast and order changes need to reach planning quickly.

How ECOM helps: ECOM runs the connection as a monitored service and watches queues and acknowledgments through busy periods, so a spike does not leave documents waiting.

What you gain: Busy periods run on the same process, without manual catch-up.

Multiple channels

Retail, club, e-commerce and distributor channels each have their own rules.

How ECOM helps: ECOM maps the documents to your systems and monitors every exchange, as software, as a managed service or both, so your team handles exceptions instead of re-keying.

What you gain: Less manual work and fewer surprises after go-live.

Multi-channel consumer products

Consumer products sell through retail, club, online and distributor channels, each with its own order and label rules, and promotions drive deductions.

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

Deductions and claims

Pricing and shipment differences become deductions that need clear documents to resolve.

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.

Workflows

Typical Unilever US business workflows

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

Supply side

  1. 1Receive schedule or order
  2. 2Confirm supply
  3. 3Ship and send 856
  4. 4Send 810 invoice

Sales side

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

Documents and APIs

Unilever US documents by program

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

DocumentNameDirectionProgramStatusPurpose
830 Planning Schedule with Release Capability From Unilever US If you supply Unilever US General guidance Typically gives forecasts and planned requirements by item and date.
862 Shipping Schedule From Unilever US If you supply Unilever US General guidance Typically gives firm shipping requirements, alone or alongside the planning schedule.
856 Ship Notice/Manifest To Unilever US If you supply Unilever US General guidance Typically tells the receiver what is on each shipment, often with carton or pallet label details.
810 Invoice To Unilever US If you supply Unilever US General guidance Typically bills for what shipped, matched against the order.
850 Purchase Order From Unilever US If you supply Unilever US General guidance Typically carries the order: items, quantities, prices, ship-to locations and requested dates.
855 Purchase Order Acknowledgment To Unilever US If you supply Unilever US General guidance Typically confirms an order, or reports changes to quantities, prices or dates.
997 Functional Acknowledgment Both directions If you supply Unilever US General guidance Typically confirms that each file was received and could be read.
850 Purchase Order To Unilever US If you buy from Unilever US General guidance Typically carries the order: items, quantities, prices, ship-to locations and requested dates.
855 Purchase Order Acknowledgment From Unilever US If you buy from Unilever US General guidance Typically confirms an order, or reports changes to quantities, prices or dates.
856 Ship Notice/Manifest From Unilever US If you buy from Unilever US General guidance Typically tells the receiver what is on each shipment, often with carton or pallet label details.
810 Invoice From Unilever US If you buy from Unilever US General guidance Typically bills for what shipped, matched against the order.
846 Inventory Inquiry/Advice From Unilever US If you buy from Unilever US General guidance Typically shares inventory positions or availability between the two sides.
852 Product Activity Data To Unilever US If you buy from Unilever US General guidance Typically reports sales or stock movement by item and location, where a program uses it.
867 Product Transfer and Resale Report To Unilever US If you buy from Unilever US General guidance Typically reports product sold or transferred, so the maker can reconcile pricing and credits.
860 Purchase Order Change Request - Buyer Initiated To Unilever US If you buy from Unilever US General guidance Typically changes an order that is already placed.

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

  • Channel variety

    Each channel adds its own documents and rules.

  • Item data

    Identifiers and pack data must match. Details depend on your agreement with Unilever US.

  • Deductions

    Short, late or mislabeled shipments cause chargebacks.

  • Forecast changes

    Plans change with promotions. Requirements vary by program.

  • Program-specific details

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

Automation options for Unilever US suppliers

Four ways to automate. One foundation.

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

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

Consumer Goods

See how ECOM supports consumer goods suppliers selling through retail channels.

Service

Fully Managed EDI

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

General EDI flow

How EDI with Unilever US typically works

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

The documents below belong to two different programs, so they are shown as two separate sequences, not one. Which one applies depends on your agreement with Unilever US.

Schedule-driven program

  1. 830 Planning Schedule with Release Capability

    From Unilever US to you

    Typically gives forecasts and planned requirements by item and date.

  2. 862 Shipping Schedule

    From Unilever US to you

    Typically gives firm shipping requirements, alone or alongside the planning schedule.

  3. 856 Ship Notice/Manifest

    From you to Unilever US

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

  4. 810 Invoice

    From you to Unilever US

    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.

  6. 856 Ship Notice/Manifest

    From Unilever US to you

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

  7. 810 Invoice

    From Unilever US to you

    Typically bills for what shipped, matched against the order.

  8. 846 Inventory Inquiry/Advice

    From Unilever US to you

    Typically shares inventory positions or availability between the two sides.

  9. 852 Product Activity Data

    From you to Unilever US

    Typically reports sales or stock movement by item and location, where a program uses it.

  10. 867 Product Transfer and Resale Report

    From you to Unilever US

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

Purchase-order program

  1. 850 Purchase Order

    From Unilever US to you

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

  2. 855 Purchase Order Acknowledgment

    From you to Unilever US

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

  3. 850 Purchase Order

    From you to Unilever US

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

  4. 855 Purchase Order Acknowledgment

    From Unilever US to you

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

  5. 860 Purchase Order Change Request - Buyer Initiated

    From you to Unilever US

    Typically changes an order that is already placed.

  6. 856 Ship Notice/Manifest

    From you to Unilever US

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

  7. 810 Invoice

    From you to Unilever US

    Typically bills for what shipped, matched against the order.

  8. 997 Functional Acknowledgment

    Both directions

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

  9. 856 Ship Notice/Manifest

    From Unilever US to you

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

  10. 810 Invoice

    From Unilever US to you

    Typically bills for what shipped, matched against the order.

  11. 846 Inventory Inquiry/Advice

    From Unilever US to you

    Typically shares inventory positions or availability between the two sides.

  12. 852 Product Activity Data

    From you to Unilever US

    Typically reports sales or stock movement by item and location, where a program uses it.

  13. 867 Product Transfer and Resale Report

    From you to Unilever US

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

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 Unilever US program

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

  • Review Unilever US's requirements

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

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

    Plan testing and certification
  • Shipping labels and ASNs

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

    Review shipping compliance

Unilever US integration FAQs

Does Unilever US use EDI?

Consumer products manufacturers commonly use EDI with suppliers and customers. This page does not include Unilever US's requirements.

Are you supplying Unilever US or buying from it?

The documents differ. Suppliers usually receive schedules or orders and send ship notices and invoices; buyers usually send orders and receive acknowledgments, ship notices and invoices.

Which EDI documents are typical for a consumer products manufacturer?

Typical documents are 830, 862, 856, 810, 850, 855, 997, 846, 852, 867, 860. That is general practice, not Unilever US's published list.

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

Does this guide mean Unilever US endorses ECOM?

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

Sources and accuracy

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

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

Request Unilever US integration assistance

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