Overview
Understanding Twinkly integration
Who this is for: Suppliers that supply Twinkly, and the retailers, distributors and gift shops that buy from it, plus their order, warehouse and finance teams.
Scope: This guide describes typical practice for this kind of trading relationship; Twinkly's own program details are confirmed during onboarding.
Twinkly is a maker of smart, app-controlled decorative lights sold by retailers and online. Holiday and seasonal product makers ship most of their volume in a short window, so preseason orders, import shipping dates, order changes and delivery deadlines drive nearly everything.
Consumer electronics-style product with seasonal demand means retailer orders, import shipments and serial or lot detail may all be part of the flow. In this kind of program the points that usually matter are preseason order books, import shipping windows, store-ready labeling and compressed delivery deadlines. Twinkly's own EDI or API specification is not part of this guide and no Twinkly 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 Twinkly 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.