Until now, a subscription discount showed up as a single number, ex: $6 off, with no explanation of where it came from. Discount Transparency (in Early Access) breaks that total into its parts, so you and your subscribers can see exactly which incentives are applied, how much each one contributed, and what each applied to.

Here's what's new:

• Every incentive, itemized: A discount total is now broken into the individual incentives behind it. A $6 discount becomes "$4 from free shipping, $2 from your 10% subscriber discount" — so the savings are never a mystery.
• The full context behind each discount: Every line shows the incentive's name, how much it took off, what it applied to (an item, the whole order, or shipping), and the order in which incentives were applied.
• Available across the Subscription Manager and your APIs: The same breakdown is accessible in the Subscription Manager and through the API, including GraphQL.

By replacing a single lumped-together number with a clear, itemized breakdown, Discount Transparency answers the question subscribers ask most — why am I getting this discount? — while giving your team the incentive-level data it's long asked for, whether that's reassuring a subscriber before they enroll or reconciling discounts downstream.

Get started: Please reach out via the Discount Transparency form if you are interested in participating in the Early Access for this feature.

Display every incentive a subscriber earns directly on the PDP, not just the headline offer. PDP Benefits Messaging (in Early Access) surfaces the full set of benefits on the enrollment widget, so subscribers see everything they're getting before they enroll.

Here's what's new:

• Surface the full value upfront: Display every incentive a subscriber earns directly on the PDP, not just the headline offer. For example: "Save 10% on your first order, 10% on all future orders, every 5th order free, and an extra 10% when you have at least 4 items in your order."
• Configure once, control everywhere: Write your own benefits copy per incentive type (Nth order, threshold, prepaid, customer group, and more), per locale, and per offer profile — with full control over what displays. Messaging is off by default and fully opt-in.
• Convert more subscribers: Conversion tests consistently show that subscribers convert better when they understand the complete value they're getting before they enroll.

By surfacing every subscription benefit on the PDP, PDP Benefits Messaging lifts subscriber conversion and grows recurring revenue — showing shoppers the full picture right where they decide whether to subscribe.

Get started: Please reach out via the PDP Benefits form if you are interested in participating in the Early Access for this feature.

When a subscriber successfully updates their payment method, Auto Retry (now in Early Access) immediately attempts a new charge on eligible subscriptions in retry — no waiting for the next dunning cycle, no manual trigger. Previously, those subscriptions sat until their next scheduled attempt, even after the subscriber had already fixed their card.

Here's what's new:

• Instant retry on payment update: As soon as Ordergroove detects a successful payment method update, it immediately re-attempts payment on eligible subscriptions in retry — instead of waiting for the next scheduled attempt.
• Automatic, across the board: Any eligible subscription currently in retry is picked up automatically. If the payment succeeds, the subscription resumes its normal lifecycle right away.
• Your existing safeguards still apply: Standard retry rules and payment processing safeguards continue to work exactly as before. Orders that have already exhausted the dunning flow aren't affected — only subscriptions actively in a retry state.

By shrinking the time between a card update and a successful charge, Auto Retry recovers more revenue sooner and reduces involuntary churn — recovering subscriptions while subscriber intent is highest, right when they've taken action to fix the problem.

Note: If you currently listen for payment update webhooks and manually trigger a retry (e.g. Send Now), disable those workflows to avoid duplicate payment attempts — Auto Retry now handles this for you.

Get Started: Reach out to your CSM or Ordergroove Support to get Auto Retry enabled for your store.

Every extra step in updating their card is a chance for a subscriber to walk away. Frictionless Card Updates (in Early Access) let customers update their payment method directly from an email via authenticated link: meaning no login, and no friction. Just a click, and they're back on subscription.

Here's what's new:

• Secure no-login link sent on payment failure: As soon as an order is rejected, your subscriber receives an email with a unique, tokenized link to update their card.
• One-tap card entry in a hosted modal: Subscribers tap the link, enter their new card in a secure modal, and they're done. No navigating their portal or Shopify to update information.
• Applied across all active subscriptions instantly: The new card replaces the old one on every active subscription the subscriber has — not just the one that failed — so you're not solving the same problem twice next month.
• Failed order retried automatically: The rejected order is immediately retried with the new payment method, so the subscriber gets the product they were expecting without ever having to ask.

What this means for you:

• Recover revenue you're losing today to subscribers who would've stayed if updating their card took five seconds instead of five minutes
• Shrink the window between payment failure and churn — the longer the gap, the more subscribers reconsider the subscription itself
• Free your CX team from the manual card-update tickets that pile up every billing cycle

Get started: Please reach out via this form if you are interested in participating in the Early Access for this feature.

Card Update Visibility in Customer Actions (in Early Access) shows you every payment update happening across your subscriber base — where they're coming from, how many are recovering rejected orders, and which decline reasons are actually recoverable. So when you invest in payment recovery, you can see the clear revenue impact.

Here's what's new:

