Sonaris for clothing brands
A storefront with sizes, colours and stock, customer care on the same record as the order, collections developed with your makers as guests, and drop days that run from a checklist and a flow.
- The storefront and the catalog3 / 14SitesCommercePayments
- Customer care on the customer's record5 / 14CRMMessages
- Collections built with the makers11 / 14ProjectsCanvasFilesFolioChatProfiles
- Drop day from a runbook and a flow13 / 14FlowsChecklists
An illustrative workspace. The business, people and figures are fictional.
A storefront that knows every size and colour
Each garment is a product with size and colour variants, SKUs and stock. Sites renders the storefront, cart and checkout from that catalog on your own domain, with lookbook galleries beside it, and every order settles to your own Stripe account.
- Products, variants, SKUs and stock that adjusts on every order
- Discounts, shipping and tax
- Themes, custom domains, SEO and redirects
- Galleries for lookbooks next to the shop
£148
£165
£38
Customer care on the customer's record
Every buyer is tagged on their contact, so care@ shows their orders next to their question. Shared inboxes give each thread an owner and internal notes, tickets carry an SLA, and segments of past buyers get the next drop first.
- Buyers tagged automatically, with transaction history on the record
- Shared inboxes with ownership, notes, transfer and close
- Tickets with SLAs for exchanges and delivery questions
- Segments, newsletters and campaigns
Collections built with the makers
Each drop is a project with phases for design, sampling, production, shoot and launch. The moodboard is a canvas tab, tech packs keep their versions in Files, and the mill, the factory and the photographer join the project's room as guests. The size guide is a page in a folio published to the site.
- Phases, owners and a timeline for every drop
- Moodboards with images, swatches and notes
- Versioned tech packs with revocable share links
- A folio published to your site
Drop day from a runbook and a flow
The drop-day checklist covers everything from stock counts to the care rota. When the drop's project advances to launch, a flow publishes the page, emails past buyers and assigns the runbook. Big orders are flagged to the team, and a ticket that sits too long is reassigned.
- Checklist templates attached to any project or task
- Triggers from phases, orders and unanswered tickets
- Branch on any field, such as order total
- Trigger · ProjectsPhase advanced to Launchwhen
- Action · SitesPublish the drop pagethen
- Action · CRMSend to “Bought AW25”then
- Action · ChecklistsAssign “Drop-day runbook”then
- Action · ChatPost to #launchthen
- Trigger · CommerceOrder placedwhen
- ConditionOrder total over £250if
- Action · CRMTag contact “vip”then
- Action · ChatPost to #packing with a handwritten-note taskthen
- Trigger · CRMTicket unanswered for 4 hourswhen
- Action · MessagesAssign to the person on the care rotathen
- Action · ChatPost to #carethen
From the sketch to the parcel on one system
The moodboard, the tech pack, the product, the order, the care thread and the customer behind it share one database. A sold-out size, a factory delay and an exchange request are all visible from the drop that caused them.
- ProjectsDrop 02 moved to Launch
- SitesHarbour drop page published
- CRMEmail to 3,860 past buyers
- CommerceOat · M sold out
- MessagesExchange agreed, note to packing
- ChatFactory: “Slate rerun ships Monday”
- ChecklistsDrop-day runbook 14/14
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.