Overview
Understanding Injinji integration
Who this is for: Factories, mills, trim suppliers and 3PLs that supply Injinji, and retailers and distributors that buy from Injinji, with the teams that run their orders.
Scope: This guide describes typical practice for this kind of trading relationship; Injinji's own program details are confirmed during onboarding.
Injinji is a Utah maker of toe socks for runners and hikers. It sells wholesale to running specialty stores and sporting goods chains. ECOM's directory lists it under Socks and hosiery.
Toe sock sizing and styles multiply SKUs, so size-level accuracy is key. Wholesale accounts such as running specialty stores and sporting goods chains usually publish routing, labeling and ship-window rules, and brands that sell through several accounts end up maintaining a different rule set for each. Typical practice is to keep that detail in one governed data set, so every document draws on the same source.
Injinji's own EDI or API specification is not part of this guide. What follows is typical practice for socks and hosiery, so confirm the documents, X12 version, delivery method and testing steps with Injinji'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.