Failed Payment Recovery Email Analytics data is now limited to the past 6 months to improve performance.

Recharge updated Failed Payment Recovery Email Analytics to enforce a rolling 6-month data window. Previously, while a banner indicated this limit, merchants could still access older data, resulting in performance issues for stores with large datasets.

With this change, Recharge automatically removes records older than 6 months. As a result, you may notice slight changes in your metrics when viewing the dashboard.

See Failed Payment Recovery in the Recharge Help Center for more information.

You can now update pricing for dynamic bundle selections directly from the Bulk updates (Import) tool.

Previously, syncing updated Shopify prices for dynamic bundle contents had to be done by the Recharge support team. Now you can upload a CSV of subscription IDs, select Sync bundle selection prices, and Recharge will automatically pull the latest pricing from Shopify and apply it to existing subscriptions.

This update also introduces improved validation. During processing, Recharge checks whether bundle contents exist before applying updates, reducing unnecessary processing and speeding up the workflow.

See How to update bundle pricing in bulk for dynamic bundles in the Recharge Help Center for more information.

The Update customer tags node lets you automatically add and remove Shopify customer tags directly within your flows.

Previously, managing Shopify customer tags required manual work or external tools. Now, you can update tags natively within your flows in real time using the Update customer tags node.

This node lets you add, remove, or update tags in a single step, making it easier to manage customer segmentation and personalize downstream experiences.

This update makes it easier to automate tagging based on customer behavior, attributes, or flow conditions, helping power more targeted workflows and personalization.

This feature is currently available only in Automate. Tags must exactly match Shopify, and updates may take a short time to appear due to asynchronous syncing.

See Understanding the Update customer tags node for Automate flows in the Recharge Help Center for more information.

Building Automate flows just got more flexible. You can now add Conditional Branch nodes before the Smart Loop, and the Smart Loop itself is fully draggable and can be deleted within the canvas.

The Smart Loop is now available in the Add a node menu and can be placed anywhere in your flow (one per branch). It’s no longer locked in place and can be deleted, so you’re not required to use it unless your flow needs item-level logic.

Previously, Automate flows were required to start with a Smart Loop node, meaning every flow evaluated items individually, whether needed or not. This update gives you more flexibility and sets the foundation for upcoming nodes that won’t require a Smart Loop.

For example, you can:

• Only enter the Smart Loop if an order contains a specific product, and segment customers differently if it doesn’t
• Swap products based on total subscription spend by adding a conditional branch before the Smart Loop
• Combine high-level conditions with item-level evaluation for more precise automation

The Smart Loop still evaluates each item individually once entered, and existing flows will continue to work as expected.

See Getting started with Automate in the Recharge Help Center for more information.

Predefined Swap and Contact Support options are now available to include in your cancellation prevention offers.

Predefined Swap reduces decision fatigue by redirecting a cancelling customer to a single hero or best‑seller with one click, making it easier for your customers to choose a save. 

Contact Support surfaces a direct support channel inside the cancellation flow so your customers can get help with complex issues automation can’t solve, preserving relationships through human assistance. 

See the Recharge Help Center for more information about cancellation prevention.

You can now run multiple Automate flows at the same time, giving you more flexibility to organize and manage your workflows with simpler, easier-to-maintain flows.

This update removes the need to manage all unpacking and swapping logic in a single, complex flow that can be difficult to maintain. You can now split your logic into smaller, focused flows (for different products, schedules, regions, or customer segments) and reorder them as needed.

When an order is processed, Recharge evaluates active flows in priority order (top to bottom) and runs any flow whose trigger conditions are met. Flows can run sequentially if conditions allow, though we recommend using mutually exclusive triggers to avoid unintended sequencing.

For more information, see Getting started with Automate.

You can now block recurring charges for individual customers.

When a customer is blocked, all charge attempts fail, no matter where they’re initiated, including:

• The customer portal
• The merchant portal
• Failed payment recovery retries

This gives you a simple way to prevent recurring charges from processing successfully for specific customers. 

The Customer timeline now also logs every block and unblock event, including whether it was initiated by a Recharge admin or a store admin.

See Can I block a customer from subscribing? in the Recharge Help Center for more information.

We improved how cut-off windows behave for manual and recovery charges to ensure consistent billing dates.

Background

When you configure a subscription to charge on a specific day of the week or month, Recharge may skip the first billing cycle to avoid charging customers too soon after checkout. Cut-off windows give you more control over this behavior by defining when the first cycle should or shouldn’t be skipped.

For example, if your charge day is the 15th and your cut-off day is the 20th:

• A customer who checks out on March 17 will be charged on April 15
• A customer who checks out on March 22 will be charged on May 15

Previously, manual charges (like “Order now”) and charges processed through error recovery could unintentionally override this logic. In some cases, they updated the next charge date even when they occurred outside the cut-off window.

What’s new
Manual and recovery charges now follow cut-off window logic more accurately, ensuring they no longer override the expected billing schedule when processed outside the cut-off window.

See Charging on a specific day of the week or month in the Recharge Help Center for more information on this setting.

Automate can now read and act on custom properties stored on processed charge line items.

You can now use Processed charge line item → Property as a condition in:

• Trigger conditions: Control who enters the flow
• Conditional branch conditions: Control how customers move through it

This allows Automate to evaluate custom line item properties at order processing time and use those values to drive flow logic.

Information customers provide at checkout is often stored as line item properties, including:

• Quiz results
• Bundle selections
• Selected plan or cadence
• Custom configuration options

With this update, Automate can detect those properties when the order is processed, determine whether a flow should run, route customers down different paths, and reuse those values later in the flow (for example, when generating a subscription).

This allows flows to respond directly to the selections a customer makes at checkout, without relying on hardcoded variants or workaround logic.

For more information, see Getting started with Automate.

Merchants using gift subscriptions can now search gift orders by the sender’s or recipient’s email address.

Previously, you could only search gift orders using sender or recipient customer IDs. Now you can locate gift orders by the sender’s or recipient’s email address, making it faster to find and manage them for your customers. For more information, see the Recharge Help Center.