Working with Chilewich
Design-led home textiles are sold to specialty retailers and the trade, so catalog data, seasonal collections and drop-ship orders matter.
What you gain: Fewer oversells and item-setup errors.
Manufacturing integration
How EDI and API integration with Chilewich typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Chilewich.
At a glance
The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Chilewich program or a customer relationship.
Tell us which documents you exchange with Chilewich, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Chilewich.
Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.
Integration and onboarding
Overview
Who this is for: Suppliers that supply Chilewich, and the retailers, designers and online sellers that buy from it, plus their order, warehouse and finance teams.
Scope: This guide describes typical practice for this kind of trading relationship; Chilewich's own program details are confirmed during onboarding.
Chilewich is a New York design company known for woven vinyl floor mats, placemats and other home textiles. Rug and floor covering makers sell through furniture and home retailers, online sellers, designers and dealers, with very large item counts by size, color and pattern and shipments that range from parcel to full truckload.
Design-led home textiles are sold to specialty retailers and the trade, so catalog data, seasonal collections and drop-ship orders matter. In this kind of program the points that usually matter are size-and-color item counts, parcel versus freight shipping, drop-ship to consumers and made-to-order lead times. Chilewich's own EDI or API specification is not part of this guide and no Chilewich document was read, so treat the document list and workflows below as typical practice for this type of company and confirm the documents, X12 version, delivery method and testing steps with Chilewich before you build.
ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications, and then monitors every file after go-live and handles partner changes, as software, as a managed service or both.
Business scenarios
Typical requirements—confirm with your trading partner.
Design-led home textiles are sold to specialty retailers and the trade, so catalog data, seasonal collections and drop-ship orders matter.
What you gain: Fewer oversells and item-setup errors.
Online sellers send single-rug orders that ship directly to the consumer, often by parcel.
How ECOM helps: ECOM connects drop-ship orders, tracking and invoices to your warehouse and ERP.
What you gain: Faster order flow and fewer late-tracking penalties.
Larger orders move by LTL or truckload and need accurate weights, labels and appointment data.
How ECOM helps: ECOM builds ship notices from your shipment data and connects status events to the order.
What you gain: Fewer delivery exceptions and compliance charges.
Workflows
Typical requirements—confirm with your trading partner. Typical flows in this industry, not Chilewich's published process.
Documents and APIs
General guidance. We could not verify Chilewich's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Chilewich's confirmed requirements. Confirm the list, versions and programs with Chilewich.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Document | Name | Direction | Program | Status | Purpose |
|---|---|---|---|---|---|
| 850 | Purchase Order | To Chilewich | If you buy from Chilewich | General guidance | Typically carries the order: items, quantities, prices, ship-to locations and requested dates. |
| 855 | Purchase Order Acknowledgment | From Chilewich | If you buy from Chilewich | General guidance | Typically confirms an order, or reports changes to quantities, prices or dates. |
| 860 | Purchase Order Change Request | To Chilewich | If you buy from Chilewich | General guidance | Typically changes quantities, dates or prices on an open order. |
| 856 | Ship Notice/Manifest | From Chilewich | If you buy from Chilewich | General guidance | Typically tells the receiver what is on each shipment, often with carton or pallet label details. |
| 810 | Invoice | From Chilewich | If you buy from Chilewich | General guidance | Typically bills for what shipped, matched against the order. |
| 846 | Inventory Inquiry/Advice | From Chilewich | If you buy from Chilewich | General guidance | Typically shares inventory positions or availability between the two sides. |
| 832 | Price/Sales Catalog | From Chilewich | If you buy from Chilewich | General guidance | Typically carries item, price and assortment data for a catalog or a line review. |
| 852 | Product Activity Data | To Chilewich | If you buy from Chilewich | General guidance | Typically reports sales or stock movement by item and location, where a program uses it. |
| 997 | Functional Acknowledgment | Both directions | If you buy from Chilewich | General guidance | Typically confirms that each file was received and could be read. |
| 850 | Purchase Order | From Chilewich | If you supply Chilewich | General guidance | Typically carries the order: items, quantities, prices, ship-to locations and requested dates. |
| 855 | Purchase Order Acknowledgment | To Chilewich | If you supply Chilewich | General guidance | Typically confirms an order, or reports changes to quantities, prices or dates. |
| 856 | Ship Notice/Manifest | To Chilewich | If you supply Chilewich | General guidance | Typically tells the receiver what is on each shipment, often with carton or pallet label details. |
| 810 | Invoice | To Chilewich | If you supply Chilewich | General guidance | Typically bills for what shipped, matched against the order. |
| 997 | Functional Acknowledgment | Both directions | If you supply Chilewich | General guidance | Typically confirms that each file was received and could be read. |
Connectivity
Many companies exchange EDI files directly over AS2 or SFTP.
General guidance
Many suppliers connect through a value-added network that delivers files to and from the partner and keeps an audit trail.
General guidance
Some programs use REST or SOAP APIs, a supplier portal or a cloud EDI service for some documents. A login is usually required for portals.
General guidance
Challenges
Size and color combinations multiply item records and updates.
Parcel, LTL and truckload each need different labels and documents.
Order acknowledgments need realistic dates.
Labeling and ASN rules differ by retailer.
The documents, identifiers, versions and test steps for your program are set by Chilewich. ECOM works from them during mapping and testing.
Automation options for Chilewich suppliers
ECOM helps you automate them, meet Chilewich's labeling and ship notice requirements, and see what needs action. Chilewich sets its program's rules; ECOM confirms which options fit yours.
Automate trading partner transactions and ERP integration through our iPaaS, SaaS, and EDI Team as a Service offerings.
Learn more about Fully Automated EDI/APIReceive orders and manage trading partner transactions through a browser-based portal, without requiring direct ERP integration.
Learn more about WebEDIConvert documents received through email or in PDF, Excel, Word, JPG, PNG, and other supported formats into structured data for automated processing, reducing manual data entry.
Learn more about SmartConvertAutomate repetitive order processing and transaction tasks in third-party portals such as SAP Ariba, Coupa, and other customer or supplier portals, reducing the work customer service representatives must log in and complete manually.
Learn more about WebConnectPRISM Supply Chain Automation Foundation
One platform beneath every option. Use one, or combine them for different partners and documents.
Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.
ECOM connects the documents you exchange with Chilewich to your ERP and warehouse systems, so orders post without re-keying and ship notices and invoices come from the data you already hold.
See how ECOM supports EDI for consumer goods makers selling to retailers.
SolutionRun drop-ship and marketplace orders from your own warehouse or ERP.
ServiceHave ECOM run your EDI connections, monitoring and partner changes.
Zero Trust for supplier data exchange
Supplier exchanges with Chilewich carry orders, ship notices, invoices and item data. A Zero Trust design assumes no connection, file or user is safe by default.
ECOM has implemented Zero Trust EDI and Zero Trust MFT in retail.
For supplier exchanges this means each supplier and vendor connection has its own scope, orders, ship notices and invoices are verified on arrival, late or altered files are noticed early, and the transfer log helps answer deduction and security-review questions.
Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.
Business outcome: A lost or reused credential affects one partner, not all of them.
Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.
Business outcome: A mistake or compromise in one account stays limited to what that account could reach.
Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.
Business outcome: Outside connections do not land directly on your internal systems.
Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.
Business outcome: Less exposure if a file is intercepted or a file store is reached.
Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.
Business outcome: Fewer outages caused by an expired certificate or key.
Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.
Business outcome: Late, missing or failed files are noticed early, before they hold up late shipments or deductions.
Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.
Business outcome: You can answer who sent what and when, for your own audits and partner reviews.
Each supplier, 3PL and vendor connection has its own account and limited scope, so one compromised credential cannot reach other partners' data.
Documents are verified when they arrive and every transfer is logged, so a missing or altered file shows up quickly.
Replace shared logins and open folders with named accounts, reviewed on a schedule you set.
Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. Chilewich may set its own security requirements, which come first.
Talk to an EDI/API Expert about Zero Trust Managed file transferSecure proxy and DMZ designSecurity at ECOM
General EDI flow
The documents, their order and the timing are Chilewich's to set; this is the general sequence most programs of this kind follow.
850 Purchase Order
From Chilewich to you
Typically carries the order: items, quantities, prices, ship-to locations and requested dates.
855 Purchase Order Acknowledgment
From you to Chilewich
Typically confirms an order, or reports changes to quantities, prices or dates.
856 Ship Notice/Manifest
From you to Chilewich
Typically tells the receiver what is on each shipment, often with carton or pallet label details.
997 Functional Acknowledgment
Both directions
Typically confirms that each file was received and could be read.
Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.
Next step
Each request goes to an ECOM EDI specialist with Chilewich's name attached, so the reply starts from your program.
Send us Chilewich's guide or your program details; we explain the documents, rules and options for meeting them.
Request a requirements reviewOrders in, ship notices and invoices out, from the ERP and warehouse systems you already run.
Discuss ERP integrationBuild, test and certify each Chilewich document, then go live with monitoring from the first file.
Plan testing and certificationLabels and ship notices that match Chilewich's rules, to help avoid receiving problems and compliance deductions.
Review shipping complianceCompanies of this type commonly exchange EDI or APIs with suppliers and customers. This page does not include Chilewich's requirements.
The documents differ. Suppliers usually receive orders or schedules and send ship notices and invoices; buyers usually send orders and receive acknowledgments, ship notices and invoices. This page shows both views.
Design-led home textiles are sold to specialty retailers and the trade, so catalog data, seasonal collections and drop-ship orders matter.
Typical documents are 850, 855, 860, 856, 810, 846, 832, 852, 997. That is general practice, not Chilewich's published list.
Typically you get the specification from the trading partner, agree the connection, map to your systems, test until the partner accepts the documents, then go live with monitoring. Timing depends on Chilewich's requirements, test cycles and your ERP.
No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by Chilewich.
This guide summarizes publicly available information as of November 2026. Chilewich sets its own requirements and can change them at any time; your Chilewich implementation guide, supplier portal or account contact is the authoritative source for your program.
Chilewich is a trademark of its owner. Its mention does not imply endorsement of, or a partnership with, ECOM Specialist.
Related integrations
How EDI and API integration with Surya typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Surya.
How EDI and API integration with The Rug Company typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with The Rug Company.
How EDI and API integration with Tufenkian Artisan Carpets typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Tufenkian Artisan Carpets.
How EDI and API integration with Annie Selke typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Annie Selke.
How EDI and API integration with Armadillo typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Armadillo.
How EDI and API integration with Brink & Campman typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Brink & Campman.
Tell us about your Chilewich program, documents and ERP. We will outline the connection, mapping and testing plan.