Manufacturing · Furniture, Furnishings and Housewares
EDI and API Integration for Rug and Carpet Manufacturers
Rug and carpet makers sell area rugs, broadloom and carpet tile through retailers, distributors, flooring dealers and contract channels. ECOM connects orders, roll and size data, freight and invoices to your ERP so lots, dimensions and delivery details agree.
What this covers
Products and business models in rug and carpet
Products
- Area rugs and runners
- Broadloom carpet and carpet tile
- Rug pads and accessories
- Custom and made-to-order sizes
Business models
- Rug brands wholesale to retailers
- Carpet mills selling to distributors and contractors
- Online and direct
Scenarios
Where rug and carpet 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.
-
Dye lots and sizing
- The problem
- Carpet and rugs vary by dye lot, and customers need the same lot across an installation.
- How ECOM helps
- ECOM carries dye lot detail from your ERP onto the 856 and can hold an order that spans lots for review.
- What you gain
- Orders can be filled from one lot, or the lot split is flagged.
Talk to an EDI/API Expert about dye lots and sizing 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.
-
Large and awkward freight
- The problem
- Rolled and boxed rugs ship by LTL or parcel with distinct handling.
- How ECOM helps
- ECOM connects LTL and parcel tenders and status (204, 990, 214) to your ERP or TMS.
- What you gain
- Large and awkward freight is planned and tracked.
Talk to an EDI/API Expert about large and awkward freight Share a sample 204 Motor Carrier Load Tender, 990 Response to a Load Tender and 214 Transportation Carrier Shipment Status Message, or describe what goes wrong, and we will show how it would map to your ERP.
-
Custom sizes
- The problem
- Made-to-order rugs introduce long lead times and changing dates.
- How ECOM helps
- ECOM carries revised dates for made-to-order rugs from the ERP to the 855.
- What you gain
- Customers see the current ship date.
Talk to an EDI/API Expert about custom sizes Share a sample 855 Purchase Order Acknowledgment 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 rug and carpet manufacturers
Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.
- Home retailers and online sellers
- Order rugs.
- Flooring distributors and dealers
- Order carpet and tile.
- Contractors and designers
- Order for projects.
- Fiber and backing suppliers
- Supply materials.
- LTL and parcel carriers
- Move rolled goods.
Partner guides: Distributor guides · Retailer guides · Carrier guides
Typical workflow
Where ECOM connects your systems and trading partners
The pattern below is typical for rug and carpet manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.
- Retailer or flooring distributor→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
- Retailer or flooring distributor→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
- Your plant and ERP→Retailer or flooring distributor 855 Purchase Order Acknowledgment Dates for custom or made-to-order sizes.
- 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.
- Carrier→Your plant and ERP 214 Transportation Carrier Shipment Status Message Shipment status events from the motor carrier.
- Your plant and ERP→Retailer or flooring distributor 856 Advance Ship Notice Item, size and dye-lot detail where the customer asks.
- Your plant and ERP→Retailer or flooring distributor 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
Orders
Orders (850) and changes (860).
Acknowledge dates
Acknowledgments (855) state dates for custom pieces.
Tender
Freight tenders (204/990).
Ship notice with lot
The 856 lists items, sizes and dye lots where used.
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.
| Document | Direction | What it carries for rug and carpet 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 | Dates for custom or made-to-order sizes. |
| 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 | Item, size and dye-lot detail where the customer asks. |
| 810 Invoice | You send | Bills for what was shipped, tied to the order and the ship notice. |
Other exchanges you may meet
- Retailer drop-ship portals
- Distributor catalogs
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
Lots and sizes
Dye lots matter across a job. The lot on the ship notice should match the roll or box, and the size and unit of measure must agree across order and invoice.
Bulky freight and delivery
Large items ship by LTL or truckload, or to the home. Ship notices, carrier information and delivery appointments matter as much as the order.
Made-to-order and options
Finishes, fabrics and configurations create long lead times. Order changes and acknowledgments with promised dates are common.
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 Kinetic · Acumatica Cloud ERP · 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 retailer or flooring 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 rug and carpet manufacturers
| Exception | Example handling, once configured |
|---|---|
| Order spans two dye lots | An order line that cannot be filled from one dye lot can be flagged for review. |
| Custom size date slips | A promised date passing with no shipment confirmation can be flagged to customer service. |
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 dye-lot data be sent electronically?
Where the customer asks for it and your warehouse system captures it, dye-lot data can be mapped into the ship notice at the level the customer’s guide requires, so installers receive matching material.
Do carpet distributors use EDI?
Many do; others use portals or files. ECOM supports a mix, so you can serve both large flooring distributors and smaller dealers.
How are drop-ship orders for large items handled?
Online retailers and marketplaces send orders for direct shipment to the consumer and expect acknowledgments, tracking and invoices back. ECOM connects those orders to your ERP or warehouse and returns the shipment data the retailer requires.
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 rug and carpet 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.