Emporia / In development
Going multi-seller usually means a platform migration or a seller axis bolted into the product catalog. Emporia does neither. Sellers, offers, and settlement live outside the commerce platform; the catalog stays under the merchant’s control.
The decision that matters
The tempting shortcut is a SKU or a variant per seller. It fails on arithmetic because variant ceilings multiply against the colour and size axes already in the catalog. More importantly, it makes seller onboarding a catalog operation and leaves product records behind when a seller leaves.
Emporia holds offers as first-class records outside the catalog. The commerce platform can keep one product while receiving the projected price and availability needed for storefront discovery.
The model
One product in your catalog, many seller offers against it. The seller does not become another variation axis, so onboarding a seller is not a catalog write and removing one does not orphan URLs, feeds, or search index entries.
A winner can be selected per product and projected into listing pages, search, and sorting. The product detail page can still expose the eligible seller offers with price and dispatch time.
A shopper who deliberately picks a seller gets that seller. If the seller cannot fulfil, the order is cancelled and refunded rather than silently reassigned to someone else.
Category alone cannot express "anyone approved for footwear may list, but nobody lists a restricted brand without permission." Entitlements are enforced at the database layer, so they hold regardless of which code path inserts the offer.
Operations
Listing sellers is the easy half. Moderation load, inventory contention, and settlement accuracy are what determine whether the operations team can actually run it.
New product submissions always need a human. Price and stock changes on an existing product do not — they can auto-approve with rule-based holds on discount depth, floor price, and delta against the current buy box.
Reserving at cart lets abandoned baskets exhaust inventory. The hold is created when the order is placed and uses the same expiry window as seller acceptance, so the two do not drift apart.
Commission is calculated from the seller line price at the applicable contract rate. The rate and ledger entry remain reconstructable from the order record.
The stated returns window is the shopper contract with the operator, not seller discretion. In-policy returns can debit the seller while preserving a separate dispute path.
Onboarding the second merchant
The architectural bar for Emporia is that onboarding another retail brand requires tenant configuration rather than a fork of the application. Merchant and seller boundaries are enforced in the database, keeping the operating model explicit as the platform grows.
Status
Emporia is not generally available. The offer model, buy-box selection, seller entitlements, atomic reservations, and commission ledger are built and verified. Fulfilment is seller-shipped only, order-management-system integration is not built, and settlement currently records what is owed rather than moving money. We are working toward a first live deployment and are not taking general signups.