Scheduling
Configure merchandising date ranges and understand scope, inclusive end dates and timing limitations.
Merchandising rules have optional start and end dates. Use these to bound a promotion's eligibility, alongside its enabled state, scope and matching conditions. Confirm the resulting storefront order before relying on a campaign.
Setting a date range
- Open Merchandising in FilterIQ and create or edit a rule.
- Choose the action, target products and the search or collection scope you intend to affect.
- Expand Schedule and set the start and end dates as required.
- Save, reopen the rule and verify the stored dates and enabled state.
- Preview an eligible query or collection, then test a query outside its scope and a shopper filter that excludes the target product.
An end date before the start date is invalid. Omitting a boundary leaves that side of the date range open; it does not bypass scope, matching conditions or a disabled rule.
Date boundaries and timing limitations
The current evaluator uses the server's calendar date and compares the date portion of the stored values. The end date is inclusive: the rule remains date-eligible on that date and becomes ineligible after it. This is not a minute-level or store-timezone scheduling guarantee.
| Date evaluated | Date eligibility |
|---|---|
| Before the start date | Not eligible |
| On the start date | Eligible, subject to other conditions |
| On the end date | Eligible, subject to other conditions |
| After the end date | Not eligible |
For a promotion tied to a specific local midnight, flash-sale time or timezone change, confirm timing with the team before use. The presence of a date picker does not prove those boundaries. Saved configuration, index freshness and the rendered storefront must all be checked.
A scoped promotion example
Suppose you want selected sale products to be more prominent in a particular collection. Choose those targets, set the collection scope, and set a start and end date. Compare the product order before and during the eligible period using the same sort and filter state.
A pin is similarly scoped: it does not put a product into every search result, override shopper constraints or make an unavailable variant purchasable. Record the product identities and the intended positions when checking the result.
Overlapping rules
Several rules can be eligible at once. Review priority, actions and scope together, including any hide rule and the shopper's active filters. Test the actual combined result; a schedule alone does not determine precedence or guarantee a product's position.
Review and rollback
Keep the previous configuration and your acceptance queries. After the end date, repeat the same queries and check that the promotion no longer affects eligible results. If behavior differs, disable the affected rule through the available editor and verify the storefront; retain the dates, scope and observed product order for support.
Use descriptive names and review old rules regularly. See the merchandising guide for the surrounding configuration workflow and contact the team for private-preview availability.