Products

When product replacement is on, the plugin replaces {variable} placeholders in the following product fields:

• Name
• Description
• Meta title
• Meta description

This affects how the storefront renders the product — listing pages, detail pages, breadcrumbs (insofar as the product name appears in them), and the <title> / <meta> tags in the HTML head.

Why it’s off by default

Product copy is high-stakes — it appears in search snippets, structured data, marketplace exports, and email confirmations. Turning replacement on changes the rendered output; the database value remains the raw {variable} string. That separation is by design but it makes some integrations (marketplace feeds that read the raw value directly) see a different string than the storefront.

Enable the scope intentionally:

1. Identify the variables you want to use in product copy.
2. Restrict each variable’s Scopes to Product so it cannot accidentally leak elsewhere.
3. Turn on Enable variable replacement in products in plugin settings.
4. Sanity-check the storefront and any feeds you export.

Use cases

• Shared disclaimers in descriptions — shipping caveats, allergens, certifications — managed once.
• Reusable USPs — {usp1}, {usp2} — that you tweak globally during promotions without re-editing every product.
• Marketplace-specific names — combined with per-channel values, the same product can be listed as Product A on your flagship store and Product A by Acme on a marketplace channel.

What is not affected

• Product images, prices, properties, options — these are not strings the plugin scans.
• Custom fields — fields stored on a product but not rendered through the standard product fields above are not touched. If you store rich HTML in a custom field, use the CMS scope or add a Twig template snippet that resolves variables on its own.