Manufacturing · Beauty, Personal Care and Household Products

EDI and API Integration for Haircare Product Manufacturers

Haircare brands sell through mass retailers, beauty chains and professional salon distributors, each with its own packs and programs. ECOM connects orders, item data, shipments and invoices to your ERP so retail and professional channels run side by side.

View all manufacturing industries

What this covers

Products and business models in haircare

Products

  • Shampoo, conditioner and treatments
  • Styling products and color
  • Professional salon sizes
  • Multipacks and promotional bundles

Business models

  • Mass-market brands
  • Professional salon brands via distributors
  • Private label haircare

Scenarios

Where haircare 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.

  • Retail versus professional channels

    The problem
    The same line can ship as retail packs and as professional sizes with different item numbers and rules.
    How ECOM helps
    ECOM keeps retail and professional item numbers apart in the ERP mapping for each customer type.
    What you gain
    The same line ships under the right item number and rules for each channel.

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

  • Promotional bundles

    The problem
    Bundles and value packs are created for retail events and need separate item handling.
    How ECOM helps
    ECOM maps bundle components to bundle items so promotional bundles order, ship and invoice as one item.
    What you gain
    Bundles do not break into the wrong components.

    Talk to an EDI/API Expert about promotional bundles Share a sample 850 Purchase Order and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Shade and formula variants

    The problem
    Hair color and treatments have many variants that must match retailer item data.
    How ECOM helps
    ECOM maps shade and formula variants to retailer item data.
    What you gain
    Variant orders post without manual lookup.

    Talk to an EDI/API Expert about shade and formula 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.

Who you connect with

Trading relationships for haircare product manufacturers

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

Mass, drug and beauty retailers
Order retail packs.
Professional beauty distributors
Order salon sizes and color.
Online retailers
Order for direct shipment.
Contract fillers
Fill product.
Packaging suppliers
Bottles, pumps and cartons.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for haircare 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 beauty distributor 832 Price/Sales Catalog Retail and professional sizes with separate item numbers.
  2. Retailer or beauty distributor→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  3. Retailer or beauty distributor→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  4. Your plant and ERP→Retailer or beauty distributor 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 beauty distributor 856 Advance Ship Notice Describes what is shipping, how it is packed and how it is labeled.
  6. Your plant and ERP→Retailer or beauty distributor 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  7. Retailer or beauty distributor→Your plant and ERP 852 Product Activity Data Sales and inventory data from the customer, used for replenishment and planning.
  8. Retailer or beauty distributor→Your plant and ERP 867 Product Transfer and Resale Report Salon-distributor resale reporting, where provided.
  9. Your plant and ERP→Contract filler or packaging supplier 850 Purchase Order Purchase orders for components and contract-filled product with quantities and requested delivery dates.
  10. Contract filler or packaging supplier→Your plant and ERP 856 Advance Ship Notice Packaging component and contract-filled shipments with quantity and lot, used to plan receiving and packing.
  1. Item data

    Item data (832) loads sizes, packs and bundles.

  2. Orders

    Orders (850) and changes (860) post by channel.

  3. Fill and pack

    Production and contract fill follow confirmed orders (855) and supplier notices (856).

  4. Ship notice

    The 856 describes cartons and bundles.

  5. Invoice and reporting

    The 810 follows; distributor sales reports (867/852) inform planning.

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 haircare product manufacturers
832 Price/Sales Catalog You send Retail and professional sizes with separate item numbers.
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.
852 Product Activity Data You receive Sales and inventory data from the customer, used for replenishment and planning.
867 Product Transfer and Resale Report You receive Salon-distributor resale reporting, where provided.
850 Purchase Order (supplier side) You send Purchase orders for components and contract-filled product with quantities and requested delivery dates.
856 Advance Ship Notice (supplier side) You receive Packaging component and contract-filled shipments with quantity and lot, used to plan receiving and packing.

Other exchanges you may meet

  • Distributor 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

Two channels, one line

A distributor ordering salon sizes and a mass retailer ordering retail packs need different item numbers, prices and ship rules from one ERP. Mapping each channel separately keeps them from mixing.

  • 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
  • Warehouse management
  • Distributor portals
  • 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 beauty distributor, and agree which documents, versions and data are in scope.

  2. Map to your systems

    Map each document to the fields in your ERP 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 haircare product manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Salon size ordered by a retail customerA channel mismatch can be held for review.
Bundle quantity not matched to componentsA bundle order whose components do not match in the ERP can be held for review before the pick.

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

Can salon distributors without EDI participate?

Often, via browser or files, so a brand need not require EDI of every distributor.

How are bundles represented?

As their own items with defined components in your ERP. The order and ship notice use the bundle item the retailer set up.

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 haircare 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.