scheduling recurrence

Re-evaluate products for each occurrence

Learn how to re-evaluate products for each occurrence with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Dynamic selectors are resolved again when each occurrence starts. Catalog edits between occurrences can therefore change the included products; static selections remain fixed.

Before you begin

• Confirm the shop timezone and trading windows
• Decide span versus separate daily windows
• Choose how the series stops

Keep the campaign in Draft while you verify the configuration. Use a private storefront window where the guide changes shopper-facing behavior.

Step-by-step setup

Open full size ↗

1. 1

   Choose all products, rules, collections, or a hand-picked selection.

2. 2

   Define the matching condition used to keep the selection current.

3. 3

   Confirm the number of matching products before continuing.

4. 4

   Inspect matching products, variants, and original prices in the preview.

1. In Products, choose All products, Conditions, or Collections rather than a manual list.
2. Configure optional variant refinement and exclusions.
3. Review the current resolved preview and note that it is time-specific.
4. Return to Basics and preview multiple recurring occurrences.
5. Before major catalog changes, remember the selector resolves again when each occurrence activates.

Dynamic selectors are resolved again when each occurrence starts. Catalog edits between occurrences can therefore change the included products; static selections remain fixed.

Juniper & Trail example

Juniper & Trail uses re-evaluate products for each occurrence for a repeat trail-hour promotion. The team previews several future occurrences and checks that each occurrence has an apply and revert boundary. The documentation fixture uses realistic products, inventory states, variants, collections, and protected exclusions so the preview exercises the same decisions as a merchant catalog.

What shoppers will see

The promotion turns on and off for each occurrence; there is no intended midnight flicker inside a continuous span. Check the relevant result from product through cart where applicable. For shopper-facing work, compare desktop and mobile and verify both an eligible and an ineligible item.

Common mistakes and troubleshooting

• Acting on the wrong shop. Confirm the Shopify store and campaign before following Re-evaluate products for each occurrence.
• Trusting a stale preview. Refresh after catalog, schedule, discount, theme, locale, or market changes.
• Repeating a background command. Read status and History first; retry only when Badgy presents a recoverable failure.
• Skipping the consequence check. Confirm what changes for shoppers and what the end or restore path will do.

If the status reports revoked authorization, reconnect Shopify before retrying. If the result still differs from the preview, preserve the campaign ID and approximate time, then open support from this identified shop. Never send customer data, access tokens, or full catalog exports in feedback.

Related guides

• Repeat a campaign monthly
• Stop a recurring campaign series
• Choose a one-time campaign schedule

Options reference

| Option | Use it when | Consequence | | --- | --- | --- | | All products | Future catalog items should join | Re-resolves each activation | | Conditions | Eligibility follows catalog fields | Results change with field values | | Collections | Eligibility follows collection membership | Membership changes affect later runs | | Manual selection | Freeze IDs | Does not re-evaluate rules |

Badgy behavior in this guide is reviewed against the repository's shipped UI, service rules, and feature design documents. Shopify-owned theme, Markets, Flow, billing, and discount behavior can also depend on the store's Shopify configuration; consult the Shopify Help Center for that platform configuration.