Manufacturing · Beauty, Personal Care and Household Products

EDI and API Integration for Household and Commercial Cleaning Product Manufacturers

Cleaning product makers sell retail packs to mass and grocery retailers and concentrates and commercial sizes to janitorial distributors. ECOM connects both channels’ orders, shipments and invoices to your ERP so retail and professional product lines stay distinct.

View all manufacturing industries

What this covers

Products and business models in household and commercial cleaning product

Products

  • Household sprays, wipes and cleaners
  • Commercial and janitorial products
  • Concentrates and dispensed systems
  • Paper and disposable cleaning supplies

Business models

  • Brands for retail
  • Professional brands via janitorial distributors
  • Private label and contract fill

Scenarios

Where household and commercial cleaning 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 and professional split

    The problem
    Retail and janitorial customers use different item numbers, pack sizes and ordering behavior.
    How ECOM helps
    ECOM maintains separate item numbers, pack sizes and ordering rules for retail and janitorial customers.
    What you gain
    Both channels run through one ERP with the right item for each.

    Talk to an EDI/API Expert about retail and professional split 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.

  • Dispensed systems and programs

    The problem
    Concentrate programs tie product to dispensers and service, with orders from program managers.
    How ECOM helps
    ECOM maps program and dispenser references on orders from program managers to ERP items.
    What you gain
    Program orders post with the dispenser and service reference intact.

    Talk to an EDI/API Expert about dispensed systems and programs Share a sample 850 Purchase Order and 810 Invoice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Wide SKU catalogs

    The problem
    Large catalogs mean distributors depend on frequent item and price updates.
    How ECOM helps
    ECOM sends item and price updates (832, 846) to distributors that accept them.
    What you gain
    Distributors order from a current catalog.

    Talk to an EDI/API Expert about wide SKU catalogs Share a sample 832 Price/Sales Catalog and 846 Inventory Inquiry/Advice, or describe what goes wrong, and we will show how it would map to your ERP.

Who you connect with

Trading relationships for household and commercial cleaning product manufacturers

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

Mass and grocery retailers
Order retail packs on promotion cycles with item setup and label rules.
Janitorial and sanitation distributors
Order commercial sizes and concentrates, and depend on current catalogs and prices.
Facility service providers
Order through program managers for the buildings they service.
Chemical, bottle and trigger suppliers
Supply materials; late bottle or trigger shipments stop filling lines.
Carriers and 3PLs
Move pallets and mixed loads to distributor branches and retailer DCs.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for household and commercial cleaning 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 janitorial distributor 832 Price/Sales Catalog Catalog and price updates for distributor item numbers.
  2. Retailer or janitorial distributor→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  3. Retailer or janitorial 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 janitorial 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 janitorial 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 janitorial distributor 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  7. Your plant and ERP→Retailer or janitorial distributor 846 Inventory Inquiry/Advice Inventory advice to distributors.
  8. Your plant and ERP→Component supplier 850 Purchase Order Purchase orders for chemicals, bottles and closures with quantities and requested delivery dates.
  9. Component supplier→Your plant and ERP 856 Advance Ship Notice Chemical, bottle and closure shipments with quantity and lot, used to plan receiving and blending.
  1. Catalog and prices

    Item and price data (832) keep distributor catalogs current.

  2. Orders by channel

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

  3. Source materials

    Orders (850) and notices (856) to suppliers.

  4. Ship notice

    The 856 describes cartons and pallets.

  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 household and commercial cleaning product manufacturers
832 Price/Sales Catalog You send Catalog and price updates for distributor 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.
846 Inventory Inquiry/Advice You send Inventory advice to distributors.
850 Purchase Order (supplier side) You send Purchase orders for chemicals, bottles and closures with quantities and requested delivery dates.
856 Advance Ship Notice (supplier side) You receive Chemical, bottle and closure shipments with quantity and lot, used to plan receiving and blending.

Other exchanges you may meet

  • Distributor portals and punch-out catalogs
  • 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 and large catalogs

Distributors rely on up-to-date catalogs and prices, and retailers on item data matched to planograms. Keeping the two channels’ item data separate in the ERP and in the integration avoids cross-channel errors.

  • 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 janitorial 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 household and commercial cleaning product manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Distributor price differs from ERPA price mismatch on an order can be held for review.
Item discontinued but still orderedThe line can be flagged for the account review team.

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 distributor catalogs be sent automatically?

Item and price documents can be sent to partners that accept them, so catalogs stay current without spreadsheets.

What about dispensed-program orders?

Program orders arrive from the program manager or distributor like other orders. Dispenser service is outside the integration.

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 household and commercial cleaning 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.