Trigger flows based on how many times a specific subscription has been processed.

You can now use Subscription orders count as a condition in Automate and Rewards to build flows based on the lifecycle of an individual subscription.

This condition tracks how many times a single subscription has been processed—including the initial checkout and recurring orders—making it easy to trigger actions at key milestones.

For example, you can:

• Reward customers after a subscription has been processed a set number of times
• Build logic tied to subscription lifecycle stages (e.g., after 3 or 5 orders)
• Support use cases like installment-style payment flows

This value continues to increment even after a swap and will decrease if an order is refunded.

Note: Historical data is available for the past 6 months; earlier data is not backfilled.