What’s new

For security, a signed-in dashboard session is deliberately short-lived and renews itself while you work. If you left a tab sitting open and came back to it later, that renewal had not happened yet — so the next thing you loaded or saved came back as an error that looked like the feature itself was broken. Panels said they could not load, actions said something went wrong, and the only way out was to reload the page or sign in again.

The dashboard now notices the moment a session has gone stale, renews it in the background, and quietly repeats whatever you were doing. You get the result you asked for instead of an error you had no way to act on.

If you keep several dashboard tabs open, they all share one session, so they renew it together: coming back to a pile of idle tabs at once gets you back to work in every one of them, and never signs you out.

Nothing that already ran gets repeated. The renewal only applies to requests the server turned away before doing any work at all, so a save, a send or a charge can never happen twice because of it.

If the session really has ended — you signed out somewhere else, or changed your password — you get the usual sign-in prompt, exactly as before. This covers the merchant dashboard; your customers' portal has always had its own separate sign-in and is unchanged.

The MCP server now serves protocol revision 2026-07-28 as well as 2025-06-18, and picks the revision per request — so a client can move across whenever it is ready, with nothing to switch on our side.

2026-07-28 is the stateless revision: there is no initialize handshake, and each request declares the revision it speaks. A new server/discover method — answered on either revision — reports the revisions this server supports, what it can do, and which server you reached, in one call.

Clients on 2025-06-18 are unaffected: same endpoint, same API keys, same scopes and rate limits, and their existing calls return exactly what they returned before. Nothing to update.

The request framing, headers, and examples for the new revision are documented at /docs/developers/mcp-server.

Your data is always yours, and now that's a button: Settings → Your data — no lock-in → Download subscriber book (CSV). No support ticket, no waiting period, no fee.

The file uses the exact columns our own importer accepts, so it round-trips — into another subscription app, into your own systems, or straight back into WallaB. Every subscriber is included, not just the live ones: active, paused, and cancelled all export, so your churn history travels with you.

We think switching costs should be earned, not engineered. Leaving being easy is the point — it makes trying WallaB a smaller risk, and it keeps the pressure on us to be worth staying for.

Switching to WallaB no longer means starting over. Upload a CSV of your existing subscribers and their plans, review a full dry-run validation report — every row checked, nothing written — then commit the import once it is clean.

Prefer to start fresh, or just kick the tires? Add subscribers one at a time instead — the import page offers both paths. Imports never charge anyone and never send email: billing stays untouched until each subscription's own next billing date.

WallaB read-only data API is now available over the Model Context Protocol (MCP) — connect an AI assistant or agent (such as Claude) to WallaB through a standard remote MCP connector and let it securely read your subscription data on your behalf.

The MCP server is a thin adapter over the same data API: the same owner-created API keys, the same Growth-plan gate, the same per-key rate limits. It exposes read-only tools for entitlements, subscriptions, the metrics summary, selling plans, and cancel-save outcomes — nothing that can change your data.

Available on the Growth plan and above.

Create scoped API keys in Settings and read your entitlements, subscriptions, retention metrics, selling plans, and cancel-save outcomes from your own systems.

Cursor pagination, per-key rate limits by plan, and machine-readable OpenAPI and llms.txt so tooling and AI agents can discover the API. Available on the Growth plan and above.

Shoppers subscribe through your theme's own product form, and see a clear cadence and discount label in the cart and at checkout — no separate widget, and purchases flow through Shopify native checkout.

Offer free trials, a founding-member discount, and referral rewards to bring more shoppers onto subscriptions.

Define bundles in the admin, and let subscribers customize what is in their box from their portal.

Reach lapsed and at-risk subscribers with scheduled, rate-paced campaigns. Fallback messaging is multilingual so customers hear from you in their language.

Import subscribers with a guided CSV importer, including a Recharge-shaped adapter and a generic mapping for other platforms.