See all services Shopify Plus Partner
Pos Global

Migrate POS Receipt Templates Before the Liquid Cutoff

Shopify POS now manages every printed receipt type in one content editor, and customized Liquid receipt templates retire on January 1, 2027. Plan the migration while both formats can still run side by side.

Executive summary

What changed

The POS channel now exposes one content editor for printed receipts. Branding, header, and footer settings apply across every receipt type by default, with location level overrides for stores needing different wording. Built in fields cover return policy copy, a signature line, and regional tax identifiers including VAT, GST, QST, and ABN.

Two behaviours changed on the printed output itself. Return and exchange receipts render as one section with a single amount summary rather than two sections with two subtotals. Gift receipts no longer list line items, which makes batch printing practical, and gift card receipts can be set to print automatically or not at all.

Shops with customized Liquid templates have until January 1, 2027 to move. You can configure and preview the new template while the existing one keeps printing in stores. Making the new format live is a shop level switch, and it cannot be reversed. Shops still on Liquid at the deadline are migrated automatically.

Why it matters

Receipt templates are usually the least maintained surface in an enterprise retail stack. They were written once, often by a developer who has since moved on, and every later change queues behind theme and checkout work. Structured fields remove that queue for policy text, tax identifiers, and footer messaging.

The consolidated return and exchange receipt is the operationally significant part. Two subtotals on an exchange is a recurring source of confusion at the counter and a predictable driver of support contacts. One summary line reduces the explaining associates do per transaction.

The irreversible switch deserves respect. Treat it as a release rather than a settings change, and fold it into a wider POS configuration review rather than handling it alone.

Role-specific impact

Use-case example

Real-world scenario

A Plus merchant runs 42 North American stores on a Liquid receipt template customized in 2022 to carry bilingual return policy text and a Quebec QST number. Exchanges print two subtotals, and retail support logs roughly 30 receipt questions a week across the fleet. In the new editor, the bilingual policy and the QST identifier are both native fields, so the customization inventory reduces to one item: a flagship specific footer, handled by a location override. The team previews for three weeks while Liquid keeps printing, validates thermal printer output at four pilot stores, then flips the switch. Weekly receipt questions settle near 10.

Implementation checklist

  1. Inventory every Liquid receipt customization in production and note which locations depend on each.
  2. Map each customization to a built in field, a branding setting, a location override, or an accepted loss.
  3. Configure the new template in the POS content editor and use the real time preview while Liquid still prints.
  4. Print test receipts on real store hardware for sale, return, exchange, gift, and gift card scenarios.
  5. Confirm regional tax identifiers, return policy copy, and the signature line render correctly in every market.
  6. Decide gift card receipt auto print behaviour with the retail operations team.
  7. Schedule the shop level switch as a release with stakeholder sign off, since it cannot be undone.
  8. Brief store associates on the single summary format before the switch goes live.

FAQ

Q: Can we roll back after enabling the new receipt format?

A: No. The shop level switch is irreversible, so complete hardware and regional testing before you flip it. The preview and the live Liquid template run in parallel for as long as you need beforehand.

Q: What happens if we do nothing before January 1, 2027?

A: Shops still on Liquid are migrated automatically. Any customization that does not map cleanly to the new editor is lost without a controlled test first, so an unmanaged migration is the expensive path.

Resources

Customize your printed POS receipts

Need guidance? Talk to Makro.