The platform
The operating layer under a branded merch business.
Seven engines on one platform: activation, a storefront editor, a multi-source catalog, routed fulfillment, a production-real design studio, terms and credit, and the multi-tenant architecture underneath.
Activate leads from a URL, keep the store standing after the campaign, and route what it sells into your own production — on your own supplier accounts, under your own brand.
The category problem
The bottleneck is activation, not production.
Traditional platforms are manual. Even when they're fast, they don't scale. A storefront is only the visible layer — the real work is the operating layer underneath: pricing, approvals, product rules, partner logic, payment flows, and customer self-service.
The merch industry doesn't have a production problem. It has a scalability problem disguised as manual process.
One core, two rails
Run it as your own platform, or sell across a network.
Pick the rail that matches how you go to market. Nothing about the core changes — only who holds the customer relationship.
Activation engines
Paste a URL. Get a store.
Enter a domain. We extract the brand, clean production-ready assets, curate the right product mix, and deploy a live buyer-ready experience — before the first call, not after the third.
- One prospect or a thousand — import a list and every prospect gets a draft branded store.
- Quote to store: build the quote, convert it into a live store and order.
- Auto-theming from the real brand read, not a template picker.
Storefront editor
Every store ships editable.
A block-based visual editor with live preview, draft-to-publish, undo/redo, and per-page SEO. Hero, editorial, promo, product grid, category grid, countdown, goal progress, supporters, location — plus header and footer symbols.
- Live-preview canvas — what you publish is what buyers see.
- Draft, review, publish. Roll back without a deploy.
- Per-page SEO fields and custom domains with managed TLS.
Catalog & pricing
One listing, every supplier.
A per-tenant Master catalog — an owned copy, not a shared pool. The same physical garment carries every supplier’s offer folded into one listing, and every price comes live from the supplier API under your own account.
- One listing per physical garment, with every supplier’s styles, colourways and size runs folded in.
- Prices are never in the index. The catalog service knows shapes, not prices.
- Quantity tiers and lock modes decide who controls cost and who controls margin.
- Commissions snapshotted at capture, so history never rewrites.
Fulfillment & routing
One cart. Every fulfillment model.
A DTG one-off, a 250-piece screen-print run and a stocked item in the same order. Each line routes to the right fulfillment path by decoration method, location and availability. Don’t choose between models — run all three.
- Network fulfillment: the provider pulls the blank, decorates and ships in one leg.
- PO + self-fulfillment: blanks land on your dock, you decorate and ship from your own floor.
- Decoration-aware shipping and a network-hold window before release.
- A source hold blocks new adds with a named refusal — nothing in flight is ever yanked.
Design studio
A print file, not a JPEG and a prayer.
Background removal in the browser, generated artwork, decoration areas that match the real print zones on the garment, embroidery digitised to .dst with stitch counts and thread palettes, DPI validation, and print-accurate PDF/SVG export. Powered by DesignMint.
- Left chest, full back, sleeve — decoration areas are the garment’s real print zones, not a rectangle on a mockup.
- Embroidery carries its stitch count and thread palette, clamped to the hoop boundary, and exports as .dst.
- DPI is validated against the decoration size in real inches, so a 72dpi logo is caught before it reaches a press.
- Configurable decoration techniques — DTG, DTF, screen print, embroidery, engraving, sublimation and more — with per-product eligibility.
Payments & net terms
B2B buys on terms. So does checkout. ROLLING OUT
Per-account trade credit with available balance shown in the cart, PO enforcement, invoices, statements, and overdue sweeps. Terms are part of the checkout, not a spreadsheet beside it.
- Balance states: blocked, prepay only, approved — enforced at checkout.
- Purchase-order numbers captured and validated at order time.
- Invoices and statements generated from the same ledger as the order.
- A Receivables surface with aging buckets, DSO and mark-paid.
Architecture & security
Multi-tenant means actually multi-tenant.
The unglamorous list your security and finance teams actually read — tenant isolation, per-tenant edge cache and purge, and identity that plugs into what you already run.
- TOTP MFA on every admin surface; per-store OIDC SSO via your identity provider.
- Custom domains with managed TLS and surgical per-tenant cache purge.
- Theming, catalog, pricing, customers, cache keys, domains and certs are all per-tenant.
- Append-only analytics; a SOC 2 readiness programme is underway.
Bring a prospect's domain. We'll build their store on the call.
Leave the call with a real store standing for a real prospect of yours.
Don't use a store platform. Be one.