Multi-store
A single DZBuild account can own multiple stores. Each store has its own products, orders, customers, theme, and domain — but you sign in once and switch between them in the dashboard.
Multi-store is a Unlimited (slug unlimited) feature. Free and Pro accounts are limited to a single store. Upgrade from /dashboard/subscribe — the ▶ How to renew button on that page launches a guided in-app tour, and video walkthroughs are on the DZBuild YouTube channel.
When to use multi-store
| Use case | Example |
|---|---|
| Different brands | "Brand A" and "Brand B" with separate themes and audiences |
| Different categories | Fashion + Electronics on separate storefronts |
| Different markets | Algeria-only and international, with different couriers / currencies |
| Test sandbox | Try a new theme or product strategy without touching your live store |
If you just want a multilingual storefront, install the Multi-Language add-on — that's a single store with multiple languages, simpler than running two stores.
Creating an additional store
Open the store-picker at the top of the dashboard sidebar → Create new store. Walk through the same flow as your first store. The new store is provisioned in seconds and you're switched into it.
Switching between stores
Click the store-picker → pick another store. The dashboard reloads in that store's context — products, orders, settings all flip to the new store.
Important: every dashboard mutation (saving a product, updating shipping rates, editing a domain) carries the active store's store_id server-side. The active store is determined from your dashboard session — switch to the right one before making changes.
Shared vs. per-store
| Shared across all your stores | Per-store |
|---|---|
| Login, password, 2FA | Products, categories, orders, customers |
| Subscription plan tier | Theme + branding + custom CSS |
| Team members (with per-store roles) | Domains, payment methods, courier integrations |
| Billing receipts | API keys |
| Account-level email + name | Pixels, abandoned cart settings |
| AI credits balance | Add-on activations |
The subscription plan applies at the account level — if you're on Pro, all your stores are Pro. The per-store usage caps still apply per store.
Team members across stores
When you invite a team member at /dashboard/team, you can grant them access to specific stores with per-store roles. A "Manager" on Store A can be "Read-only" on Store B and absent from Store C.
API and multi-store
Each store has its own API keys. There is no cross-store endpoint — operate one store at a time. To work with both stores from a script, generate a key per store and authenticate per-call. See API authentication.
Multi-store gotchas
- Server-side
store_id: every dashboard mutation must carry the active store. If a stale browser tab somehow submits a request with the wrong store, the server still validates ownership before applying the change. JS-only validation is not enough — server enforcement matters here. - AI credits are per account, but the credits are spent on whichever store generated the AI landing page. Watch the per-store consumption in
/dashboard/ai-credits. - Add-ons activate per store. Activating Captcha Protection on Store A does not turn it on for Store B.
Deleting a store
/dashboard/settings → Store → Delete store (Owner only). 30-day soft-delete; restorable within that window. After 30 days, hard-deleted and unrecoverable.
Frequently asked
Q: How many stores can I have? A: Free and Pro: 1 store. Unlimited and Enterprise: multiple stores (a typical default cap is 3 — contact support if you need more). The plan limit applies at the account level.
Q: Can I move products between stores? A: Use the CSV bulk export on Store A and bulk import on Store B (Pro plan).
Q: Can two team members work on different stores at the same time? A: Yes — sessions are independent. Each operator picks the relevant store from their own picker.