Manufacturing · Beauty, Personal Care and Household Products

EDI and API Integration for Cosmetics and Skincare Manufacturers

Cosmetics and skincare brands sell hundreds of shade and size variants through beauty retailers, department stores and online channels. ECOM connects item setup, orders, ship notices and invoices to your ERP so variants, batches and display programs stay accurate.

View all manufacturing industries

What this covers

Products and business models in cosmetics and skincare

Products

  • Color cosmetics and skincare
  • Sun care and body care
  • Gift sets and seasonal collections
  • Testers, samples and display units

Business models

  • Brands selling to beauty and department retailers
  • Private label and contract fill for other brands
  • Brand sales online and wholesale

Scenarios

Where cosmetics and skincare 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.

  • Shade and size variants

    The problem
    Each shade, size and set is its own item, and retailers receive only what is set up.
    How ECOM helps
    ECOM maps each shade, size and set to its retailer item, and tests the item data with the retailer.
    What you gain
    Retailers receive and reorder only what is set up.

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

  • Testers, samples and displays

    The problem
    Non-sale items such as testers and displays ship with orders and need their own item handling.
    How ECOM helps
    ECOM handles testers, samples and displays as their own items on orders, notices and invoices.
    What you gain
    Non-sale items ship and bill as planned.

    Talk to an EDI/API Expert about testers, samples and displays 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.

  • Launch and promotion windows

    The problem
    New launches and gift sets have fixed on-shelf dates, so late orders or notices miss the window.
    How ECOM helps
    ECOM sets up launch and gift-set items early with the retailer and posts launch orders as they arrive.
    What you gain
    On-shelf dates are planned against orders instead of notices that arrive late.

    Talk to an EDI/API Expert about launch and promotion windows Share a sample 832 Price/Sales Catalog, 850 Purchase Order and 860 Purchase Order Change Request, or describe what goes wrong, and we will show how it would map to your ERP.

Who you connect with

Trading relationships for cosmetics and skincare manufacturers

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

Beauty specialty and department retailers
Order launches, replenishment and displays, with item setup due before the first order.
Online retailers and marketplaces
Order for direct shipment and expect fast acknowledgments and tracking.
Distributors
Serve salons, spas and international markets with their own item numbers.
Contract fillers and packaging suppliers
Fill product and supply bottles, pumps, cartons and displays on release schedules.
3PLs and carriers
Distribute to retailer DCs and to consumers, including gift-set and display shipments.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for cosmetics and skincare 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→Beauty or department retailer 832 Price/Sales Catalog Shade, size and set data before a launch.
  2. Beauty or department retailer→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  3. Beauty or department retailer→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  4. Your plant and ERP→Beauty or department retailer 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  5. Your plant and ERP→Beauty or department retailer 856 Advance Ship Notice Describes what is shipping, how it is packed and how it is labeled.
  6. Your plant and ERP→Beauty or department retailer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  7. Beauty or department retailer→Your plant and ERP 852 Product Activity Data Retail sales for replenishment and sell-through.
  8. Your plant and ERP→Contract filler or supplier 850 Purchase Order Fill and component purchase orders.
  9. Contract filler or supplier→Your plant and ERP 855 Purchase Order Acknowledgment The supplier confirms quantities and dates for ingredients, components and contract-filled product.
  10. Contract filler or supplier→Your plant and ERP 856 Advance Ship Notice Ingredient, component or contract-filled shipments with quantity and lot, used to plan receiving and the fill schedule.
  1. Item and launch setup

    Item data (832) loads shades, sizes and sets before launch.

  2. Orders and promotion changes

    Orders (850) and changes (860) post to the ERP with display and tester quantities.

  3. Buy and fill

    Orders to contract fillers and component suppliers (850) with their notices (856).

  4. Ship notice

    The 856 describes cartons with batch information where asked.

  5. Invoice

    The 810 follows shipment; promotions and allowances are researched against the order.

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 cosmetics and skincare manufacturers
832 Price/Sales Catalog You send Shade, size and set data before a launch.
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 Retail sales for replenishment and sell-through.
850 Purchase Order (supplier side) You send Fill and component purchase orders.
855 Purchase Order Acknowledgment (supplier side) You receive The supplier confirms quantities and dates for ingredients, components and contract-filled product.
856 Advance Ship Notice (supplier side) You receive Ingredient, component or contract-filled shipments with quantity and lot, used to plan receiving and the fill schedule.

Other exchanges you may meet

  • GS1 item data via GDSN or retailer portals
  • GS1-128 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

Shades, batches and launches

A launch depends on item data, packaging and inventory arriving at each retailer on time. Batch or lot codes on shipping documents let the retailer and brand trace affected units; the codes come from production.

  • 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
  • Retailer portals
  • Contract manufacturer systems

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 beauty or department retailer, 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 cosmetics and skincare manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Launch item not yet set up at a retailerAn order line for an unset-up shade can be held for review.
Component shipment late for a fill dateA late supplier 856 or missing confirmation can be flagged to purchasing against the fill date.

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

How are testers and displays handled on orders?

They are separate items on the order and ship notice, with their own item numbers. ECOM maps them as the retailer defines.

Does ECOM support cosmetics regulatory requirements?

Regulatory and labeling obligations remain with your regulatory team. The integration carries the item, batch and shipment data that partners agree to exchange.

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 cosmetics and skincare 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.