The Economics of Running a Portfolio of Niche Stores

There is a strategy that works well in dropshipping and that almost nobody executes properly: run several small, tightly focused niche stores instead of one general one. A store about montessori toys converts better than a store about everything, because the visitor can tell within two seconds that they are in the right place. The copy, the theme, the product mix, and the ad creative all pull in one direction.

The reason people don’t do it isn’t that they disagree. It’s that the second store costs about as much as the first.

The per-store fee is a tax on experiments

On a conventional hosted store platform, each storefront is a separate subscription. Not a separate line item on one bill — a separate account, separate login, separate app installs, separate configuration. Whatever the monthly number is, multiply it by the number of niches you want to test, and add the paid apps each store needs to be functional.

The arithmetic is uncomfortable in a specific way: the fee is identical whether the store makes $0 or $5,000. That flips the economics of experimentation. Testing a niche stops being “spend a weekend and some ad budget” and becomes “commit to a recurring cost before you know anything”. So operators run one store instead of five, stuff unrelated products into it, and wonder why conversion is mediocre.

The dropshipping model is fundamentally a search problem. You are looking for the niche and product combination that works, and you find it by testing. Anything that makes a test more expensive makes you worse at the thing the business is actually about.

What is genuinely shared between stores

The interesting question is which parts of a store are niche-specific and which are pure infrastructure. Go through it honestly and the list is lopsided:

Genuinely unique per store — the brand name, the theme and colours, the product catalogue, the copy, the customer list, and the orders. This is the part that should be separate, and on Volmeris it is: every store has its own catalogue, orders, content, branding, and theme, with data scoped to that store at the database layer.

Identical across every store you will ever run — the checkout, the payment integration, the currency conversion, the supplier connection, the order routing, the tracking-number sync, the stock sync, the transactional email, the promotions engine, the CMS. None of this is niche-specific. It is plumbing. You pay for it once per store because of how the software is packaged, not because of anything inherent to the problem.

That asymmetry is the whole argument. If the plumbing is built once and shared, the marginal cost of your next storefront collapses to the part that is genuinely new: choosing a niche, picking products, and writing copy.

What that looks like in practice

Volmeris is built around this shape deliberately. Concretely, on your second store:

• The account is the one you already have. Sign in once, with an email magic link, and every store you run is in the same dashboard. There is no second platform account to create or pay for.
• The address is free and immediate. Each storefront gets a Volmeris subdomain that is live over HTTPS within minutes of provisioning. (Bringing your own domain is on the way — see the roadmap — so today the free subdomain is what ships.)
• Stripe is already connected. Connect a Stripe account once and each new store’s setup wizard defaults to reusing it. You confirm the choice; you don’t re-enter keys.
• The sourcing, checkout, promotions, fulfilment, and email machinery is already there. It arrives with the store rather than being assembled per store.

So launching store number two looks like: name it, pick a theme, confirm Stripe, and publish through the same provisioning wizard — then import products separately in the admin. Same handful of steps whether it’s your second store or your twelfth.

The portfolio view is the payoff

Running several stores creates a problem one store never has: knowing which of them is working. Five separate platform accounts means five dashboards and a spreadsheet you maintain by hand on Sunday nights.

Volmeris gives you one order list across every store, with portfolio-wide order-count and paid-revenue totals plus a per-store filter, so you can drill into any one store’s numbers without leaving the dashboard. That’s the number that drives portfolio decisions — which niche gets the next round of ad budget, which one gets a second product line, and which one you quietly stop working on.

Killing a store that isn’t working should be an easy decision, and it is only easy when it isn’t also a decision about a subscription.

The honest caveats

Two things this argument does not claim.

Shared infrastructure doesn’t make stores free to run. Each store still needs a niche worth serving, products worth listing, copy worth reading, and traffic. The work is real; it is only the platform overhead that goes away. A portfolio of five stores you haven’t put any thought into is worse than one store you have.

And it doesn’t mean you should launch twenty at once. The point of cheap store creation is that testing a niche stops requiring a financial commitment up front — not that volume substitutes for judgement. Most portfolios that work look like two or three stores that earn their keep plus one experiment running at any time.

Volmeris is in public beta and everything is free while we build it; the plans we intend to launch are published on the pricing page so you can see where it’s heading before you build on it. If the portfolio approach is what you’ve been avoiding because of what the second store costs, that particular obstacle is gone.