This section didn't finish loading
Something took too long to respond. Reloading usually fixes it.
— Industry · Multi-brand manufacturers
A multi-brand commerce platform for manufacturers.
A second brand should not mean a second everything. We build one platform that carries several storefronts, each with its own catalog, pricing and identity.
SBFS builds multi-brand commerce platforms for manufacturers who sell the same production capacity under more than one name. Nafarú launched as a second retail brand on the platform we had already built for Muebles Torga, with its own ranges, reference codes, pricing and identity, while the commerce, catalog and configurator layers stay shared, so a fix or a feature lands once and both storefronts get it.
02— Fit
Who this is for
You sell under more than one name
A retail brand and a trade brand, a regional brand, or an acquired range that still needs to read as its own storefront.
Two codebases are already drifting
The same fix gets written twice, and the two storefronts answer the same customer question differently.
Each brand has to stand on its own
Customers should see a brand, not a skin over another shop: separate ranges, reference codes, pricing and identity.
03— Capabilities
What we build
One commerce and catalog layer
Nafarú and Muebles Torga run on the same commerce and catalog layer, so a fix or a feature lands once instead of twice.
Per-brand catalog, pricing and identity
Separate ranges, reference codes, pricing and typography per brand, so each storefront reads as its own rather than as a variant.
A shared configurator with per-brand rules
The configurator and its compatibility rules are shared infrastructure; the option sets, geometry and materials belong to each brand.
One admin for the group
Catalog, content and orders for both brands are managed from a single admin, so the storefronts are maintained as one system rather than as two.
05— Method
How an engagement runs
01
Week 1 · Scope and catalog audit
We map what is genuinely shared between your brands and what is not, model the catalogs, and write the spec. You see the split before anything is built.
02
Weeks 2 to 6 · Build to MVP
The shared platform and the first storefront ship together, with a reviewable demo every Friday in your own staging environment.
03
Week 6 · Production handoff
Deployed to your domains on your Vercel team and your Neon database. Your team is trained on the system, and we stay on retainer for tuning.
06— FAQ
Questions buyers ask before they commit.
07— Related
Related solutions
10 — Get in touch
Got a configurable product? Let us talk.
Fastest way to start
Book a 20-minute intro call
Pick a time that suits you — you'll get a Google Meet invite. We look at your product, your catalog, and whether a six-week Forge build is the right fit. No slides, no pressure.
See available times
See available times Rather send details in writing?juan@sbfs.co
Direct to Juan. Twenty-four hour reply, typically. If we cannot take your project on, we will tell you fast.
Product briefemails juan directly
