Manufacturing · Plumbing, Water, HVAC and Appliances

EDI and API Integration for Water Filtration and Treatment Equipment Manufacturers

Water filtration and treatment equipment makers sell systems and consumables through dealers, distributors, retailers and commercial projects. ECOM connects system orders, serial and configuration data, consumable reorders and invoices to your ERP.

View all manufacturing industries

What this covers

Products and business models in water filtration and treatment equipment

Products

  • Residential filtration and softeners
  • Commercial and industrial treatment systems
  • Replacement filters and media
  • Pumps, valves and controls

Business models

  • Manufacturers selling to dealers and distributors
  • Retail filtration products
  • Project-based commercial systems

Scenarios

Where water filtration and treatment equipment 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.

  • Systems plus consumables

    The problem
    Equipment sales create recurring filter and media orders.
    How ECOM helps
    ECOM processes consumable and media orders through the same connection as equipment and ties them to the installed base in your ERP.
    What you gain
    Recurring filter orders post without manual entry.

    Talk to an EDI/API Expert about systems plus consumables 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.

  • Configured and project-based systems

    The problem
    Commercial systems are configured to a site and delivered in phases.
    How ECOM helps
    ECOM maps configuration and project references on orders to the ERP and carries them to notices and invoices.
    What you gain
    Phased commercial systems stay tied to the project.

    Talk to an EDI/API Expert about configured and project-based systems 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.

  • Serial numbers and service

    The problem
    Installed systems are tracked for service.
    How ECOM helps
    ECOM carries serials onto the 856 and into the service system interface.
    What you gain
    Installed systems are linked to the shipment for service.

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

Who you connect with

Trading relationships for water filtration and treatment equipment manufacturers

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

Water treatment dealers
Order systems and filters, often with configuration details for the site.
Plumbing and industrial distributors
Resell equipment and consumables to contractors and facilities.
Retailers and online sellers
Order filters and cartridges that reorder on a cycle.
Component and media suppliers
Supply valves, pumps, membranes and filter media.
Carriers
Deliver systems and consumables to dealers, sites and homes.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for water filtration and treatment equipment manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.

  1. Dealer or distributor→Your plant and ERP 850 Purchase Order System configuration references and consumable quantities.
  2. Dealer or distributor→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  3. Your plant and ERP→Dealer or distributor 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  4. Your plant and ERP→Dealer or distributor 856 Advance Ship Notice Serial numbers for installed systems.
  5. Your plant and ERP→Dealer or distributor 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  6. Your plant and ERP→Dealer or distributor 846 Inventory Inquiry/Advice Shares available inventory so the customer can order against it.
  7. Dealer or distributor→Your plant and ERP 180 Return Merchandise Authorization and Notification Return authorization: which items and quantities are coming back and why.
  8. Your plant and ERP→Component supplier 850 Purchase Order Purchase orders for membranes, vessels, valves and pumps with quantities and requested delivery dates.
  9. Component supplier→Your plant and ERP 856 Advance Ship Notice Component shipments with quantity and the supplier’s lot or serial where provided, used to plan receiving ahead of assembly.
  1. Orders

    System and consumable orders (850), changes (860).

  2. Confirm configuration

    Acknowledgments (855) restate the configuration.

  3. Ship notice

    The 856 lists units, serials and cartons.

  4. Invoice

    The 810 follows.

  5. Replenish consumables

    Recurring orders and inventory advice (846).

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 water filtration and treatment equipment manufacturers
850 Purchase Order You receive System configuration references and consumable quantities.
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 Serial numbers for installed systems.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
846 Inventory Inquiry/Advice You send Shares available inventory so the customer can order against it.
180 Return Merchandise Authorization and Notification You receive Return authorization: which items and quantities are coming back and why.
850 Purchase Order (supplier side) You send Purchase orders for membranes, vessels, valves and pumps with quantities and requested delivery dates.
856 Advance Ship Notice (supplier side) You receive Component shipments with quantity and the supplier’s lot or serial where provided, used to plan receiving ahead of assembly.

Other exchanges you may meet

  • Dealer portals
  • Service systems outside the integration

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

Systems, serials and consumables

The system sold and its serial number anchor service and filter replacement later. Configuration references on the order should reach production, the packing list and the ship notice unchanged, and consumable reorders should refer to the installed system where the customer includes it.

  • Serial and model numbers

    Appliances and equipment are tracked by model and serial number. Where a customer or warranty process needs them, they travel with the shipment data.

  • 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 with configurators
  • Warehouse management
  • Service systems
  • Dealer 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 dealer or 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 with configurators 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 water filtration and treatment equipment manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Configuration on an order cannot be builtThe order can be held for engineering review so a system is not built to a configuration that does not exist.
Serial number missing on a shipped systemA required-field check can hold the shipment for review before the notice is sent, since service records depend on the serial.

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 recurring filter orders be automated?

Orders from dealers or retailers arrive electronically and post to the ERP without keying. Subscription logic or reminders live in your commerce or service systems, outside the integration.

Can commercial project deliveries be phased?

Yes, as releases against a project order, in the way the customer sends them.

Can serial numbers be reported on shipments?

Where a trading partner asks for serial numbers on the ship notice, they can be taken from your ERP or warehouse system and mapped into the document. Whether and how they are sent is set by the partner’s guide.

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 water filtration and treatment equipment 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.