• Payment Updates by channel, over time: See total payment updates broken down by where they came from
• Payment Updates on Rejected Orders: A dedicated view of what % of rejected orders were followed by a successful payment update, with a view of rate and raw count
• Recovery rate by rejection code: A breakdown showing rejected orders, payment updates, and update rate for each individual decline reason— so you can tell which rejections end up being most recoverable 

What this means for you:

• Easily quantify the impact of your payment recovery efforts
• Spot downward trends in subscriber card updates before they show up as churn
• Make the case internally for further investment in payment recovery with data your finance team will recognize

Get started: Please reach out via this form if you are interested in participating in the Early Access for this feature.

The order.retryable_placement_failure Klaviyo event now includes rejected_code and rejected_message fields, giving you the detail you need to tailor customer communication around orders that failed but are still in the retry flow.

Previously, this level of rejection detail was only available on the order.reject event – which fires for initial non-retryable rejections or once all retries are exhausted. Now Shopify merchants can craft messaging earlier in the failure lifecycle, while the order is still recoverable.

What's new:

• rejected_code and rejected_message are now included in the order.retryable_placement_failure event payload (Shopify merchants).
• Use these fields in Klaviyo flows to send targeted, reason-specific messaging during the retry window – not just after final rejection.
• No changes needed on your end – the fields will appear automatically on all newly generated events.

Get started:

Check out the Information Sent to Klaviyo article in the Knowledge Center for the full event payload and filterable properties.

Ordergroove GraphQL– an API designed for building high-performance, customer-facing subscription experiences – is in Early Access. With GraphQL, developers can query subscriptions, orders, and related data like items, product details, payment methods, addresses, and more in a single structured request, replacing the need to stitch together multiple REST calls. This is purpose-built for headless architectures and latency-sensitive customer journeys. Early adopters are already seeing 30–50% improvements in page load times, with Subscription Manager loading in as few as 1–2 queries.

Here's what's new:

• Single-query data fetching: Query subscriptions, orders, and related data like items, products, payment methods, and addresses in one request.
• Dramatically reduced API calls: Replace 10+ REST calls with a single, UI-tailored query to load Subscription Manager.
• No new auth model: Uses the same authentication as your existing REST integration.
• Typed, discoverable schema: Production-ready and compatible with modern tooling and headless frontend frameworks.

What this means for you:

• Faster customer-facing experiences.
• Less backend API orchestration complexity.
• Simpler, more maintainable frontend code.

Get started: Please reach out via this form if you are interested in participating in the Early Access for this feature. You can also visit our Developer Documentation to learn more. 

Rejection rates rise for many reasons, but until now, it's been hard to see which payment methods are actually behind the shift. Our Rejection Rate by Payment Method Mix chart (in Early Access) breaks rejection rate down by payment method, weighted by how much of your business runs on each, so you can tell the difference between a real threat to revenue and noise at the margins.

Here's what's new:

• Rejection rate by payment method, over time: See how Shop Pay, Apple Pay, Credit Card, Google Pay, and PayPal each perform week-over-week, with the overall rejection rate trendline overlaid for context.
• Bubble size = share of your business: Each payment method's share of subscription volume is reflected in the size of its bubble, so a high rejection rate on a method only a handful of subscribers use looks very different from the same rate on a method 40% of subscribers rely on.
• Spot mix shifts before they hurt revenue: If a high-rejection method starts gaining share, the bubble grows and the impact on overall rejection rate becomes immediately visible– no more guessing why your number is moving.

What this means for you:

• Diagnose the why behind rejection rate trends in seconds
• Catch payment method shifts before they materially impact revenue
• Make targeted decisions about which payment methods to optimize, prioritize, or address

Get started: Please reach out via this form if you are interested in participating in the Early Access for this feature.

Analyze your product performance with more precision. The product filter in the Analytics overview now has two key upgrades:

• Filter by product type: Isolate digital products vs. physical products so you can analyze each category without the noise of the others combined. For our Digital Merchants (Early Access), this is especially impactful: you can now view digital-only subscription performance without physical products skewing your data.
• Search and select all: Search a keyword and select all matching products at once, then layer in another search to build your exact product set — no more selecting items one by one.

Available now for all merchants. Digital product type filtering is available for Digital Merchants (EA).

Get started in Analytics now.

Subscription order add-ons now automatically inherit the currency of the customer's order, bringing cross-sells fully in line with the rest of your multi-currency experience. This update also extends to subscriptions created through the CSA, ensuring currency consistency across the board.

The result is a seamless, currency-aware subscription experience for every customer, in every market.

Here's what's new:

• Subscription cross-sells now inherit the order's currency – just like one-time add-on items have always done.
• Subscriptions created through the CSA now match the currency of a customer's existing subscriptions.
• The subscriptions-create-in-order and subscriptions-create-from-item API endpoints have been updated to support this behavior.

What this means for you:

• Unlock cross-sells across all markets
• Consistent experience for every currency
• More revenue, zero manual workarounds

Get Started Now

This is live now and works automatically – no changes needed on your end. Check out the updated API docs for subscriptions-create-in-order and subscriptions-create-from-item, or visit the Shopify Markets Multi-Currency guide in the Knowledge Center to explore everything that's now supported.