Features · the whole machine
Every feature. Nothing overclaimed.
The platform is deeper than any one page shows. Here's all of it — each capability labelled by exactly how far it's shipped.
No user counts, no GMV, no "trusted by". Every number we can print today is an engineering number — 13 of 56 integrations are wired to a live consumer.
From a prospect to a catalog.
Activation & catalog
Paste a domain; the brand is read and a buyer-ready store is assembled around it. The logo is validated against real print DPI before it can reach a press.
Import prospect domains and generate a draft branded store per prospect as a background job.
The job is real; the notification email step is still stubbed.
Freeze design, decoration, and pricing into a curated catalog, then deploy it to many stores — including stores already standing.
Each tenant owns an imported copy of its catalog — not a shared global pool.
The same physical garment carries every supplier’s offer folded into one listing. Master → source master → curation, with the curation pinned to exactly one source. Prices are never in the index — every figure comes live from the supplier API under your own account.
A Meilisearch index family plus an admin-governed facet-settings page deciding which filters each product-selection surface exposes.
Built; go-live is gated on the fast-serving infrastructure flip.
Build a quote from the catalog and convert it into a live store and order.
Generated artwork, background removal in the browser, decoration areas matching the garment’s real print zones, embroidery digitised to .dst with stitch counts and thread palettes, DPI validated in real inches, and print-accurate PDF/SVG export. Powered by DesignMint.
Operator-configurable decoration techniques with per-product eligibility — DTG, DTF, screen print, embroidery, engraving and laser, sublimation, plus foil, emboss and deboss. Embroidery is the one with a tiered quantity × stitch-count matrix, clamped to the hoop boundary.
Upscaling, background removal, triage, validate, quantize, vectorize, colour separation and stitch analysis — run per decoration type, so the file that reaches the press is the file the press expects.
Photorealistic worn and used shots with the logo composited in, keyed to the decoration technique so an embroidered chest hit doesn’t render as a flat print.
Every print-location row records where it came from — api, template, default, donated or manual. An operator pin beats everything, forever, and master edits cascade down pin-respectingly.
Every store ships editable.
Storefronts
Live-preview canvas: hero, grids, editorial, countdowns, goal bars, supporter feeds. Draft, publish, undo/redo.
Extracted brand colors and logo applied before first paint on every white-label store.
Instant subdomain; custom domains connect with managed TLS and automatic verification and renewal.
Per-page metadata, a store-level SEO rail, canonical and robots handling across both the custom domain and the subdomain.
A per-tenant HTML micro-cache with surgical purge on publish. Stock deliberately left the cached HTML — a slim endpoint serves it live.
The app side is complete; the infrastructure flip is pending.
One cart, every model.
Fulfillment
A DTG one-off, a screen-print run and a stocked item in the same order, each line routed by decoration method, location and availability. The buyer never sees the routing.
FulfillEngine and TaylorOnDemand wired as fulfillment providers, with an optional network-hold window before release. Idempotent, and cancellations are honoured.
When a supplier pulls a colourway, it greys out for new carts with a named refusal — but a size run already in someone’s cart still checks out. Nothing in flight is ever yanked.
A supplier-generic PromoStandards layer with SanMar first. A PO is raised on order placement against a configured stock location.
Verified end to end against SanMar’s Test environment, including a PO they accepted. The live-stack pass has not been run.
Per-seller shipping profiles, credentials at platform and per-distributor scope, live carrier rates, label purchase inside fulfillment creation.
Live rates verified 2026-08-06; label purchase and the tracking webhook are unverified.
The math a network actually runs on.
Money
Quantity tiers with no_lock / lock_cost / lock_selling / lock_both — the mechanism that decides who controls cost and who controls margin across a network.
Commission rules snapshotted at capture, so a later edit never rewrites history.
Commission and settlement ledger built in; automated Stripe payouts activate per-seller on Connect enablement. Offline settlement is the exercised path until then.
Pay-on-terms with available balance shown in the cart, PO enforcement, and terms orders placed unpaid and invoiced.
Built and deliberately flag-gated. Trade credit is built in — we do not claim to extend credit today.
Customer invoices (open/paid/overdue/void, PDF), statement cycles, overdue sweeps, plus a Receivables surface with aging buckets, DSO, per-distributor rollup and mark-paid.
Per-tenant Stripe credential resolution at runtime — each partner is its own merchant of record.
See what the stores are doing.
Analytics
Append-only event log with daily rollups; raw events pruned at 90 days.
Period-over-period movement on orders, revenue, and store activity.
Subscribers track each order through its states for accurate profitability.
Per-tenant GTM / GA4 / Meta / Klaviyo tags when a store wants them.
Multi-tenant means actually multi-tenant.
Enterprise & platform
Every store its own catalog, pricing, customers, theme, cache keys, domains and certs — with surgical per-tenant purge.
In-house TOTP, encrypted secrets, backup codes, step-up on sensitive actions across all three admin surfaces.
Your issuer, your claims, mapped to store accounts. Customer social login alongside it.
Credential scoping per tenant, CORS management, a system log, and a partner API with webhook delivery, retry and an audit log.
A verified 12-domain gap audit with findings mapped across all five Trust Services Criteria. A readiness programme is underway.
Readiness programme only — Brandfora is not SOC 2 certified.
Store-type features
Six machines, each with its own rules.
Access, payment, and lifecycle differ per type — not six themes, six machines. Compare the mechanics →
See any of it running.
Production prints the product. We manufacture the revenue.