Manufacturing · Plumbing, Water, HVAC and Appliances

EDI and API Integration for Sink, Basin, Bathtub and Toilet Manufacturers

Sink, tub and toilet makers sell large, fragile ceramic, cast and acrylic products through plumbing wholesalers, home centers and builders. ECOM connects orders, pallet-level shipments, freight and invoices to your ERP so bulky goods ship with accurate documents and claims are traceable.

View all manufacturing industries

What this covers

Products and business models in sink, basin, bathtub and toilet

Products

  • Toilets and bidets
  • Sinks, basins and vanities
  • Bathtubs and shower bases
  • Commercial fixtures

Business models

  • Manufacturers selling to wholesalers and home centers
  • Builder and multifamily programs
  • Commercial fixtures through reps

Scenarios

Where sink, basin, bathtub and toilet 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.

  • Bulky, fragile freight

    The problem
    Breakage and freight claims are a regular cost; the shipment record is evidence.
    How ECOM helps
    ECOM builds the 856 at pallet and item level and connects delivery status (214) to your ERP.
    What you gain
    A damage claim can be traced to the pallet and item.

    Talk to an EDI/API Expert about bulky, fragile freight Share a sample 856 Advance Ship Notice and 214 Transportation Carrier Shipment Status Message, or describe what goes wrong, and we will show how it would map to your ERP.

  • Color and model matching

    The problem
    Fixtures in a bathroom must match in color and model.
    How ECOM helps
    ECOM holds an order whose color or model combination does not match a set for review.
    What you gain
    Mismatched pieces are caught on the order.

    Talk to an EDI/API Expert about color and model matching Share a sample 850 Purchase Order and 855 Purchase Order Acknowledgment, or describe what goes wrong, and we will show how it would map to your ERP.

  • Builder phases

    The problem
    Multifamily and builder programs order in phases.
    How ECOM helps
    ECOM carries builder phase releases through order changes (860) and acknowledgments.
    What you gain
    Phased orders follow the builder’s schedule.

    Talk to an EDI/API Expert about builder phases Share a sample 850 Purchase Order, 860 Purchase Order Change Request and 855 Purchase Order Acknowledgment, or describe what goes wrong, and we will show how it would map to your ERP.

Who you connect with

Trading relationships for sink, basin, bathtub and toilet manufacturers

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

Plumbing wholesalers
Order fixtures for contractors and builders, often in pallet quantities.
Home centers
Replenish stock models and colors under program rules.
Builders and multifamily developers
Order for developments in phases, usually through wholesalers.
Clay, resin and hardware suppliers
Supply the materials and fittings that fixtures are made from.
LTL and truckload carriers
Move bulky, fragile pallets, with claims depending on accurate shipment records.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for sink, basin, bathtub and toilet manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.

  1. Wholesaler or home center→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  2. Wholesaler or home center→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  3. Your plant and ERP→Wholesaler or home center 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  4. Your plant and ERP→Carrier 204 Motor Carrier Load Tender Tenders a truck shipment to a motor carrier.
  5. Carrier→Your plant and ERP 990 Response to a Load Tender The motor carrier’s acceptance or decline of the tender.
  6. Carrier→Your plant and ERP 214 Transportation Carrier Shipment Status Message Shipment status events from the motor carrier.
  7. Your plant and ERP→Wholesaler or home center 856 Advance Ship Notice Pallet and item detail that supports freight and damage claims.
  8. Your plant and ERP→Wholesaler or home center 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  9. Wholesaler or home center→Your plant and ERP 180 Return Merchandise Authorization and Notification Returns and breakage authorizations.
  10. Your plant and ERP→Wholesaler or home center 846 Inventory Inquiry/Advice Shares available inventory so the customer can order against it.
  1. Orders and phases

    Orders (850) and changes (860).

  2. Tender

    Tenders (204/990); status (214).

  3. Ship notice by pallet

    The 856 lists pallets and items.

  4. Invoice

    The 810 follows.

  5. Damage and returns

    Return authorizations (180) track breakage claims.

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 sink, basin, bathtub and toilet manufacturers
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.
204 Motor Carrier Load Tender You send Tenders a truck shipment to a motor carrier.
990 Response to a Load Tender You receive The motor carrier’s acceptance or decline of the tender.
214 Transportation Carrier Shipment Status Message You receive Shipment status events from the motor carrier.
856 Advance Ship Notice You send Pallet and item detail that supports freight and damage claims.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
180 Return Merchandise Authorization and Notification You receive Returns and breakage authorizations.
846 Inventory Inquiry/Advice You send Shares available inventory so the customer can order against it.

Other exchanges you may meet

  • Wholesaler portals
  • Carrier claim portals

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

Fragile freight and claims

Ceramic and cast fixtures are heavy and break easily. Accurate pallet and item detail on the ship notice, matched to delivery status, supports freight claims when product arrives damaged, and color and model have to match across a bathroom set.

  • Warranty-related exchanges and returns

    Returns, replacements and warranty claims create documents and adjustments that follow the original sale.

  • Distributor and contractor channels

    Plumbing, HVAC and appliance products reach contractors through wholesale distributors, retailers and builders, each with its own order and item data.

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
  • Transportation management
  • Claim 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 wholesaler or home center, 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 sink, basin, bathtub and toilet manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Damage reported on deliveryPallet and item detail on the 856, with the delivery status, can help trace the item for a carrier claim.
Color or model mismatch on an orderThe line can be held for review so a bathroom set is not shipped with mismatched pieces.

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 freight claims be supported by the data?

The order, ship notice, delivery status and invoice are kept together for reference, which helps support a claim. The claim process itself stays with you and the carrier.

Are phased builder orders supported?

Yes, as releases against a program, in the way the customer sends them. ECOM scopes the release method with each builder or wholesaler.

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 sink, basin, bathtub and toilet 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.