Specs on every page
Fabric, weight, trim, care and size charts published beside each style and kept in step with the factory record.
SIZ Group builds a school uniform manufacturer website that publishes product specifications, captures variant orders by size and color, and passes each order into your production planning. We design it for the sales director who wants fewer emails, cleaner specs and orders that arrive ready to produce.
For most uniform manufacturers, a school order starts as a spreadsheet that an administrator emails to a sales rep. The rep retypes sizes into a quote, the quote goes back for approval, and the production planner rekeys the order into the factory system. Each handoff adds a chance to mistype a waist size or swap two colors of the same blazer.
The breakdown usually happens at the variant level. A school may need a blazer in four sizes, two fabric weights and an embroidered crest, and the spec for each combination lives in a different PDF. When a change is approved, it rarely reaches every document, so the cutting room works from an old sheet. A direct store puts the spec and the variant on the same page the order is placed from.
Before signing off, a sales director will ask whether orders arrive cleaner than email and whether the factory receives them without extra admin. The test is simple. Take one real school order, place it through the store and check whether the production sheet matches what the school approved, line for line, with no rep retyping anything.
The director also needs to see control. Price lists by school, minimum run sizes and approval steps for custom crests should be enforced by the system rather than by memory. We would prove those rules with one pilot school before opening the store to every account, so the first season does not depend on a rep catching exceptions. Those same rules also keep your team out of the awkward call about why one school pays a different price from another.
Manufacturers commonly run a production system or an ERP such as NetSuite or Microsoft Dynamics 365, with accounting in QuickBooks or Xero. The store should write orders into that system through its API or a connector, rather than create a second source of truth. We confirm the system of record during the scoping call.
Where a factory has no modern planning system, we describe a simple export: a structured order file with size, color and crest data that the planner imports each morning. It is less elegant but reliable, and it can be replaced later once the store has proven its value.
Fabric, weight, trim, care and size charts published beside each style and kept in step with the factory record.
Buyers choose size, color and crest per line, and the store totals the quantity matrix automatically.
Orders flow into your planning system as structured data, with size, color and approval status on every line.
Each school sees only its own price list, approved styles and order history.
A direct store is only as good as its product data. Each style needs a specification sheet with fabric, weight, trim and care details, plus a size chart that matches the factory's pattern grading. Crest and logo files should arrive as vector artwork with approved colors, so embroidery quotes and store images come from the same source.
The team also needs named access. Decide which buyers at each school can order, which accounts can see trade prices and which staff can approve custom crests. Before the build starts, we will need the approved sample list, a price list per school and a contact for production questions.
Factory staff adopt the store faster when they see their own work improve. Show the production planner the order file that arrives after a school places an order, and let her flag any field that does not match what the cutting room needs. Her feedback will shape the export more than any spec document.
School buyers need a short path: sign in, pick the school, confirm sizes and submit. Send the first invitation with a link to a sample order and a phone number for questions. Keep the email route open for the first season, but mark the store as the default in every reply.
Measure the handoffs that cost the most time. Count how many orders reach production without a correction, how long a school order takes from submission to a confirmed production sheet, and how many quote requests a rep still handles by email. Those numbers move first when the store works, well before revenue shows the change.
Watch the mistakes that cost money as well. Rework from wrong sizes, sample rounds caused by outdated specs and credit notes for wrong colors all show up in the accounts. Review them each term with the sales director and use the same report to decide which schools to add next.
No, although the value grows with volume. A smaller factory benefits as soon as a few schools move onto the store, because specs and approved sizes stop living in email threads. We start with the schools that order most often and widen from there.
Yes, for the first season. We keep the email route open and show the store as the default in every reply, so buyers move across as they see the benefit. Most switchovers happen school by school rather than all at once.
Custom crests pass an approval step that records the artwork and a sample sign-off before the order can be released. New styles go through the same product record, and their specs publish once the factory approves the sample.
You do. Orders, specs and customer records stay in your own systems and can be exported in standard formats. We design the connections so your production system stays in charge, not the storefront.
Book a free scoping call and we will map your specs, variants and production handoff before anything is built.