Some orders are the same design many times with different words: 120 name badges for a conference, 60 wine labels with each guest's name, 40 place cards, a set of staff mugs. Customers already have the list in a spreadsheet. What they usually do not have is a way to give it to your store, so it arrives by email, and someone at your shop spends an afternoon copying names into a design file and proofing each one.
This post shows how to take these orders through the product page instead, with the list as part of the design.
How variable-data orders work
Printers call this variable data: one layout, with some fields that change on every copy. The design has placeholders, the spreadsheet has a column for each one, and each row becomes one printed item.
| Design text | Row in the list | Printed |
|---|---|---|
Hello {{name}} | name = Alex | Hello Alex |
{{name}} / {{title}} | Sam, Head of Sales | Sam / Head of Sales |
That is the whole idea. The rest is making it easy for the customer and safe for you.
Step 1: The customer adds fields to the design
With the Bulk Personalization (CSV) addon, the designer's Text panel gets a Bulk list tab. Add field puts a text layer such as {{name}} in the print area. Any text layer can hold fields, mixed with fixed text if needed, and the layer is styled like any other text: font, colour, size and position.
Step 2: They add the list
The customer can Upload CSV or Paste a table copied straight from a spreadsheet. CSV, TSV and an Excel paste all work.
- If the list has a header row, columns are matched to fields by name.
- Without a header, columns are taken in order, and the mapping can be changed before importing.
- Download sample CSV gives a file with the right header, for customers who would rather fill in a template.
- Rows can be typed and edited in the table after import, so fixing one typo does not mean uploading the file again.
Step 3: They preview every row
The ‹ › buttons step through the list and the canvas shows each row in turn. A value that is too wide for its layer is shrunk to fit, so "Maximiliana Rodríguez-Hernández" does not run off the badge.
The quantity follows the list: 120 rows are 120 items. While there is a list, the designer's quantity controls are locked, and so is the cart quantity of that line on WooCommerce, OpenCart, PrestaShop and Shopware. That prevents the classic mismatch of 120 names and an order for 100.
What you get in the order
- One summary line. Cart, checkout, order page and emails show, for example, Bulk: 120 rows. Order pages and emails also list the first five rows so both sides can see it is the right list.
- A print file per row. On the order's design page, each view with a field layer gets a Bulk files (N) button. It downloads a ZIP with a 300 DPI PNG and an SVG per row (
001-alex.png, …) plusdata.csvfor checking the run. - Optional fees. You can set a charge per personalized row and a setup fee per order line, both priced on the server.
Safety checks you do not have to write
A list from a customer is untrusted input. When the item is added to the cart, the server checks the number of fields and rows, the length of each value, unprintable characters and empty rows, that every field is used by a text layer, and that the quantity matches the list. A changed request is refused.
Limits are set in Veyo Personalizer → Bulk CSV:
| Setting | Default | Range |
|---|---|---|
| Rows per order line | 100 | 1–500 |
| Fields per design | 8 | 1–10 |
| Value length (characters) | 60 | 1–100 |
| Per personalized row | 0 (no charge) | Store base currency |
| Setup fee per order line | 0 (no charge) | Store base currency |
| Field used in file names | First field | A field name, such as name |
The designer reads the same limits, so the customer is stopped where the server would refuse, not after they press Add to cart.
Bulk lists and team orders
If you read the team jerseys post, this will look familiar. The difference is what changes per row. Team Names & Numbers is built for kit: a name, a number and a size per shirt, with size surcharges. Bulk Personalization is for any text fields on the same product: badges, labels, cards, certificates. A design can carry one kind of list or the other, not both.
What it does not do yet
This first version handles text fields. Images, QR codes or barcodes per row, serial numbers and multi-line values are not included, so plan those orders the usual way for now.
Requirements
Bulk Personalization needs Veyo Product Personalizer 1.10.0 or later, and the PHP zip extension for the print-file ZIP. The per-row PNGs are made on the server with PHP exec(), librsvg and ImageMagick. If your host disables exec(), the ZIP cannot be built; the Download PNG button on the production page then renders the view in your browser at 300 DPI, with the first row as saved in the design. Nothing is sent to outside services.
FAQ
Can customers use Excel?
Yes. They can copy cells from Excel and paste them, or export a CSV.
What if a name is too long?
It is shrunk to fit its layer, and values over the length limit are refused before checkout.
Can I charge more for bulk orders?
Yes. Set a per-row charge, a setup fee per line, or both.
Next steps
Read the Bulk Personalization docs, then try it with a five-row list of your own to see the files you would get. The launch announcement has the rest of this week's releases.