Overview
Understanding Polygroup integration
Who this is for: Suppliers that supply Polygroup, 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; Polygroup's own program details are confirmed during onboarding.
Polygroup is an international maker of artificial trees, decorations and other seasonal products, supplying retailers directly and under private label. 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.
Private-label and branded seasonal products produced in Asia for retailers mean factory-to-retailer ship notices, ocean documents and retailer labeling rules are all 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. Polygroup's own EDI or API specification is not part of this guide and no Polygroup 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 Polygroup 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.