Manufacturing · Plumbing, Water, HVAC and Appliances
EDI and API Integration for Ventilation, Ductwork and Air Filtration Manufacturers
Ventilation, ductwork and air filtration makers sell stock sizes and engineered products through HVAC distributors and contractors. ECOM connects orders, project releases, shipments and invoices to your ERP so sizes, ratings and project references stay accurate.
What this covers
Products and business models in ventilation, ductwork and air filtration
Products
- Ducts, fittings and registers
- Fans, ventilation and exhaust equipment
- Filters and air-quality products
- Commercial air handling components
Business models
- Manufacturers selling to HVAC distributors
- Engineered products for projects
- Filter replenishment programs
Scenarios
Where ventilation, ductwork and air filtration 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.
-
Size and rating variants
- The problem
- Filters and ducts come in many sizes and ratings.
- How ECOM helps
- ECOM maps size and rating variants to each distributor’s items and sends updates (832).
- What you gain
- Orders for a particular size and rating post correctly.
Talk to an EDI/API Expert about size and rating 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.
-
Project releases
- The problem
- Engineered products release against projects in phases.
- How ECOM helps
- ECOM carries project references on releases through acknowledgments, notices and invoices.
- What you gain
- Engineered products stay tied to their project.
Talk to an EDI/API Expert about project releases Share a sample 860 Purchase Order Change Request, 855 Purchase Order Acknowledgment and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.
-
Recurring filter replenishment
- The problem
- Filter programs reorder on cycles.
- How ECOM helps
- ECOM posts recurring filter orders as they arrive and matches quantities to the facility program.
- What you gain
- Filter programs reorder on cycle without manual entry.
Talk to an EDI/API Expert about recurring filter replenishment 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.
Who you connect with
Trading relationships for ventilation, ductwork and air filtration manufacturers
Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.
- HVAC distributors
- Order stock and project items, with project references on engineered products.
- Contractors
- Buy through distributors, often urgently.
- Facility managers and service companies
- Order recurring filter programs.
- Metal, media and motor suppliers
- Supply the sheet metal, filter media and fan motors products are made from.
- Carriers
- Deliver ducts, filters and equipment to branches and jobs.
Partner guides: Distributor guides · Carrier guides · Manufacturer guides
Typical workflow
Where ECOM connects your systems and trading partners
The pattern below is typical for ventilation, ductwork and air filtration manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.
- HVAC distributor→Your plant and ERP 850 Purchase Order Size, rating and project reference per line.
- HVAC distributor→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
- Your plant and ERP→HVAC distributor 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
- Your plant and ERP→Carrier 204 Motor Carrier Load Tender Tenders a truck shipment to a motor carrier.
- Carrier→Your plant and ERP 990 Response to a Load Tender The motor carrier’s acceptance or decline of the tender.
- Your plant and ERP→HVAC distributor 856 Advance Ship Notice Describes what is shipping, how it is packed and how it is labeled.
- Your plant and ERP→HVAC distributor 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
- Your plant and ERP→HVAC distributor 832 Price/Sales Catalog Catalog and rating updates.
- Your plant and ERP→HVAC distributor 846 Inventory Inquiry/Advice Shares available inventory so the customer can order against it.
Receive orders and releases
Orders (850) and project releases (860) post to the ERP by item, size and rating.
Confirm
Acknowledgments (855) restate sizes, ratings and dates.
Ship
Tenders (204/990) cover stock freight and project deliveries.
Send the ship notice
The 856 lists items and sizes by carton and pallet.
Invoice
The 810 follows shipment and carries the project reference.
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.
| Document | Direction | What it carries for ventilation, ductwork and air filtration manufacturers |
|---|---|---|
| 850 Purchase Order | You receive | Size, rating and project reference per line. |
| 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. |
| 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. |
| 832 Price/Sales Catalog | You send | Catalog and rating updates. |
| 846 Inventory Inquiry/Advice | You send | Shares available inventory so the customer can order against it. |
Other exchanges you may meet
- Distributor portals
- Project submittal 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
Sizes, ratings and projects
Ratings and sizes are the identity of filters and ducts. Project references on engineered orders should follow through acknowledgments, notices and invoices, and recurring filter programs need quantities that match what each facility actually installs.
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.
Sizes, configurations and bulky freight
Ductwork and air filters come in many sizes and configurations, and bulky freight makes the pallet and carton structure on the ship notice important.
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
- Distributor portals
ERP integration guides: SAP S/4HANA · Oracle NetSuite · Microsoft Dynamics 365 Business Central · Infor CloudSuite Industrial (SyteLine) · Epicor Prophet 21 · QAD MFG PRO · All ERP guides
Onboarding and monitoring
From first requirement to daily exception handling
Confirm the requirement
Obtain each partner's implementation guide or specification, for example from your HVAC distributor, and agree which documents, versions and data are in scope.
Map to your systems
Map each document to the fields in your ERP and warehouse management so the data posts without re-keying.
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.
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.
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 ventilation, ductwork and air filtration manufacturers
| Exception | Example handling, once configured |
|---|---|
| Filter rating on an order is not available | The line can be held for review so the wrong MERV or size is not substituted without the customer’s agreement. |
| Project release changed by the customer | A changed release can update the order, the 855 and the shipping plan. |
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.
Services: Trading partner onboarding · ERP integration · API integration · Fully managed EDI · Supply chain visibility · Mapping and translation
Frequently asked questions
Can filter replenishment be automated?
Replenishment orders from distributors or facilities arrive electronically and post to the ERP. The logic that triggers them lives in the customer’s systems.
How are project references handled?
Carried on the order and echoed on acknowledgments, ship notices and invoices, so engineered products stay tied to the project they were ordered for.
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 ventilation, ductwork and air filtration 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.