Yes. APIWORX connects Chewy EDI to your ERP.
But exchanging the documents is only the beginning. Chargebacks come from the process around them — the ASN that goes out after the truck left, the invoice that does not match the PO, the acknowledgment nobody watched.
APIWORX automates the whole supplier process for Chewy: purchase orders landing as orders in your ERP, inventory and acknowledgments going back, ASNs and labels produced from the actual shipment, invoices matched to the PO before they transmit, and exceptions surfaced to a person while there is still time to fix them.
Required EDI Documents
Chewy typically exchanges the following EDI transaction sets with suppliers. Each one carries its own compliance window and chargeback exposure.
Initiates the order cycle.
Buyer → Supplier
Confirms acceptance, partial acceptance, or rejection.
Supplier → Buyer
Detailed shipment manifest sent before delivery.
Supplier → Buyer
Electronic invoice requesting payment.
Supplier → Buyer
Confirms receipt and structural validity.
Both
POS and sales velocity data from retailer.
Buyer → Supplier
Chargeback Risk: Medium
Chewy enforces compliance with regular chargebacks but with somewhat more flexibility than the strictest retailers. ASN accuracy, invoice matching, and routing compliance are the most common triggers. Penalties are real but typically less severe than high-risk partners.
How APIWORX Automates Chewy Compliance
APIWORX runs the complete Chewy EDI flow end-to-end — connectivity, mapping, validation, transmission, and exception handling — and connects it to your ERP or order management system so nothing is re-keyed.