One platform, a separate isolated instance for every brand, one sign-in across the group, and portals that put thousands of suppliers and your wholesale customers on the same record as your team.
Run by Brand Collective, Retail Apparel Group, Caprice and the Boardriders brands. See customer stories
Portfolios that run several labels, licences or channels on the platform.
Separate where brands need to be separate, shared where the group needs one view.
Each brand runs on its own instance with its own database, its own configuration and its own supplier list. Single sign-on carries one login across the instances a person is allowed into.
A licence register holds every trademark, licensor, term and royalty condition against the styles produced under it, with expiry alerts before a licence comes up for renewal.
Suppliers work in the supplier portal on the same orders, styles and approvals as your team, with chat, an activity feed, sustainability actuals and compliance submissions on the record. 3,500+ suppliers are connected today.
Buyers order in the customer portal with approval workflows, reorder with a diff of what changed, shopping lists and an asset library, all reading live style data.
Sell-through, weeks of supply, velocity and markdown simulation are calculated from the order and sales data in the instance, by colour, size and channel.
Audits, certifications, claims, the digital product passport, product carbon and Australian packaging reporting sit on the style and order, with supplier actuals accepted or returned line by line.
What IT, security and procurement teams ask for, and how it is set up.
The standard programme runs from kickoff to hypercare in six weeks. Each phase ends with a written sign-off, so nobody discovers in week five that the integration was never scoped.
What groups, licensors and IT teams ask before a demo.
Yes. Every brand runs on its own instance with its own database. Nothing is shared between tenants unless you choose to connect them.
Yes. Sign-in runs through the platform's cloud sign-in with multi-factor authentication, or through your identity provider, and the same session carries across the instances a person is allowed into.
Yes. A REST API with per-customer accounts and IP allowlisting, plus webhooks. API writes are recorded in History.
Six phases over six weeks is the standard. Integrations and data migration are scoped in week two and can extend the timeline. Each additional brand is provisioned as its own instance.
Yes. Send your questionnaire and it is returned completed with an architecture summary. Agreement, SLA terms and billing contacts are confirmed in week one.
3 Clicks, the Australian apparel technology company that builds and supports StyleChain. An implementation team roster is shared at kickoff and a consultant is on standby for the first production day.
Bring one brand's range and we will walk through how the instances, sign-in, portals and implementation would work for you.
Book a Demo60-minute walkthrough · no commitment