Planera for Shopify

Campaigns

Prepare collection changes ahead of time, then let Planera apply them on a date or a recurring schedule.

Campaigns

Prepare collection changes ahead of time, then let Planera apply them on a date or a recurring schedule.

Two ways to time a change

Use a Calendar Campaign for a launch, sale, seasonal switch, or other dated event. Use a Schedule when a collection should behave differently during recurring store hours or weekdays.

What a Campaign can change

Depending on the collection, a Campaign can prepare changes to:

Title-only and sort-only campaigns do not depend on collection population rules. When a Campaign changes conditions, Planera asks you to choose the collection logic it should update.

Safe condition changes

Shopify's current collection API can combine more than one set of membership rules. Planera updates only the collection logic selected for the Campaign rather than replacing the collection's complete membership definition.

Planera stores the condition definitions it changes. When an ended Campaign restores them, it matches their complete meaning and preserves unrelated collection logic and later merchant edits wherever it can do so safely.

The current creation flow focuses on Include changes. Planera may support other execution paths internally, but the merchant workflow exposes only the operations that can be reviewed safely.

How to create a Campaign

  1. Choose the collection.
  2. Select the collection logic to update if the Campaign changes conditions.
  3. Define the collection change.
  4. Choose a Calendar Campaign or Schedule.
  5. Review the preview before saving.

Restoration behavior

A Campaign with an end can restore the relevant state after it finishes. Restoration is scoped to what that Campaign changed; it is not a whole-collection rollback.

Start-only Calendar Campaigns apply the prepared change and leave it in place.

Overlapping Campaigns

Planera warns when Campaign timing or targets may overlap. The warning is advisory because some overlaps are intentional, but reviewing them helps avoid competing updates.

Practical examples