Overview
Understanding Jockey integration
Who this is for: Factories, mills, trim suppliers and 3PLs that supply Jockey, and retailers and distributors that buy from Jockey, with the teams that run their orders.
Scope: This guide describes typical practice for this kind of trading relationship; Jockey's own program details are confirmed during onboarding.
Jockey is a Wisconsin-based family-owned maker of underwear, sleepwear and activewear. It sells wholesale to department stores, mass merchants and online retailers and direct to consumers through its own website and stores. ECOM's directory lists it under Underwear and intimate apparel.
Underwear and basics carry deep size runs and many packaging formats, so UPC accuracy and pack configuration on the order, label and ship notice decide whether a carton can be received quickly. Wholesale accounts such as department stores, mass merchants and online 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.
Jockey's own EDI or API specification is not part of this guide. What follows is typical practice for underwear and intimate apparel, so confirm the documents, X12 version, delivery method and testing steps with Jockey'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.