Starting the week of October 26, we’re upgrading Ordergroove’s connection to your Shopify store to use a more secure type of access token. You don’t need to do anything. The update happens behind the scenes, and your subscriptions, orders, and storefront keep running as usual.

On January 1, 2027 Shopify will begin enforcing all public apps, Ordergroove included, to use expiring offline access tokens. The change is designed to better protect your store’s data. We’re rolling the upgrade out early and in phases, so every store is switched over before the holiday rush.

Questions? Reach out to your Ordergroove CSM or our support team. For the technical details, see Shopify’s developer announcement.

As of October 20, 2026, Card Update Visibility is out of Early Access and available to all Ordergroove merchants. You don’t need to sign up. It’s already live in your analytics.

It tracks every payment update across your subscriber base, broken down by source and by decline reason. That lets you put a real number on payment recovery: how many rejected orders get a card update, and how much revenue comes back when they do.

If you were part of the Early Access, nothing changes on your end. For more on what it can show you, see the original Early Access announcement.

Get started: Head to Analytics > Retention & Churn in your Ordergroove Admin, open the Customer Actions tab, and select Subscription payment updates from the Customer Action dropdown. For a chart-by-chart walkthrough, see Customer Actions View.

Our developer documentation has moved to docs.ordergroove.com. It's the same documentation your developers use today — same guides, same endpoints, same reference content — rebuilt on a new platform, and it's live now. What's changed is what's around it: a live API explorer, code examples in nine-plus languages, and a site your team's AI coding assistant can actually read.

What's new

• Built for AI coding assistants: The new site publishes llms.txt, serves clean Markdown to any agent that requests a page, and ships an MCP server for the API reference. When you ask Cursor or Claude how to create a subscription in Ordergroove, you get our actual endpoints instead of a plausible-looking guess.
• An interactive API explorer: Authenticate and send a real request from the reference page you're already reading — no Postman setup, no copying cURL into a terminal to see what comes back.
• Code examples in your language: Every endpoint ships examples in nine-plus languages, generated from the spec, so a Python developer isn't mentally translating our cURL samples.

Get started: Visit docs.ordergroove.com. If something doesn't look right, please let your Ordergroove CSM know.

item.sku_swap is now available in the webhook UI. Select it on any webhook integration and you’ll get an event every time a SKU is swapped on an item in an upcoming order, including one-time swaps that apply only to the next order.

Previously, this event wasn't exposed for you to subscribe to. Now your OMS, ERP, and analytics can pick up a swap the moment it happens.

Here's what's new:

• Subscribe from the webhook page: item.sku_swap now appears under Item events, alongside item.create, item.change_quantity, and the rest. Check the box and it's part of that integration.
• Payloads in Delivery: Swap events show up in the Delivery section of Webhooks, so you can inspect exactly what was sent and confirm it landed.
• Catches one-time swaps: subscription.sku_swap fires only when the subscription’s product changes. item.sku_swap fires when the product in an upcoming order changes, so it also catches one-time swaps that leave the subscription as is.

One note: item.sku_swap isn't available for Klaviyo or Attentive integrations, as item events aren't fully compatible with those platforms.

With SKU Swap now available in the Customers page and the Customer Service App, this closes the loop. Between item.sku_swap and subscription.sku_swap, the systems downstream of Ordergroove hear about every swap the moment it happens, whether it changes a single order or the subscription going forward.

Get started: Head to Webhooks in your Ordergroove Admin and select item.sku_swap on any integration.

Updated 10/14/26: Clarified that item.sku_swap fires on items in upcoming orders. For subscription-level swaps, use subscription.sku_swap.

As of September 8, 2026, the previous Customers page has been retired. The new Customers page is now the only version.

Your existing links still work. If your team has bookmarks or saved links pointing at the previous version, they now redirect to the equivalent page on the new Customers page. Nothing breaks, nothing needs re-saving, and no one gets stranded mid-ticket.

If your team hasn't spent much time on the new page yet, here's what changed:

• A ground-up redesign: Faster to scan and navigate, and it loads natively in your admin instead of an embedded frame.
• SKU Swap: Change the SKU on an active subscription — prepaid included — without canceling and re-creating it.
• Digital subscription support: Digital subscriptions are now supported on the Customers page.
• Oriented from the start: The page opens with a customer list instead of an empty search box, and search results preview key details before you open a profile.

Everything the previous version did, the new page still does — with fewer clicks to answer a simple question, and no more workarounds for the things the old page couldn't do.

Questions or concerns? If something looks off, or your team is missing a workflow they relied on, contact your Ordergroove CSM or our support team. We'd rather close the gap than have you build around it.

Get started: Head to Data > Customers in your Ordergroove Admin. For what's changed and why, see New Customers Page. For step-by-step guidance on managing subscribers and their subscriptions, see Modifying Customer and Subscription Information.

The new Product Price Code API is live; you can now read, create, update, and delete price codes on a product directly through our Product APIs. Previously, price codes could only be set through the SFTP product feed - so teams managing their catalog through the API still had one piece of their pricing living in a file drop.

