How do you proof names and dates on personalized products?

Define which kind of personalized image you are creating

A public image of a necklace engraved with “Avery” can show the personalization style. It is not a proof for the customer who ordered “Avéry.” A private approval image for that customer has a different obligation: it must match their intended spelling, accent, case and placement. The file sent to an engraver has another obligation: it must meet that supplier’s actual production process.

Keep these three roles separate in filenames and your own review records. Do not silently move a marketing mockup into the manufacturing folder. Label sample personalization clearly in the storefront where appropriate, and use invented example names for public testing rather than a real customer’s personal information.

Make the role visible in the working record: public sample, private customer proof or production artwork. A public example uses invented text; a private proof uses the actual authorized order information and should not be copied into campaign samples. Use the packaging-text review for unchanged printed labels; this workflow adds customer-specific variables and approval versions.

Capture the variable as an approved string

Keep the requested text as a separate string, then settle any ambiguity before visual production. Copy the customer-approved accent, case, punctuation and line breaks. Record a date’s intended meaning independently from its display: for example, an invented sample date of 5 April 2026 can be displayed in the agreed format, whereas “04/05” alone leaves the meaning unresolved. Do not silently “correct” a name or date to a more familiar form.

Shopify’s line_item documentation, checked October 21, 2026, describes custom properties as name/value pairs captured through a product form or Cart API, including an engraving example. It also distinguishes variant, cart/checkout and order-line identity. Preserve the actual order and line context in your external record; a shared product variant is not enough to distinguish two customers’ text. Capturing a value does not validate the artwork.

Use generation for presentation, not the final text authority

Use Product images to explore composition from a truthful product source. A generated “Avery” scene is not a proof for an order specifying “Avéry.” If lettering changes, retain the approved string and move exact artwork to a suitable external editor or supplier workflow. Enlarging a sharp-looking wrong word does not make it correct.

Compare the final downloaded file with the approved string character by character, including repeated letters, accents and digits. Inspect the intended readable view, not only the reduced workbench preview. Automated text recognition, if your external process uses it, is an aid rather than the final authority for stylized or engraved characters. This article does not claim an CartVisual OCR or order-to-engraver integration.

Review the customer proof without approving unseen production

Send the customer the appropriate proof through your existing business process, with a readable view of the personalization and the stated approval scope. Ask them to confirm the exact text and intended placement. If the rendering uses approximate material appearance or scale, explain that limitation instead of allowing the mockup to imply a physical sample was produced.

The supplier should independently confirm font support, printable or engravable area and file requirements. A generated italic accent may look plausible yet be unavailable in the real typeface. Keep customer approval linked to the correct order and version in your external system; generating a newer scene must not overwrite the already approved spelling.

Approve text and placement against a named proof version. Record which export was shown to the customer, which reply applies to it and what the supplier still needs to approve. After a revision, do not attach the old “approved” reply to a different file. Use the proof-version workflow for that handoff and the image review checklist for product accuracy apart from lettering.

Run a small exception test before using the workflow repeatedly

Proposed exception exercise, not an executed accuracy benchmark: use invented entries for a short name, a long name, “Avéry,” repeated initials and an unambiguous date. For each, preserve the expected string, actual exported appearance and the observed difference. Do not prefill a pass from the fact that the request contained the right text. The goal is to locate a manual artwork or clarification step in your own process.

If an accent disappears, return to the approved string and the supplier’s supported typeface; do not remove it from the order without approval. If the long name overflows, ask for an approved supported layout rather than silently shortening it. If the customer changes the date after approval, hold the old production file, create a new proof version and obtain the required new decision before the supplier proceeds.

Check the actual supplier file against the final approved text and placement. Record separate states for customer proof approval, supplier production approval and physical output if one is later made. Neither a generated mockup nor a customer’s approval proves that an unseen manufactured item is correct.

Personalization order-to-artwork record

Copy this external record for the actual item and file being reviewed. Fill from retained evidence and observed results. Empty cells and unresolved facts are not approval.