Enterprise · annual agreement, scoped in writing

Your operation,
wired end to end.

White-glove Commerce, an SDK licence for your own applications, or both — with dedicated environments, SLA support and the supplier plumbing a real decoration operation runs on. Every engagement starts and ends as a written scope.

Dedicated environmentsSLA supportSupplier & POD routingCustom scope, approved in writing
The custom scope process

No sales deck.
A scope in writing.

Every Enterprise engagement — platform builds, migrations, integrations — runs the same way: scoped, priced and approved in writing before work begins.

Step 01
The scoping call

An hour on your current setup — platforms, techniques, suppliers, order volume. You bring the catalog; we bring the questions.

platformsShopify + own press
techniquesDTG · DTF · EMB
volume2,400 orders / mo
Step 02
The written scope

Deliverables, integrations, environments, dates and price — a document, not a promise. Change requests amend it in writing.

APPROVEDscope-v2.pdf · 14 pages
youus
Step 03
Build, rehearse, cut over

Migrations rehearse on copies and cut over on verified data — the same discipline as the migration path, applied to the whole engagement.

rehearsal 12 mismatches
rehearsal 3clean ✓
cut oververified · live
The PO & routing spine

Every order becomes
a purchase order somewhere.

Your presses, the POD network and blank suppliers behave as one system: the order routes, the PO writes itself, and the state comes back over webhooks.

Order confirmedrouted per linePO createdconfirmedshipped
PO lifecycle
States, not spreadsheets

Created → sent → confirmed → in production → shipped → received. Every transition timestamped on the order, every exception in one queue — and mirrored to your ERP over webhooks.

created → sent09:12 ✓
confirmed → in production11:40 ✓
shippedawaiting carrier
Supplier catalogs
Synced, not re-keyed

Blank catalogs sync on schedule — styles, colourways, size runs and cost. A discontinued blank flags every product built on it before a customer finds out.

SanMar sync02:00 ✓
G500 · Navydiscontinued → 3 products flagged
Inventory
Stock checked before promise

Supplier stock is checked at order time, per warehouse. A size run that can't be filled splits or holds by your rule — never silently.

PC61 · L · Dallas412 in stock
PC61 · XL · Dallas0 → split to Reno
Cost & margin
Margin per route, visible

Blank cost, decoration cost and freight per routing option — so "own press vs. Printful vs. SanMar-drop" is a number, not a hunch, line by line.

own press$6.20 · 41%
Printful$8.90 · 29%
SanMar drop$7.40 · 35%
Bring your own
Webhook & CSV suppliers

Your factory, your contract decorator, your 3PL — POs go out as webhook payloads or scheduled CSV drops, confirmations come back the same way.

POST yourfactory.com/po ← PO-2291 · 200 ✓
Scoped per operation
Your routing rules

Which lines route where — by technique, quantity, region or margin — is part of the written scope. The rules run in your dedicated environment.

technique = EMB→ own press
qty > 200→ SanMar
region = EU→ HelloPrint
SLA & support

Support with a clock on it.

Production downresponse < 1 hr · 24/7
Degraded — orders flow, something's offresponse < 4 hrs
Questions & changesnext business day

Named contacts, a shared Slack channel, and quarterly reviews against the scope. Targets are contractual, set in the agreement.

Dedicated environments

Your own lane.

  • Isolated production and staging environments, in a region you pick
  • Release windows you approve — no surprise deploys mid-season
  • Self-hosted Docker where policy requires it
  • Data residency and retention set in the agreement
The migration path
Enterprise

Bring the org chart.

An hour on your platforms, techniques, suppliers and volume — and you leave with a written scope, not a sales deck.