Skip to content

Preview (how it works + coverage)

Preview is your safety check before running a job. It loads a sample of matching products/variants and shows the before → after values for the fields your action will change.

What Preview does (and does not) do

  • Preview focuses on the fields that will actually change, so you can validate patterns, text operations, and price math before running a job.
  • Preview is a sample view for speed (it does not attempt to load every matching row for very large scopes).

Preview coverage by field

This table mirrors the in-app Preview coverage table.

Field / actionUnderlying field(s)How it appears in Preview
TitleProduct titleText operations (replace, prepend, append) and patterns. Shows a single before/after row per product.
DescriptionProduct descriptionText operations and patterns on the product description. Preview shows the resolved description text.
SEO TitleProduct SEO titleText operations and patterns on SEO title.
SEO DescriptionProduct SEO descriptionText operations and patterns on SEO description.
HandleProduct handleText operations and patterns on the product handle.
VendorProduct vendorText operations and patterns. Can combine vendor with product/variant variables (for example, vendor plus SKU).
Product typeProduct product typeText operations and patterns on product type.
TagsProduct tagsAdd or remove tags. Preview shows the full tag list before and after (for example, “Summer” → “Summer, New”).
Variant priceVariant pricePer-variant rows. Supports set, percent/absolute increase or decrease, rounding, and helpers that set compare-at prices.
Variant compare-at priceVariant compare-at pricePer-variant rows. Shows compare-at price before and after when compare-at is changed.
Variant SKUVariant SKUPer-variant rows. Supports text operations and patterns (for example, [PRODUCT_PREFIX]-[SEQUENTIAL]).
Variant barcodeVariant barcodePer-variant rows. Supports text operations and patterns on barcode.

Tips

  • Start with a small filter scope and use Preview to confirm the right products/variants are targeted.
  • For patterns, always check a few sample rows to confirm variables resolve the way you expect.

Was this helpful?

Need help interpreting Preview? Visit the Support & contact checklist for what to include (shop URL, screenshots, job ID), then email support@xyppy.com or open an issue at GitHub Issues.