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?

The Incentive Builder now supports two new condition types based on order quantity criteria. This opens up a variety of use cases with our self-serve builder, like Buy More, Save More tiers, order thresholds, per-product quantity discounts, and more.

Here's what's new:

• Order quantity conditions: Trigger incentives based on the total number of items in a subscriber's order, total subscription items only, or count of distinct subscriptions — perfect for order-level Buy More, Save More offers and minimum quantity thresholds.
• Per-product quantity conditions: Set conditions based on units of a specific product, with support for both "greater than" and "less than" thresholds — enabling product-level quantity offers, bundle discounts, and more.

With these new conditions, we're giving you more ways to launch offers directly from the Incentive Builder, no engineering required.

Get started: Incentive Builder is already available today in Open Beta. Head to Flex Incentives in your Merchant Dashboard to start building with these new conditions. For guidance on getting started, visit our Knowledge Center or reach out to your Ordergroove CSM.

Failed payments cost the average subscription business close to 10% of ARR every year, and closing that gap has been one of our biggest pushes this year. You may have already spotted some of these as they shipped, but here's the full roundup of features to recover more revenue, make card updates effortless for your subscribers, and give you clearer visibility into what's actually driving rejections.

You can read more in our latest blog, and sign up for the waitlist for any early access features here.

Payments Roundup

• Payment Agent (Early Access) recovers more revenue from failed payments by continuously A/B testing retry strategies against your baseline- scaling the winners automatically, then starting the next test from that smarter place.
• Frictionless Card Updates (Early Access) gives subscribers a secure, one-tap link to update their card with no login required, and their failed order retries automatically once it's fixed.
• At-Risk Payment Banner (Early Access) flags at-risk payment methods with a banner the moment a logged-in subscriber lands anywhere on your site.
• The Subscribers-at-Risk API (Early Access) surfaces those same risk signals so merchants on headless or custom storefronts can build their own version of the at-risk experience.
• Auto Retry on Card Update automatically retries any orders stuck in retry the moment a subscriber updates their card, so there's no more waiting for the next scheduled sweep, or requiring customers to manually click "Send Now”. This will be rolled out as a new standard to all merchants starting July 22nd, and you can read more about the feature and how to opt out here.
• Rejection by Payment Method Mix (Early Access) breaks down your rejection rate by payment method in a bubble chart weighted by share of your subscription business on each one, so you can tell a real revenue threat from noise at the margins.
  
• Card Update Visibility (Early Access) helps you quantify the impact of your recovery efforts, with every payment update tracked across your subscriber base, broken down by channel and by decline reason.

Interested in getting early access to any of these features? Fill out this form to share your interest with our team, and they'll reach out when next steps are ready. 

On July 22, 2026, Auto Retry — instant payment re-attempts the moment a subscriber updates their card — becomes standard behavior on all Ordergroove accounts.

Using a custom retry workflow? Merchants who listen for payment update webhooks and manually trigger a retry (e.g., Send Now) must disable that workflow before July 22. Otherwise, your automation and Auto Retry will both attempt payment, which can result in unforeseen and compounding errors in your subscription program. Need more time to adjust? Opt out here.

Using the standard retry process? There's nothing you need to do — Auto Retry will be enabled automatically on July 22.

What's changing

• Today: a subscription in retry waits for its next scheduled attempt (or a manual Send Now) — even after the subscriber has already fixed their card.
• Starting July 22: as soon as Ordergroove detects a successful payment method update, we immediately re-attempt payment on eligible subscriptions in retry.
• 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.

What you need to do

• Most merchants: nothing. Auto Retry turns on automatically on July 22.
• If you listen for payment-update webhooks and trigger your own retry (e.g., a custom Send Now automation): disable that workflow before July 22. Otherwise, both your automation and Auto Retry will attempt payment, resulting in duplicate payment attempts.

Why we're making this change

• Faster recovery of failed payments — revenue is recognized sooner, and fewer subscriptions slip into involuntary churn.
• A better subscriber experience — no awkward gap between fixing a card and seeing the order go through. Recovery happens while subscriber intent is highest, right when they've taken action.

Need more time?

If you need to adjust conflicting automations, or need more time to check your set-up before the rollout, you can opt out via this form. You must complete the form by the end of the day on July 21, 2026. If we don't hear from you, your account will get Auto Retry starting on July 22. 

Learn more: How Do Credit Card Retries Work?

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.