The short answer
- Names must arrive as structured data, entered by the person they belong to
- Validate length and characters at entry, not at the art station
- Never retype a name — every transcription is a chance to create scrap
- Get the customer to approve the list exactly as it will be produced
- A misspelled name is scrap, not a reprint
Personalised orders are among the most valuable work a decorator does and among the most error-prone. Two hundred garments each carrying a different name is two hundred opportunities for a mistake, and each mistake is a ruined garment rather than a reprintable one.
Almost all of the risk comes from the same source: names being retyped by somebody who was not the person the name belongs to.
Where it goes wrong
| Failure | Cause |
|---|---|
| Misspelled name | Transcribed from a handwritten list |
| Name too long for the garment | No length check at entry |
| Wrong name on wrong size | Two separate lists, matched by hand |
| Duplicate or missing entry | Collected across several channels |
| Accented or unusual characters | Not supported by the font or machine |
| Last-minute additions | Arrived after the list was finalised |
The first is the most damaging and the most avoidable. A name typed by the person it belongs to is spelled correctly; the same name copied from a handwritten sheet by somebody else is a coin toss on anything unusual.
Every time a name is retyped, you have created a chance to make scrap.
Collecting names
At the point of ordering, from the person concerned, as a field rather than a note.
What good collection looks like
- Each person enters their own name, number and size
- Fields, not free text — name and number separately
- The entry attached to that person's order line
- A preview showing how it will appear on the garment
- Confirmation of what they entered in their order confirmation
That is one of the strongest arguments for running team kit through a store rather than collecting a spreadsheet. The roster arrives as structured data attached to real orders, with the sizes already matched to the names — which removes the reconciliation step entirely.
Where a customer insists on supplying a list, ask for it in a defined format with one row per person and separate columns, and refuse a scan or a photograph. A list you have to read is a list you have to retype.
Validating at entry
Catch problems while the person is still there to fix them. Every check at entry is one that does not become a phone call later.
| Check | Prevents |
|---|---|
| Character limit | Names that will not fit the garment |
| Allowed characters | Symbols the machine or font cannot render |
| Number range and uniqueness | Two players with the same number |
| Required fields | Blank entries discovered at production |
| Live preview | The person seeing what you will make |
The character limit should come from your actual garment and method rather than a round number. A name that fits across an adult back may not fit a youth garment, and embroidery has its own minimum size below which lettering is unreliable.
Duplicate number checking matters for sports kit specifically, and it is trivially easy to implement and painful to fix afterwards — two players with the same number is discovered at the fixture rather than in your shop.
Getting them to the machine
Export, never retype. The list that reaches production should be the same data the customers entered, in whatever format the machine or software wants.
The production list should carry
- Name and number exactly as entered
- Garment style, colour and size for that person
- Placement and character height
- Ink or thread colour
- A sequence number, so production order matches the sort order
The sequence number is a small thing that saves an hour. If garments are produced in the same order they will be sorted and bagged, the sorting step becomes checking rather than searching — which matters when sorting a named order is already one to two days of work.
Checking before production
One approval, on the exact list, before anything is made. This is the single most valuable checkpoint in a personalised order.
Send the customer the list as it will be produced — every name, every number, every size — and ask them to confirm it. Not the artwork; the list. Spelling is what will be disputed, and it is the customer or the organiser who knows whether a name is right.
Attach that approval to the job, dated, the same way as a proof. When somebody says a name is wrong, the approved list settles whether it was wrong when they approved it — which usually ends the conversation without anyone having to argue.
Sorting and delivery
Sort by recipient, bag individually, and check each against its order line as it is sealed. That is slower than sorting by size and it is the only approach that produces a correct delivery.
What makes handover work
- One bag per person, labelled with their name
- Bags grouped by team, class or department
- A manifest the organiser can check without opening anything
- Spares kept separately for exchanges
- An agreed process for anything wrong
Keep a few spare blanks on the common sizes. A single misspelled or misprinted garment on a named order is otherwise a full reprint with its own setup, and a spare turns that into a five-minute fix — which is the practical use for printed overs. The rest of the software archive assumes nobody retyped a name.
Late additions and changes
Somebody always asks to be added after the list is closed, and how you handle it decides whether the job stays one job.
The honest answer on a consolidated run is that a late addition is a separate small job with its own setup, and pricing it that way is fair rather than obstructive. On a team store the cleanest policy is that late orders go into the next run, stated before the store opens so nobody is surprised.
Where you do accept one, treat it as a new entry through the same process — entered by the person, validated, approved on the list. A late name typed straight onto a job sheet is the single most likely name to be wrong, because it skipped every check the others went through.



