Overview
Understanding Patagonia integration
Who this is for: Factories, mills, trim suppliers and 3PLs that supply Patagonia, and retailers and distributors that buy from Patagonia, with the teams that run their orders.
Scope: This guide describes typical practice for this kind of trading relationship; Patagonia's own program details are confirmed during onboarding.
Patagonia designs outdoor clothing and gear, with a repair and resale program for used garments. It sells wholesale to independent outdoor specialty shops and selected larger retailers and direct to consumers through its own stores and website. ECOM's directory lists it under Outdoor apparel.
Alongside new product, used garments come back through repair and resale channels, so returns, refurbished inventory and new-product orders have to be kept separate in inventory and invoicing data. Wholesale accounts such as independent outdoor specialty shops and selected larger retailers usually publish routing, labeling and ship-window rules, and brands that sell through several accounts end up maintaining a different rule set for each.
Patagonia's own EDI or API specification is not part of this guide. What follows is typical practice for outdoor apparel, so confirm the documents, X12 version, delivery method and testing steps with Patagonia's trading-partner team. ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications, as software, as a managed service or both.