How to Run Multiple Online Stores From One Account

On ShopsWired, one account can own — or be a team member of — as many stores as you want, and you switch the active store from a menu inside the admin. Each store keeps fully isolated data, its own plan, its own domain and its own team, while your login, security settings and billing live at the account level. Nothing is shared between stores unless you deliberately move it.

The short version

Multi-store on ShopsWired works on three rules, and everything below follows from them:

• One identity, many stores. Your email, password, 2FA and passkeys are account-level. You sign in once and pick the store you want.
• Data is isolated per store. Products, orders, customers, themes, plugins, settings and staff belong to a single store. There is no shared catalog or shared customer list across stores.
• Billing is per store, grouped how you like. Pricing is per shop, and each shop is assigned to a named billing account — so three stores can land on one card, or on three separate invoices.

Why merchants end up with more than one store

Most multi-store setups fall into one of four patterns:

• Separate brands. Two catalogs that share nothing — different audiences, different domains, different look. Keeping them in one store means fighting the theme and the navigation forever.
• Retail vs. wholesale. Some merchants prefer a dedicated trade store rather than mixing price tiers into a consumer storefront. (If that's the only reason, read the alternative below first — ShopsWired has native B2B pricing on Pro and above, and one store is usually simpler.)
• Different currencies or regions. A store carries one currency and one timezone, so a genuinely separate market often wants a genuinely separate store.
• Agencies and operators. One person runs stores for several clients and needs the invoices, not just the data, to stay apart.

Setting it up

1. Create the second store. You can create new stores at any time from your account — you pick the plan as part of creating it. Nothing carries over from your first store; it starts clean.
2. Switch between them. The admin has a store switcher; changing the active store changes everything you're looking at — catalog, orders, settings, plugins.
3. Point a domain at it. Add a custom domain and verify it with a CNAME and TXT record. Use a subdomain such as www.example.com or shop.example.com; root domains aren't supported yet because DNS doesn't permit the required CNAME on a root. Each store also keeps its own <name>.shopswired.net address, and customer-facing links in emails and packing slips automatically use the public domain.
4. Set the team per store. Invites, roles and custom permissions are per store. Someone who runs your outlet shop doesn't automatically get your main shop — you invite them where they're needed.
5. Assign a billing account. See below.

Billing accounts: the part that saves the most pain

You can create multiple named billing accounts — "Personal", "Client ABC", "Northern Brands Ltd" — manage cards for each through the Stripe customer portal, and assign each store to one of them. Two things follow that matter in practice:

• Clean separation of invoices. An agency or a holding company gets per-client invoices without maintaining a separate login (and separate 2FA, and separate recovery email) per client.
• You can hand one over. A billing account can be transferred to another user. When a client wants to take their store in-house, that's the mechanism — you move the billing account rather than rebuild the store somewhere else.

The usage view is worth checking per store too: it shows the current plan, record and file storage against your limits with projected overage, compute spend against your monthly cap, and your plan's rate and retention limits. Multi-store operators usually find one busy store and two quiet ones, which is exactly the shape per-shop plans are good at.

How the cost works out

Pricing is per shop, and each shop gets its own independent plan and rate limits — so you can run one store on a higher tier and a small side project on a lower one. Plans start at $29/mo for Starter; Pro is $99/mo and adds building your own plugins, wholesale/B2B pricing and the Wired supplier network; Business is $249/mo and Enterprise $499/mo. New shops currently run at $1/mo for the first 3 months, which is a cheap way to try a second storefront before committing to it.

The thing that compounds across stores is the fee model: ShopsWired charges 0% transaction fees on every plan. You pay your payment processor's standard rate (Stripe's 2.9% + 30¢, for example) and nothing to us on top. Across three stores, a platform percentage is three percentages. The full breakdown is on the pricing page.

Compared with juggling separate Shopify stores

To be fair: Shopify also lets one login hold several stores and switch between them, so the "one account" part isn't unique. The differences show up in the economics and the plumbing. Each Shopify store carries its own subscription, its own app purchases, and — unless you're on Shopify Payments — its own transaction fee on top of your processor's rate. Apps you pay for are bought per store, so a $40/mo app across four stores is $160/mo. On ShopsWired the platform fee is 0% everywhere, and a plugin or theme you build yourself can be packaged and installed on each of your stores without buying it again.

What is not shared — be honest about this

Store isolation is a feature, but it has a cost. Out of the box:

• No cross-store inventory sync. Stock levels are per store. If two stores sell from one warehouse, you need something to reconcile them.
• No unified analytics. Dashboards and reports are scoped to the active store. Consolidated reporting is something you build or export.
• Customers don't carry over. A shopper with an account on one store is a stranger on the other, which is correct for separate brands and annoying for one brand split in two.

The practical bridges: CSV import/export in Settings moves products, customers, orders and custom records between stores, with an option to skip plugin hooks on large loads; a plugin or theme you build can be packaged and installed on each store from a .zip, so you write the integration once; and the Wired network exists if one of your stores genuinely supplies another — it links two ShopsWired stores with an offer scope, markup rules, automatic supplier fulfillments and a ledger, which is a real answer to "my second store resells my first store's catalog". See the features reference for the specifics.

When not to split

Run one store if the difference between your two ideas is a product line, a customer segment, or a price list. Collections, tags and native B2B tiered pricing handle those inside a single store, and you'll keep one catalog, one customer list and one bill. Split when the stores need different domains, different currencies, different teams, or different books — that's when isolation is worth paying for twice.