Tilpas for teams
Team orders,
with persisted handoff truth.
Compare persisted supplier quotes, select a route, pass manufacturing-readiness checks, pay only when checkout is enabled, then follow recorded fulfillment and shipment states.
The workflow
Six stages, each tied to persisted state.
Brief
After sign-in, Tilpas resolves the active organization server-side. A new brief persists every product line and quantity, plus provided budget, brand, deadline, and delivery-country details.
Organization-scoped · all line items persisted
Review
Successful design generation records manufacturing snapshots and variants for review. If generation fails or a snapshot cannot be loaded, the flow keeps a recoverable state instead of inventing a proof.
Persisted snapshots · recoverable draft on generation failure
Routes
The route page compares persisted supplier quote rows and the recorded routing recommendation. If no quote row exists, it says quotes are not ready; selecting a route queues the existing tech-pack flow.
Persisted quotes · full brief coverage required
Readiness
Manufacturing readiness checks the persisted snapshot, selected quote coverage, trusted supplier product references, tech-pack job state, and downloadable artifact. Missing evidence blocks the next step.
Missing evidence blocks the next step
Payment & fulfillment
Payment is offered only when the tech pack is available, proof approval is recorded, and a valid payable total is present. A paid status does not by itself mean production has started.
Paid does not mean production started
Tracking & feedback
Tracking advances only from exact persisted brief, supplier, and shipment evidence. Feedback stays locked until delivery evidence is complete; with structured shipments, every shipment must be delivered.
Fulfillment requested → In production → Shipped → Delivered
Manufacturing readiness
The handoff can refuse to proceed.
The buyer-facing readiness state is derived from persisted brief, quote, supplier-reference, production-spec, and queue evidence. A missing prerequisite is shown as a blocker instead of being promoted into a production claim.
| Gate | Persisted evidence | Buyer effect |
|---|---|---|
| Manufacturing snapshot | A persisted manufacturing snapshot ID exists for the brief. | Missing → return to design review |
| Quote coverage | The selected persisted quote covers every brief item. | Incomplete → route blocked |
| Supplier references | Every selected line has a trusted automated supplier product reference. | Missing → payment blocked |
| Tech pack | Generation state and a downloadable tech-pack artifact are recorded. | Failed or missing → retry before payment |
| Checkout | The brief is awaiting payment and both quote and checkout totals are valid. | Only then is payment offered |
What later statuses do — and do not — mean
- Paid
- Payment is recorded. Production start is not implied.
- Fulfillment requested
- The paid order has entered fulfillment. The system does not record a separate factory-approval state.
- In production
- The order is shown in production only when that lifecycle state is recorded.
- Delivered
- When structured shipments exist, every shipment needs delivery evidence before feedback unlocks.
Persisted brief
What the workflow actually records.
Items
Each brief line is persisted with its product and quantity; a size breakdown is stored when supplied. A manufacturing quote must cover the full set of brief items before it can pass readiness.
Brief snapshot
The brief stores the provided budget maximum, brand-guideline snapshot, deadline, and delivery country alongside the organization-scoped order intent.
Fulfillment evidence
The selected route and production spec carry supplier references, fulfillment status, tracking information, and structured shipment records when those facts exist. Tracking does not invent unrecorded milestones.
Start
Start with a real brief.
Sign in with an active organization to create a brief. If catalog or manufacturing evidence is incomplete, the flow blocks instead of inventing a route, order, or delivery state.