Manufacturing · Beauty, Personal Care and Household Products

EDI and API Integration for Soap, Bath and Body Product Manufacturers

Soap, bath and body brands rely on scent variants, seasonal sets and a mix of mass, specialty and online channels. ECOM connects orders, item data, shipments and invoices to your ERP so scents, sets and seasons stay organized.

View all manufacturing industries

What this covers

Products and business models in soap, bath and body product

Products

  • Bar and liquid soap
  • Bath, shower and body care
  • Gift sets and seasonal collections
  • Hand sanitizer and personal wash

Business models

  • Mass and specialty brands
  • Small-batch and artisan brands scaling to retail
  • Private label and contract fill

Scenarios

Where soap, bath and body product manufacturers lose time and margin

Recurring problems for this kind of business, how ECOM connects the systems and documents involved, and what you gain. Bring your own example and we will work through it with you.

  • Scent and set variants

    The problem
    Scents multiply SKUs, and seasonal sets are assembled from them.
    How ECOM helps
    ECOM maps each scent to its retailer item and maps set components to the set item.
    What you gain
    Scent and set orders post correctly and a missing scent is held for review.

    Talk to an EDI/API Expert about scent and set variants Share a sample 832 Price/Sales Catalog and 850 Purchase Order, or describe what goes wrong, and we will show how it would map to your ERP.

  • Seasonal programs

    The problem
    Holiday and gifting programs concentrate orders and require early set planning.
    How ECOM helps
    ECOM exchanges early program orders and changes so set planning follows the retailer’s buy.
    What you gain
    Seasonal set components are planned from the orders, not afterwards.

    Talk to an EDI/API Expert about seasonal programs Share a sample 850 Purchase Order, 860 Purchase Order Change Request and 846 Inventory Inquiry/Advice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Growth from small to large accounts

    The problem
    Brands moving from small retailers to national chains face EDI requirements for the first time.
    How ECOM helps
    ECOM onboards a new national retailer with partner testing, mapping and validation before the first order.
    What you gain
    A first national retailer program starts with tested documents, not a trial order.

    Talk to an EDI/API Expert about growth from small to large accounts Share a sample 850 Purchase Order, 856 Advance Ship Notice and 810 Invoice, or describe what goes wrong, and we will show how it would map to your ERP.

Who you connect with

Trading relationships for soap, bath and body product manufacturers

Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.

Mass, drug and specialty retailers
Order seasonal sets and replenishment, with item setup required before the first order.
Online retailers
Order for direct shipment, often with strict ship-by windows.
Distributors and gift wholesalers
Resell to small shops that may order by portal, file or email rather than EDI.
Fragrance, container and carton suppliers
Supply components, including those needed to assemble seasonal sets.
3PLs and carriers
Pick, pack and ship sets and singles to retailer rules.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for soap, bath and body product manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.

  1. Your plant and ERP→Retailer or gift wholesaler 832 Price/Sales Catalog Scent, size and set data.
  2. Retailer or gift wholesaler→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  3. Retailer or gift wholesaler→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  4. Your plant and ERP→Retailer or gift wholesaler 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  5. Your plant and ERP→Retailer or gift wholesaler 856 Advance Ship Notice Describes what is shipping, how it is packed and how it is labeled.
  6. Your plant and ERP→Retailer or gift wholesaler 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  7. Your plant and ERP→Component supplier 850 Purchase Order Purchase orders for packaging and ingredient components with quantities and requested delivery dates.
  8. Component supplier→Your plant and ERP 856 Advance Ship Notice Component shipments with quantity and lot, used to plan receiving and the packing schedule.
  9. Your plant and ERP→Retailer or gift wholesaler 846 Inventory Inquiry/Advice Available inventory by scent.
  1. Item and set data

    Item data (832) covers scents, sizes and sets.

  2. Orders

    Orders (850) and changes (860) post to the ERP.

  3. Source components

    Component orders (850) and notices (856) support set assembly.

  4. Ship notice

    The 856 describes cartons.

  5. Invoice

    The 810 follows shipment.

EDI and API exchanges

The documents behind the workflow

X12 transaction sets typical for this workflow, with what each carries here. Select a code for the full transaction reference.

DocumentDirectionWhat it carries for soap, bath and body product manufacturers
832 Price/Sales Catalog You send Scent, size and set data.
850 Purchase Order You receive The customer order: items, quantities, prices, ship-to and requested dates.
860 Purchase Order Change Request You receive Changes to open orders: quantities, dates or cancellations.
855 Purchase Order Acknowledgment You send The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
856 Advance Ship Notice You send Describes what is shipping, how it is packed and how it is labeled.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
850 Purchase Order (supplier side) You send Purchase orders for packaging and ingredient components with quantities and requested delivery dates.
856 Advance Ship Notice (supplier side) You receive Component shipments with quantity and lot, used to plan receiving and the packing schedule.
846 Inventory Inquiry/Advice You send Available inventory by scent.

