A gift message is not an order note
Gift checkout fields are everywhere again — Checkout UI Extensions make a text box easy to add on Shopify. The failure mode is not collecting the words. It is treating those words like Shopify's freeform order note: one mutable string that customer service, delivery instructions, and the card enclosure all share. On Al's Flowers the message has to land on a printed ticket and a card the recipient sees. That is an operational field, not a scratch pad.
One string cannot hold three jobs
An order note is usually whatever fits: the buyer saying leave it by the gate, the shop writing that the recipient is out until three, and sometimes a card message the florist is supposed to hand-letter. Those are different lifecycles. Delivery instructions change when the driver calls. Staff notes accumulate as the order moves. The gift message should freeze once the buyer commits it — or change only through an explicit edit the shop can reprint from.
When everything shares one field, the last writer wins. A helpful update in admin quietly deletes the card copy. The ticket reprints without it. Nobody notices until the arrangement goes out with a blank enclosure, which is the kind of failure customers remember and dashboards do not.
Collect it as structured checkout data
If the store sells gifts, model the fields the shop actually uses: whether it is a gift, the card message, and any flags that change fulfillment — hide prices on packing slips, include a blank card, skip a receipt in the box. Persist those as order attributes or metafields with stable keys, not as prose dumped into `note`.
Checkout Extensibility is the right capture surface in 2026. Keep the UX boring: optional message, a hard character limit the card can physically hold, and no requirement that forces abandoned checkouts. Accelerated wallets often skip custom note mutations; plan a post-purchase path or a cart attribute that survives express pay, otherwise you will collect messages only from the slow checkout.
Carry it onto the operational record
Shopify owning the order does not mean the workroom should read Shopify. On Al's Flowers, webhooks ingest into an operational record that already carries delivery window, address, and ticket type. The gift fields belong there too, copied on ingest with the same idempotency rule as everything else: replaying the webhook must not invent a second message or blank a good one.
The PDF ticket is the contract with the bench. Put the card message in its own labeled block, separate from delivery instructions and internal notes. If PrintNode already printed and the message later changes through an order edit, void or supersede the old ticket — do not hope someone notices a second sheet in the tray. A reprint without a void is how two different cards leave the shop.
Edits need a message lifecycle
Orders get edited. Windows move. Line items swap. Gift copy changes less often, but when it does the shop needs a clear state: original message, revised message, and whether the enclosure was already printed. Treat that like any other fulfillment-affecting edit — subscribe to the edit webhook, compare the structured fields, and only then queue a reprint.
Customer service still needs a place for freeform notes. Keep that channel. Just do not make it the source of truth for anything that prints onto a card. If a buyer emails a rewrite, the agent updates the gift message field and triggers the same reprint path the checkout edit would. The note can say why; the field holds what.
What we ask before we schedule a gift field
Where does the message appear — packing slip, enclosure card, both? Who is allowed to change it after payment, and does that change require a reprint? What is the character limit the physical card can hold, not the textarea default? What happens on Apple Pay or Shop Pay when the extension cannot write a note?
If the honest answer to "where does this print" is nowhere, you do not need a gift message system — you need a note field and lower expectations. If it prints, give it a key, a place on the operational record, and a reprint rule. Collecting sentiment in checkout is easy. Delivering the right words with the arrangement is the product.