Personalized Coated Cards: Proof a Variable Name List
Before engraving a variable name list, reconcile the CSV against the order and preview the longest, shortest, blank and duplicate records. Run one sacrificial coated-card proof with visible row identification before releasing the list.
A current LightBurn forum answer explains that variable-text output substitutes CSV fields line by line, directly exposing row, duplicate and preview risks. See the variable-text explanation.
Preview records in their actual sheet order. A clean first row does not reveal a blank field near the end, and an array offset can make later names pull from unexpected lines.
Prove the longest and missing records
1. Freeze an order export and keep it read-only.
2. Normalize leading spaces, blank cells and unsupported characters.
3. Flag duplicate customer or order identifiers for a human decision.
4. Preview the longest name in the actual card field.
5. Engrave one labeled proof and compare it with the source row.
A data error never justifies rushing a coated-card proof; pause on a row mismatch or any abnormal surface response.
| Workflow stage | Measured evidence | Boundary |
|---|---|---|
| Row count | CSV versus paid order | Must match |
| Blank field | Name or ID missing | Hold row |
| Duplicate | Same ID or exact name | Confirm intent |
| Overflow | Longest value exceeds safe area | Resize by rule or contact buyer |
Attach the previewed CSV row to the sacrificial card. Photograph row count beside its 'Must match' rule. Repeat that discipline for blank field, where the retained record is name or id missing.
Variable-data questions
Can the software skip an empty row automatically?
Do not assume so. Preview the actual data sequence and define how held records affect later rows.
What if two customers share a name?
Use an order ID or another non-public control field; a duplicate name alone is not proof of an error.
Can P2 engrave bare stainless cards?
This article is limited to verified coated or treated blanks; do not infer bare-metal capability.
Coated-card process boundary
Use the current P2 blue-laser product configuration and a coating-side proof. CSV behavior comes from the selected software workflow, not from the laser wavelength itself. The live TYVOK P2 listing is the source for dimensions and included hardware. Limit the list proof to verified coated or treated cards, never assumed bare metal.
Use Filled Logo: Should the Engraving File Be Vector or Raster? when the variable list also exposes a logo-format problem. Small Monthly Gift Orders: How Many Blanks Should You Stock? moves from data proof to inventory risk.
Release the list only after row count and longest-name proof agree.
