Built for multi-brand retailers
Run several storefronts without juggling several tools
One catalog, per-brand pricing, shared customer records — plus a REST API and webhooks for when your stack gets opinionated.
What we hear
The problems this solves
Each brand is a separate tool
Every new banner means another instance to configure, another seat to pay for, and another dataset to reconcile. Growth should get easier, not harder.
Shared customers, duplicate accounts
A buyer who shops two of your brands ends up with two logins, two address books, and two credit profiles. Every edit has to happen twice.
Per-brand overrides land in the code
Branding, VAT rules, shipping defaults — each tweak becomes a fork that your ops team can't self-serve. Engineering becomes the bottleneck for merchandising.
How Distribu helps
What you get on day one
One catalog, per-brand pricing
Products live once; prices and availability can override per brand or per buyer. Inventory counts reconcile across storefronts without a sync job.
Feature tour →Per-brand storefronts at your slugs
Each brand gets its own distribu.app/store/{slug} with its own look and its own buyer accounts. Staff manage all of them from one dashboard with scoped roles.
Storefront features →REST API + webhooks for your stack
Keep your existing PIM, OMS, or warehouse system as the source of truth, and use Distribu's API as the ordering + storefront layer. Twelve webhook events fire on every meaningful state change.
API reference →
“We had three storefronts on three platforms. Consolidating onto one catalog freed up half a person on my team — and my engineers stopped getting pinged for branding tweaks.”
- Brands consolidated
- 3 → 1
- Ops hours saved / mo
- ~40
Directional beta metric; swapped for a named customer as soon as we have one.
Ready to see it in your tenant?
Built for teams running a portfolio — not a single-brand shop or a marketplace.