sonaris
Join waitlist

Use cases / Products

Sonaris for e-commerce groups

Prove it on one brand's store, add customer care on the same record as the order, then roll out brand by brand. Each brand keeps its own isolated workspace, shared teams keep one profile across all of them, and Flows connects the warehouse.

Join the waitlist See the platform
OG
Ouseburn Commerce GroupFour direct-to-consumer brands · Newcastle
  1. One brand's store as the pilot3 / 14CommerceSitesPayments
  2. Customer care on the order's record5 / 14CRMMessages
  3. Brand by brand, team by team12 / 14ProfilesChatProjectsFolioCanvasFilesChecklists
  4. Warehouse, care and launches connected13 / 14Flows

An illustrative workspace. The business, people and figures are fictional.

01 · Start with Commerce, Sites and Payments

One brand's store as the pilot

The group moves one brand first. Its catalog becomes Commerce products with variants, SKUs and stock, imported from CSV. Sites renders the storefront on the brand's own domain, and orders settle into that brand's own Stripe account.

  • Products, variants, SKUs, stock, discounts, shipping and tax
  • Storefront, cart and checkout rendered from the catalog
  • Custom domains, SEO and redirects for the move
  • Transaction history on every order and customer
CommerceSitesPayments
Commerce · Kettlehaze Tea · Orders · today
OrderCustomerItemsTotal
#K-20418Hannah BrookSmoked Lapsang · 250 g£14
#K-20417Dev MalhotraTasting box, infuser£46
#K-20416Sato & Lyle CaféBreakfast blend · 12 × 1 kg£312
#K-20415Emma LoweGift tasting box£28
148 products · 412 variants imported from CSVCommerce
02 · Add CRM and Messages

Customer care on the order's record

Each brand gets a shared care inbox. Buyers are tagged on their contact, so an agent sees the order history next to the question. Tickets carry SLAs, and every thread is filed on the customer for the next agent who picks it up.

  • Shared inboxes with ownership, read state and internal notes
  • Tickets with SLAs and automations
  • Segments and campaigns per brand
CRMMessages
Messages · care@kettlehaze · SLA view
TicketOwnerSLA
Café order arrived shortGroup care35 min
Change gift messageAoife3 h
Is the Lapsang caffeine-free?Marcus5 h
Sato & Lyle Café · 31 orders · tradeCRM
03 · Roll out with Profiles, Chat, Projects, Folio, Canvas, Files and Checklists

Brand by brand, team by team

Each brand runs in its own workspace, isolated at the database level, with role-based permissions on every module. Shared teams such as care and operations join several workspaces with one profile. Launches run as projects, campaigns are mapped on a canvas, and the operations handbook is a folio.

  • One profile across every workspace a person joins
  • Each workspace keeps its own records
  • Agencies and suppliers as guests on the projects they work on
  • Launch-day checklists attached to each launch
ProfilesChatProjectsFolioCanvasFilesChecklists
The group's workspaces
Ouseburn Group46 seats · finance, ops, care, peopleAOMRJS+43
Kettlehaze Tea38 seats · liveAOMR+36
Ferrovia Cookware31 seats · liveAOJS+29
Pipkin Kids24 seats · migratingMR+23
Nocturne Sleep19 seats · next quarterJS+18
Aoife O'NeillGroup care lead · one profile, four workspaces
04 · Connect with Flows

Warehouse, care and launches connected

Every order calls out over HTTP to the third-party warehouse, tags the buyer and flags large trade orders. Tickets close to their SLA move to the group care team, and a launch phase publishes the product and emails the right segment. Every run is logged, every edit is versioned, and circuit breakers stop a runaway flow.

  • Call out over HTTP to the systems you keep
  • Branch on any field, such as order total or channel
  • Run logs, versioned edits, circuit breakers and execution limits
Flows
  1. Trigger · CommerceOrder placed
    when
  2. Action · HTTPSend to the warehouse's order API
    then
  3. Action · CRMTag contact “kettlehaze-buyer”
    then
  4. ConditionOrder total over £250
    if
  5. Action · ChatPost to #trade-orders
    then
  1. Trigger · CRMTicket unanswered for 3 hours
    when
  2. Action · MessagesAssign to the group care team
    then
  3. Action · ChatPost to #care-escalations
    then
  1. Trigger · ProjectsPhase advanced to Launch
    when
  2. Action · SitesPublish the range page
    then
  3. Action · CRMSend to “Bought cookware in 2026”
    then
  4. Action · ChecklistsAssign “Launch day” to the brand team
    then
05 · The running business

Four brands, one way of working

Every brand runs the same modules in its own workspace, so a launch template, a care rota or a fulfilment flow that works for one brand is a pattern the next brand copies. People who work across brands switch workspaces, not tools.

Projects · Ferrovia
Cast iron range — Launch
Spring catalogue shoot
Retail partner onboarding
Packaging refresh
Sections
Boards
Templates
Workflows
Project · Range launch · Ferrovia CookwareCast iron range — Launch
9 products · 27 variantsWarehouse flow live#cast-iron · 4 guestsLaunch flow armed
Content
Range pageSites · draft
Product shotsFiles · 64 assets
Stock
First delivery bookedChat · supplier guest
Variants and SKUsCommerce · 27
Launch
Launch dayChecklist · 0/16
Email to past buyersCRM · 18,400
Linked
Cast iron · 9 productsCommerce
Launch flow · 4 stepsFlows
Campaign mapCanvas
#cast-iron · 4 guestsChat
Ops handbook · LaunchesFolio
A week across the group
  1. CommerceKettlehaze · 6,410 orders to the warehouse
  2. MessagesShort café order moved to group care
  3. CommercePipkin Kids catalog imported
  4. ProfilesCare team joins the Pipkin workspace
  5. ProjectsFerrovia cast iron moved to Launch
  6. CRMLaunch email to 18,400 past buyers
  7. FlowsWarehouse retry log reviewed
13of 14 modules in use
ProjectsFolioCanvasChecklistsFilesCRMMessagesChatFormsProfilesSitesCommercePaymentsFlows
Seats
158 across five workspaces
Guests
Agencies, photographers and suppliers
Data
Each workspace isolated at the database level, encrypted in transit and at rest
Replaces
Shopify, Zendesk, Slack, Asana, Notion, Miro, Dropbox, Mailchimp and Zapier
Next use caseWeb agencies All use cases

Start with one module. Add the rest as you grow.

Every module works with every other from the day you switch it on, and your data exports whenever you want.

Join the waitlist More use cases