Here's what's new:

• List and retrieve price codes: Pull every price code on a product in a single call, or check one code directly to confirm it exists before you write to it. A product can carry as many codes as your program needs.
• Create and update in bulk: Send one code or many in a single request. Codes you include are set or overwritten; codes you leave out stay exactly as they are, so a partial update never wipes the rest of a product's pricing.
• Delete a price code: Remove a single code from a product once it's no longer in use.

For API-first and headless builds, that's one less feed dependency to maintain - your catalog and your pricing now sit behind the same integration.

Get started: Reference documentation is live for each operation: list, retrieve, create/update, and delete. Questions about how price codes fit your pricing setup? Reach out to your Ordergroove CSM.

Our developer documentation is moving to docs.ordergroove.com. It's the same documentation your developers use today — same guides, same endpoints, same reference content — rebuilt on a new platform, and it's live now. Nothing you rely on goes away. What's changed is what's around it: a live API explorer, code examples in nine-plus languages, and a site your team's AI coding assistant can actually read.

developer.ordergroove.com stays up until August 27, 2026. After that it's retired, and we'll redirect its URLs to their equivalents on the new site so existing links and bookmarks keep working.

What's new

• Built for AI coding assistants: The new site publishes llms.txt, serves clean Markdown to any agent that requests a page, and ships an MCP server for the API reference. When you ask Cursor or Claude how to create a subscription in Ordergroove, you get our actual endpoints instead of a plausible-looking guess.
• An interactive API explorer: Authenticate and send a real request from the reference page you're already reading — no Postman setup, no copying cURL into a terminal to see what comes back.
• Code examples in your language: Every endpoint ships examples in nine-plus languages, generated from the spec, so a Python developer isn't mentally translating our cURL samples.

Get started: Visit docs.ordergroove.com. If something you relied on is missing or a page doesn't look right, let your Ordergroove CSM know - we’ll get it fixed before the old site goes away.

The new Customers page is out now. It's the same page your team uses to manage subscribers and their subscriptions, rebuilt from the ground up — everything the previous version does, plus the additions and fixes below.

Nothing your team does today goes away, and the new page should feel familiar within a few minutes. If anyone needs the version they're used to while they get their bearings, it's one click away.

What's new

• A ground-up redesign: Faster to scan and navigate, and it now loads natively in your admin instead of an embedded frame.
• SKU Swap: Change the SKU on an active subscription — prepaid included — without canceling and re-creating it.
• Digital subscription support: Digital subscriptions are now supported on the Customers page.
• Oriented from the start: The page opens with a customer list instead of an empty search box, and search results preview key details before you open a profile.

Need the previous version?

Click See Previous Version at the top of the Customers page to switch back. It stays available until September 7, when the previous version is removed and the new Customers page becomes the only version.

If there's a specific reason your team needs the previous version, let your CSM know before then. We'd rather close the gap than have you lose a workflow you depend on.

Get started: Head to Data > Customers in your Ordergroove Admin. For a full tour of what's changed, see What's New in the Customers Page.

Recurring Revenue Waterfall shows you where expected recurring revenue moves throughout any given month to help you understand the difference between expected vs. actual revenue. Look across cancellations, moves or skips, additional upsells, and payment retries, and finally get the details needed to build action plans grounded in data.

Here's what's new:

• Waterfall view: See scheduled revenue and every movement bucket at a glance (red = revenue lost, green = revenue gained)
• "Not Captured" view: Pinpoint your largest churn sources– whether from involuntary churn like payment rejections or out-of-stock, or from cancellations– to prioritize the right fix first
• Month-by-month table view: Compare revenue values and success rates across time periods, side by side

The result? A complete picture of recurring revenue performance: detailed enough to spot leaks early, prioritize the highest-impact fixes, and align stakeholders around a single source of truth.

Get started now

This update is now live in your analytics by visiting Data > Revenue Waterfall.

👉 Learn more here.

As of July 22, 2026, Auto Retry is live on all Ordergroove accounts unless you opted-out. The moment a subscriber updates their payment method, we now immediately re-attempt payment on any eligible subscription sitting in retry. No more waiting for the next scheduled attempt or a manual Send Now.

If your subscriber email communications mention a manual retry step, for example asking customers to wait for the next payment attempt, that step is no longer needed. Auto Retry re-attempts payment the moment a card is updated, so please update any messaging that references it.

If you were running a custom retry workflow — for example, listening for payment-update webhooks to trigger your own Send Now — this is your reminder to confirm it's been fully disabled. Left running alongside Auto Retry, it can cause duplicate payment attempts.

Notice something off?

• What to look for: Duplicate or unexpected payment attempts on a subscription - most likely if a custom retry automation is still active. You can view payment attempts in Ordergroove > Data > Order Logs
• What to do: Confirm any custom retry workflow is fully disabled, then contact your Ordergroove CSM or support with the affected subscription IDs

Learn more: How Do Credit Card Retries Work?