Give each store its own identity and workspace.
Operate distinct merchant businesses through a shared platform while keeping their storefront identities, records, and assigned access clear.
Keep the merchant's brand at the front
A storefront can use its own domain and approved store identity. The shared administration application sits behind that customer-facing experience; store owners do not need a separate admin application for every merchant domain.
Assign people to the work they manage
Owners and staff receive permissions for their assigned stores. A person who works across stores can hold explicit assignments without making every merchant record visible to every account.
Distinguish a business from its locations
A boutique, warehouse, or service point can be a location within a store. A separate merchant business can be its own store tenant. Decide that boundary from the operating model rather than creating a new tenant for every address.
Plan the rollout deliberately
Review the store boundary, domain, people, catalog, channels, and provider setup. Domain ownership and ready hosting are separate requirements; onboarding includes the configuration and validation appropriate to the merchant.
Can an external merchant use its own domain?
Yes. That storefront is configured for the merchant's store. Domain and hosting activation are part of the onboarding scope.
Do merchants use the same admin login address?
They can enter through one shared administration address. What they can manage depends on their store assignments and permissions.
Are records automatically shared between merchant tenants?
No. Separate tenants retain their own records. Cross-tenant sharing should not be assumed from common ownership or a shared platform login.
Let’s start with your business.
Bring a piece, a workflow, or a question. We’ll explore it together.