When one product design is reused for many gift messages, a customer-specific note can quietly become part of the master artwork. Separate the product layer from the personalization layer before the order queue grows.
Start with a stable master file
Keep the product name, fixed graphic elements and reusable borders in one master file. Store the recipient name, date and gift message in a separate clearly labeled variant. The resulting proof makes it easier to see what changes from order to order.
Before approval, read the variant aloud against the order record and check punctuation, line breaks and recipient names. If a message is too long for the planned visual space, return it as an artwork question rather than silently compressing it.
Preserve the approval trail
Save the customer-approved variant with the date and the artwork version used. That record helps distinguish a later edit request from the earlier approved message; it is not a guarantee about production output or timing.
For an AntBelt G1 project, keep the master and variant files in a job folder with the related proof. The hero is a packaging-workflow illustration, not evidence of a specific order being completed.
Browse related planning notes in /updates/.