BusinessNovember 7, 2026
Three shops shouldn't look like the same website
What a shared platform should change for an agency managing several independent customers.
NGNick GonzalesNovember 7, 2026 · 2 min read
A pottery shop, a bicycle workshop and a bakery might all need a website, an inventory, customer messages and someone to reconcile the money. That doesn't mean they should share a customer-facing design or be forced through the same checkout and appointment flow.
We spent time on this question while building the Aurekai white-label examples. A shared technical platform could make each business cheaper to run, but only if the people using it still felt they owned their shop.
The part the customer sees
The pottery shop needs to show what is available, tell the story of the maker and handle special orders. The bicycle workshop may need service requests, bike history and parts availability. The bakery cares about dates, preorders and production capacity. An agency working with all three needs a way to manage them without giving staff at one business access to another.
Different brands can keep their own domains, content, staff, customer records and application permissions. Bonfÿre's address and account systems are designed to support those distinctions. Aurekai supplies the websites and operations each business needs.
What can be shared
The technical pieces are familiar: login, media, forms, catalogue records, notifications, source management, CRM, finance, reporting and deployment. An agency shouldn't have to rebuild them for every client. More importantly, an improvement to the underlying editor or application can become available across the portfolio without making the stores look alike.
This changes how we think about migration work too. Moving a customer off older WordPress or PHP hosting should preserve their content, reports and working forms. A new front end is one part of the project; the business underneath is much larger.
We put a concrete example in the three-businesses guide. It uses different fictional shop identities to explore the actual operational differences. The Bonfÿre product guide places this work alongside the rest of Aurekai's business applications.
An agency could operate ten sites with shared infrastructure. The visitor should still recognize ten distinct businesses.
| Business | Customer-specific need | Shared service underneath |
|---|---|---|
| Pottery studio | Maker story, available work and custom orders | Catalogue, customer and order records |
| Bicycle workshop | Service requests, bike history and parts | Account, inventory and notifications |
| Bakery | Order dates, preorders and production windows | Catalogue, operations and billing |
Pottery / editorial
Lead with the maker’s work and custom ordering, not a generic service-booking template.
Bicycle / service
Surface repair requests and service history, using account services but distinct layout.
Bakery / production
Lead with collection dates, order deadlines and real production capacity.