The Products List endpoint has been optimized to respond approximately 44% faster, with average response times dropping from 185ms to 103ms, with no changes required on your end. 

This is most impactful for high-traffic and headless builds: Merchants with large catalogs or latency-sensitive subscriber-facing UIs will see the biggest gains in page responsiveness.

Faster API responses mean better subscriber experiences, and for headless merchants building custom UI, every millisecond counts.

We are beginning a gradual rollout of these enhancements, and all merchants using this endpoint will be upgraded with no action needed. 

The Customer Service App (CSA) has been completely overhauled with new UI to make it easier for your teams to navigate and take action, plus the addition of native SKU swap to manage subscribers more efficiently.

Here's what's new:

• Full visual refresh: A completely redesigned UI that's even more intuitive and easy to navigate, so teams spend less time finding what they need and more time resolving tickets.
• Native SKU swap: Support teams can now swap a subscriber's product directly in the CSA. Previously, merchants needed to cancel and re-initiate subscriptions and no longer need to do this workaround. 

A more intuitive and robust CSA means faster ticket resolution, giving your support team the tools to deliver a better subscriber experience without leaving our platform.

Get started: Please reach out via this 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.

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.

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.

We’ve just released enhanced Customer Action Analytics to all merchants, with dedicated dashboards for every key subscriber action so you can go beyond overviews to understand the direction and magnitude of their actions, and spot patterns behind what subscribers are doing. 

Here’s what’s new:

Customer Actions now have dedicated views that go deeper than aggregate numbers: 

• Order Date Changes: See if subscribers are pulling dates forward or pushing them out– and by how many days 
• SKU Swaps: Learn which products are swapped most, and whether subscribers are trading up or down in price
• Frequency changes: Understand if subscribers are moving to more or less frequent deliveries, and which intervals are most switched to
• Quantity changes: Discover if subscribers are increasing or decreasing quantity, and by how much
• Skips: Explore patterns of how your subscribers skip, with even more views coming soon

The result? A complete picture of subscriber behavior: detailed enough to spot patterns early, act before churn happens, and build a retention strategy grounded in data. 

Get started now

This update is now live in your analytics by visiting Analytics > Retention & Churn > Customer Actions. 

👉 Read more here.

Give your integrations only the access they need: API Key Read/Write Permissions

With Read/Write Permissions, you can now scope each API key to exactly what it needs - read-only access for reporting and data sync, or full read and write for operational integrations. Following the principle of least privilege is security best practice, and now we make it easy to apply it across your entire integration ecosystem.

Here's what's new:

• Create API keys with Read Only (GET) or Read & Write (POST/PATCH/DELETE) permissions
• Edit permissions on any key after creation
• Existing keys automatically inherit Read & Write permissions, so no integrations break on day one

What this means for you:

• Scope third-party tools to only the access they actually need
• Reduce the risk of accidental or unauthorized data changes
• Build and audit your integration ecosystem with confidence

Get Started Now:

API Key Read/Write Permissions are now available. Head to your API settings to review and update your keys.

We've updated how certain rejected orders appear in the Rejected Order Reasons section of your Orders Analytics tab. Specifically, orders that were in a payment retry cycle and subsequently superseded by a Send Now action will now surface with more detail than before, previously showing “NA”.

What is a "810" Rejection Code?

When a subscription order fails due to a payment issue, Ordergroove automatically retries it based on your store's retry settings. If a Send Now action is triggered on a subsequent order for the same subscriber while a retry is still in progress, Ordergroove automatically rejects the retrying order to prevent a duplicate shipment from going out. This is expected platform behavior and it protects your subscribers from being charged or shipped twice.

Previously, these rejections appeared with limited detail:

• In Orders Analytics, the rejection code and text appeared as N/A
• In the API, Order.rejected_message appeared as {}

What’s changed:

• Rejection Code: Instead of N/A, the Rejection Code field now displays 810, making it immediately clear why the order was rejected.
• Rejection Text: Instead of N/A, the Rejection Code field now displays "Order superseded by Send Now"
• API Response: Instead of {}, the Order.rejected_message field now returns: {'code': '810', 'message': 'Order superseded by Send Now'}

What to Expect:

The Rejected Order Reasons table in the Orders Analytics tab reflects these new formats immediately.

If your team exports rejection data or uses it in a data pipeline, you will see the updated rejection code and message appear.

No action is required within the Ordergroove platform. You can view this table in Data > Analytics > Orders.

Questions?

If you have questions or notice unexpected behavior in your data, reach out to your CSM or to the support team.

SendNow has been upgraded to run near real-time across all merchants, completing in seconds.

What's new:

• SendNow requests are fulfilled in near real-time, eliminating processing delays.
• No changes are needed from your end–  the SendNow endpoint works exactly as before, just faster. 

Holiday promotions and test offers have a habit of sticking around forever. To fight the clutter, you can now archive unused offer profiles and keep your subscription promotions clean, organized, and easy to manage. 

Plus, new filter views let you view promotions by active or archived status.

What’s new:

• Archive with confidence: Offer profiles can be archived as long as they don’t have active subscriptions and aren’t part of a live A/B test.
• Smart recovery: If a subscription on an archived offer profile is reactivated, we’ll automatically unarchive it for you.
• Faster searching: Find the promotion you’re looking for faster with a new dropdown menu that lets you filter by archived or active status.
• Better API filterability: Enhancements to the Offer Profile List endpoint let you filter offer profiles by archived or active status.

What this means for you:

• Manage your incentives efficiently and safely.
• Find the promotion you’re looking for, faster.

Get Started Now:

Offer Profile archiving is available to you now! Head to Flex Incentives in Ordergroove to clean up your promotional roster. 

And if you’re interested in more OOTB promotional setup, ask your Ordergroove CSM about the new Self-Serve Flex Incentives Alpha today.