Other exchanges you may meet

  • Retailer vendor portals
  • GS1 carton labels

Where a trading partner offers an API, a portal or file exchange instead of EDI, ECOM scopes that connection alongside the EDI ones. Functional acknowledgments (997 or 999) report validation results, including rejection; they do not prove business acceptance or ERP posting. Which acknowledgments and business responses each partner expects is confirmed with that partner.

Operational detail

Scents, sets and first-time EDI

A growing brand often meets its first retailer EDI requirement while also scaling production. A managed approach to onboarding, testing and monitoring means the team is not learning X12 in the middle of a season.

  • Variants, sizes and multipacks

    Personal care and household lines have many shades, scents, sizes and multipacks. Item setup with retailers has to match what orders, ship notices and invoices carry.

  • Batch and date codes

    Many products carry batch or date codes. Where a customer asks for them on shipping documents, they come from the production or warehouse system.

  • Promotions and displays

    Retailers order promotional displays and seasonal sets that ship on specific dates. Orders and changes need to reach the plant in time.

Connected systems

Systems that send and receive this data

Documents are only useful when they reach the systems that run the business.

  • ERP or accounting system
  • Warehouse management
  • Ecommerce platform
  • Retailer portals

Onboarding and monitoring

From first requirement to daily exception handling

  1. Confirm the requirement

    Obtain each partner's implementation guide or specification, for example from your retailer or gift wholesaler, and agree which documents, versions and data are in scope.

  2. Map to your systems

    Map each document to the fields in your ERP or accounting system and warehouse management so the data posts without re-keying.

  3. Test with the partner

    Exchange test documents and review the results with the partner before go-live, including changes, cancellations and error cases, not only the simple order.

  4. Validate, acknowledge and monitor

    A 997 or 999 reports the validation result of the document as received, including rejection; it does not show that the business accepted the content or that your ERP posted it. Business responses are separate: an 855 for orders, an 824 for application errors. Monitoring can show what is late, missing or rejected, once it is set up with you.

  5. Resolve exceptions

    Which failures and late documents are watched, who is alerted and how each is resolved are agreed during onboarding. Rejected or unacknowledged documents can then go to the people who can fix them, with the document and the reason in view.

Example exceptions for soap, bath and body product manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Scent not available on a set orderAn order line for a scent with no available stock can be held for review before the set is committed.
First order from a new retailer fails validationValidation errors and their causes are shown during partner testing, before go-live.

Illustrative examples of exceptions a team in this industry may need to review. Each check compares data from your ERP, WMS, trading partner documents or scans, where those are available. Which conditions are checked, who is alerted and what happens next are configured with you during onboarding. This is not a screenshot of a live system or a list of built-in checks.

How ECOM helps

ECOM products and services that apply

Each partner connects in the way it can support. These products cover the connections and visibility manufacturers need most.

  • PRISM-EDI

    Exchange of schedules, orders, ship notices and invoices with customers and suppliers in X12 or EDIFACT, translated to and from your ERP.

  • PRISM-WebEDI

    Browser-based purchase orders, acknowledgments, ship notices and invoices for suppliers without EDI systems.

  • PRISM-SmartConvert

    Supplier confirmations, invoices and customer orders that arrive as PDFs, emails or scans converted into ERP-ready data.

  • PRISM-SCV

    Monitoring of transactions and exceptions across customer and supplier documents.

Frequently asked questions

We are a smaller brand. Can we still connect to national retailers?

Yes. ECOM supports businesses of different sizes, including options where ECOM manages the EDI work. Scope depends on the retailer and your systems.

Which ERPs or accounting systems do you connect?

See the ERP integration guides for the systems ECOM supports, and tell us what you run.

Do retailers send promotional and replenishment orders differently?

Often both arrive as purchase orders, but promotional orders are tied to dates and quantities that change. Retailer guides define how promotions, changes and cancellations are sent, and ECOM confirms the rules per partner.

Do you need our trading partner's implementation guide to start?

It helps, but you can start without one. Tell us who you trade with and which systems you run, and we will help obtain and review each partner's requirements. The guide, not this page, decides the exact documents, versions and rules for that partner.

Talk to an EDI/API expert about soap, bath and body product manufacturers

Share your trading partners, your ERP, a sample document or the problem that keeps recurring. A completed specification is not needed: a partner guide, a rejected document or a description of the issue is enough to start.