Multi-Channel Ecommerce Software, Where The Channels Are Yours.
A retail site, a wholesale portal and a landing page can be three front ends on one backend, sharing one catalog, one order list and one customer record, each with its own key and its own domain.
One Backend, Many Storefronts, One Queue.
One
One Backend
A single organization holds the catalog, the orders, the customers and the money. There is no second copy to reconcile, because there is no second copy.
Many
Many Storefronts
Each site gets its own API key, its own allowed domains and its own environment. Ship a second brand without standing up a second backend.
Once
One Dashboard
Orders from every storefront land in one list. Staff work one queue rather than logging into a system per site and adding the numbers up by hand.
A Key Per Storefront, Not Per Company.
Each site points at the backend with its own key. That key carries the domains it may be used from, whether it is a test or a live key, and what it is allowed to reach.
Which means a key lifted off one site does not work on another, and revoking one storefront’s key leaves every other storefront running.
Read The API Key Docs// One storefront, one key. Same backend behind both.
// storefront-a/.env.local
NEXT_PUBLIC_DASH4DEVS_API_KEY=pk_live_a...
// storefront-b/.env.local
NEXT_PUBLIC_DASH4DEVS_API_KEY=pk_live_b...
// Each key carries its own allowed domains, its own
// scope and its own request count, so revoking one
// site's key does nothing to the other's.
Shared, And Not Shared
Shared
The Catalog
One product, one price, one stock count, read by every storefront that asks for it.
Shared
Orders And Customers
A sale on either site lands in the same list, against the same customer, in one order record.
Separate
Keys And Domains
Each storefront’s key is its own record, scoped to its own origins and revocable on its own.
Separate
The Front End
Different framework, different design, different domain. The backend does not care what you built it in.
Retail And Wholesale, Side By Side.
The commonest second storefront is not a second brand. It is the same business selling to a different buyer. A public site and a wholesale portal can share a catalog while showing different prices to different customers, because the price belongs to the customer and not to the site.
What This Is Not.
This is many storefronts you own on one backend. It is not a connector that pushes your catalog onto a third-party marketplace. Those get sold under the same words and they are not the same thing, so it is worth saying plainly which one you are reading about.
It Reads From The Same Records
Questions People Ask
What is multi-channel ecommerce software?
It is a backend that serves more than one storefront at once. On DashForDevs one organization holds the catalog, orders, customers and payments, and each site you build points at it with its own API key. A second brand, a wholesale portal or a landing page is another front end, not another system to keep in sync.
How many storefronts can one backend run?
There is no fixed limit. An organization issues as many API keys as it needs, and each one is scoped to its own domains. Organizations in production today run two and three sites off a single backend.
Do the storefronts share a catalog and customers?
Yes, and that is the point. One product, one price and one customer record, read by every storefront. A sale on either site decrements the same stock and lands in the same order list.
Can I keep a test site separate from the live one?
Keys carry an environment, so a staging storefront runs on a test key while production runs on a live one. Each key also has its own allowed domains, so a key lifted from one site will not work on another.
What happens if one storefront's key is compromised?
Regenerate or deactivate that key on its own. Every other storefront keeps running, because the keys are separate records with separate domains and separate request counts. There is no shared secret to rotate across all of them at once.
Is this the same as selling on marketplaces?
No, and it is worth being plain about it. This is many storefronts you own, on one backend. It is not a connector that syncs your catalog to a third-party marketplace. That is a different product and we do not claim it.
Point A Second Site At It.
Sign up, issue a key per storefront, and run both off one backend.