Smart Tailor
Status
Jersey ordering & production operations Preview build

Every stitch. Accounted for.

A single system for structured jersey design, server-checked totals, seven stages of production, and pickup or delivery. Built to make every handoff visible.

Explore the workflow System status
Design
Catalog studio
Payment
Confirmed by customer
Production
Seven tracked stages
Specimen 01 / front Concept
Team identity Number field Colorway Crest layer Conceptual dark jersey with lime accents and editable design zones SMART TAILOR 07 ST EST. IN THE STUDIO
Structured layers

Editable name, number, palette, and crest.

ST / 01

Visual concept for the design system — not a catalog item or live order.

Production sequence

01 The operating thread

One thread.
Four handoffs.

From the first editable layer to the final handover, every part of the order has a place, an owner, and a record. No disconnected spreadsheets. No mystery status.

01

Shape the
identity

Build a jersey from the catalog or the studio. Team names, player numbers, crests, and colors remain structured, editable data — not baked into a flat picture.

CatalogDrag & dropOptional AI draft

02

Lock the
details

Choose sizes, quantities, pickup, or delivery. Availability and totals are checked on the server, then the product, design, and price are snapshotted into the order.

Server pricingS / M / L / XLFulfillment

03

Confirm the
order

The customer confirms payment from the order page; no money moves and no transfer is checked. Every change still carries an actor, a time, and a note. Reviewing uploaded GCash proofs is deferred work, not a feature of this build.

Audit trailNo gatewayReview deferred

04

Follow every
stage

Design, printing, cutting, pressing, sewing, quality control, and finish. Each stage has an assigned owner, notes, and history. Customers see progress without seeing internal detail.

Seven gatesStaff queueCustomer tracker

02 Production, in sequence

Seven stages.
No shortcuts.

Work moves through one gate at a time. Each handoff records who changed what, when, and why — so a delayed stage is visible before it becomes a missed date.

A later stage cannot begin until the prior stage is complete, unless an authorized administrator records a reasoned override.

  1. 01

    Design

    Approval gate

    Confirm the structured artwork, exact spelling, player numbers, crest, and colorway before anything is produced.

  2. 02

    Printing

    Production

    Record print progress against the approved design before the job moves to cutting.

  3. 03

    Cutting

    Production

    Track cut work for the order and log the handoff with a timestamped stage update.

  4. 04

    Heat Pressing

    Production

    Confirm pressing progress and keep a clear record of the assigned staff member and update time.

  5. 05

    Sewing

    Production

    Update assembly status with staff notes, stage ownership, and a durable history entry.

  6. 06

    Quality Control

    Quality gate

    Staff start and complete the inspection with a note; the next stage stays locked until this one is recorded as completed.

  7. 07

    Finished Product

    Release gate

    Mark the completed job ready for the agreed pickup or delivery handover.

03 Built on guardrails

Trust is a
backend feature.

The interface can be beautiful. The rules underneath have to be stricter. These are the constraints the ordering, payment, and production flows are built around.

No automatic payment capture. This build confirms payment on the customer's word and records who did it. No gateway is connected and no proof is verified.

01 Server-owned totals

Line items and prices are recalculated on the server, stored with Decimal, and snapshotted at order placement. A browser-submitted total is never trusted.

Decimal pricing · immutable snapshots · transactional checkout

02 Audited status changes

Order status only moves through the transition rules, and each move writes an event with actor, timestamp, previous value, and note. A GCash reference submitted by the customer waits in the administrator's review queue; only a verified transfer moves the order to confirmed, and a rejection records its reason.

Transition guards · actor + timestamp · staff-verified GCash

03 Private by default

Customers see only their own orders, designs, and addresses; production and fulfillment tools sit behind role checks. Public catalog photos are re-encoded without EXIF/XMP before storage, and the application serves no media route once DEBUG is off.

Object ownership · role checks · metadata-stripped uploads

04 Gated production

Stages follow the required sequence. Authorized staff can update assigned work; a skip requires an administrator override with a reason. Every change keeps actor, timestamp, previous value, new value, and notes.

Seven fixed stages · audit history · scoped staff access

05 Honest integrations

AI image generation is optional and stays server-side. Catalog ordering and manual design work without it. If a provider is missing, slow, or out of quota, the interface says so instead of pretending a request succeeded.

Optional provider · explicit failure states · safe fallback

Current build · Foundation

Every phase.
Verified end to end.

This is a phased thesis build, not a finished mockup. Catalog, accounts, design studio, ordering, production, fulfillment, notifications, and reporting are live and covered by the automated suite. What is deferred is stated plainly on the status page and in the README.

Inspect live checks

Live today

  • Catalog, design studio, and editor
  • Order placement and tracking
  • Seven-stage production board
  • Reports, CSV export, notifications

No fabricated orders, customers, payments, or sales statistics appear in this build. Every figure on screen comes from rows in the database you are running.