'Bride Squad, and my name is Sarah with an h'
Personalised hen party T-shirts, named mugs, family Christmas jumpers. They sell well, especially on Etsy. Each order comes with personalisation text in a field the customer filled in, or in the order note, or in a follow-up message. One says 'as the photo but with Chloe'. One has seven names for seven shirts in one field separated by commas. One wants a name that is too long for the print area.
For each order, you open the design, type the name, check the spelling against the message, export the file and upload it to the partner for that order. When a customer mistypes their own name, you print it as written, and then they ask for a reprint.
Personalisation arrives in free text
Marketplaces and shops give you a text box. Everything else is up to you.
- The text is free-form, so layouts, separators and capitals vary.
- Multi-item orders put all the names in one field.
- Some customers use the order note or a message instead of the field.
- Nothing checks whether the text fits the design or uses characters the font lacks.
- Each print file is built by hand, one order at a time.
So each personalised order costs design time, and every step has room for a mistake.
What manual personalisation costs
The time per order limits how many personalised products you can sell, especially in peaks like Christmas and wedding season. Mistakes, yours or the customer's, lead to reprints, and a reprint for a personalised item cannot be sold to anyone else. Late files mean late dispatch, which hurts on marketplaces that measure dispatch times.
It also ties personalisation to one person, usually the owner, who becomes the bottleneck.
The personalisation flow we build
- Each personalised design has a template: the text areas, font, maximum characters, allowed characters and how the text should fit.
- On your own shop, the product page has structured fields for each text area and item, with a live preview. On marketplaces, the field instructions are written to guide customers towards a consistent format.
- When an order arrives, the text is read from the field and any messages, split per item and checked against the template's rules.
- The print file is generated from the template with the customer's text, sized for the partner's product.
- Where you want a proof, the customer gets an image of their item to approve, and the order waits until they reply or your deadline passes.
- Approved files are sent to the partner with the order. Orders that fail checks, such as text too long or unclear instructions, go to a queue for you.
| Check | What it catches | What happens |
|---|---|---|
| Length | Text that will not fit the print area | Customer asked to shorten, or queued for you |
| Characters | Symbols or accents the font lacks | Queued for you |
| Item count | Seven names for six items | Customer asked to confirm |
| Missing text | Field left empty | Customer asked, order held |
The proof step is optional per product. For simple name mugs you might skip it; for a family set with ten names, it saves reprints.
Personalised orders that need no design time
An order for seven hen party shirts arrives. The names are split, checked, and seven print files are generated in seconds. The customer gets a proof image, spots that she spelled her own name wrong, corrects it and approves. The files go to the partner that afternoon. You only see the orders the checks could not handle.
In December, personalised jumpers go out as fast as orders arrive, and nobody spends evenings typing names into Illustrator.
Is this your personalisation process?
- You build each personalised print file by hand.
- Names arrive in messages as well as the personalisation field.
- Customers' own typos have led to reprints.
- Long names have been squeezed or cut off on print.
- Personalised products are limited by your time.