Subscription and Recurring Revenue Commerce with Elastic Path: B2B Beyond One-Off Orders

Subscription and Recurring Revenue Commerce with Elastic Path: B2B Beyond One-Off Orders

For most of the last fifteen years, B2B commerce has been built around the purchase order. Buyer logs in, browses a catalogue, places an order, gets it shipped, gets invoiced. The transaction is the unit of value, and the underlying commerce platform is fundamentally an order capture engine. By 2026 this model is no longer sufficient. A growing share of B2B revenue comes from subscriptions, managed service plans, equipment-as-a-service arrangements, consumables auto-replenishment, and platform-level licensing — recurring revenue structures that the traditional B2B order model fits poorly.

The shift is significant for two reasons. First, recurring revenue is more valuable to the seller — predictable cash flow, higher customer lifetime value, deeper buyer relationships, more compounding network effects. Second, the buyer increasingly expects it. B2B buyers who consume subscription software in their own organisations are unsurprised when their suppliers offer subscription-based propositions, and they will switch to suppliers that do.

This article addresses Elastic Path subscription commerce — what it is, how it differs from one-off order handling, what the data model looks like, and how to integrate it with payment, dunning, customer self-service, and reporting. It is written for B2B commerce directors and product owners who are evaluating or actively building subscription propositions on Elastic Path.

The article is deliberately practical. McKenna Consultants delivers composable commerce engagements on Elastic Path, and the patterns described here are the patterns we apply in production builds.

Why B2B Subscription Commerce Is Different

Subscription commerce in a B2C context is well-understood. A consumer subscribes to streaming, to meal kits, to a SaaS product, to a coffee club. The transaction shape is largely uniform: a fixed plan, a fixed price, predictable billing cycles, simple cancellation and renewal logic.

B2B subscription commerce is meaningfully more complex.

Multi-product subscription. A B2B subscription frequently bundles multiple products and services. A managed service plan might include hardware (rented or sold), software licences (per-seat or per-feature), professional services hours, and consumables (replenished monthly). Each line of the bundle has its own commercial dynamics. The platform must represent the bundle as a coherent commercial proposition while preserving the line-level economics.

Negotiated and contract pricing. The price of a B2B subscription is rarely the catalogue price. Contract pricing applies — sometimes per customer, sometimes per business unit, sometimes per project. The platform must support contract-aware pricing across the subscription lifecycle, including renewals where the contract terms may evolve.

Approval and procurement integration. B2B buyers operate inside procurement processes. A subscription is not generally bought by a single buyer at a self-service checkout; it is procured through a multi-step approval workflow that may involve purchase orders, contract review, and integration with external procurement systems (Coupa, SAP Ariba, Oracle Procurement Cloud).

Mid-cycle changes. Real B2B subscriptions change in flight. A customer adds seats, removes seats, upgrades plans, downgrades plans, changes payment terms, adds new bundle components. The platform must handle these changes with correct proration, correct invoicing, and correct downstream entitlement updates.

Renewal complexity. B2B renewals are not silent. They are negotiated. Pricing changes, terms change, scope changes. The platform must support renewal workflows that are visibly different from initial subscription creation — including surfacing renewal opportunities to account managers ahead of expiry rather than auto-renewing without negotiation.

Hybrid catalogues. Most B2B sellers do not stop selling one-off products when they introduce subscriptions. The platform must support a single buyer experience that combines purchase orders for one-off products and subscription orders for recurring revenue lines, often within the same shopping session.

These differences are why B2C subscription platforms — Recharge, Bold, the consumer-focused Stripe Billing tier — do not generally fit B2B requirements without substantial customisation. A composable B2B commerce platform is the natural home for B2B subscription commerce because composable architecture allows the subscription, billing, and entitlement components to be selected and integrated specifically for B2B requirements.

What Elastic Path Brings to the Subscription Commerce Picture

Elastic Path’s composable commerce platform offers a few specific capabilities that make it well-suited to B2B subscription commerce.

Subscription offerings as a first-class catalogue concept. Elastic Path represents subscriptions as offerings with associated plans and billing schedules, distinct from one-off products but living in the same catalogue. A buyer can browse a catalogue that contains both, add items of either type to a cart, and check out through a unified flow. The subscription offering data model supports the multi-product, contract-priced, approval-gated patterns B2B subscriptions require.

Pricing flexibility. Elastic Path’s price book and price modifier model supports contract pricing applied to subscription offerings, tiered pricing across volume thresholds, account-specific overrides, and time-bound promotional rates. The same flexibility applies to one-off and subscription products, which simplifies the operational model for catalogue managers.

API-first architecture. Every subscription operation is available through the Elastic Path API: creating a subscription, modifying a subscription mid-cycle, terminating a subscription, querying entitlements. Composable architecture means your application is the orchestrator — you can integrate Elastic Path subscription state with your CRM, your finance system, your customer portal, and your fulfilment system through clean API contracts rather than through brittle middleware.

Account hierarchy support. B2B subscriptions live within account hierarchies — buyers, sub-accounts, business units, parent companies. Elastic Path’s account model supports these hierarchies natively, which is essential when a single subscription serves multiple sub-accounts or when consolidated billing crosses business units.

Composability with billing platforms. Elastic Path does not implement payment processing or billing engine logic itself for subscriptions; it integrates with specialist billing platforms (Stripe Billing, Recurly, Chargebee, native subscription gateways for specific use cases) and with ERP-based billing engines (SAP, Oracle, Microsoft Dynamics). This separation of concerns is a strength — the billing platform is the system of record for monetary obligations, while Elastic Path is the system of record for catalogue, customer relationship, and entitlement state.

The Data Model

A working Elastic Path subscription commerce implementation has six core entities.

Subscription Offering. The product-catalogue representation of “what is on offer.” Offerings encapsulate the bundle composition, the plan options, the billing schedule, the eligibility rules, and the associated entitlements. Offerings are the equivalent of a subscription product in the catalogue.

Subscription Plan. A specific commercial expression of an offering — a price point, a billing frequency, a contract length. Multiple plans typically exist per offering (monthly, annual; basic, professional, enterprise). Plans are the unit a buyer selects.

Subscription. An active relationship between a customer and a plan. The subscription record holds the current plan state, the pricing, the billing schedule, the start and end dates, and the references to upstream and downstream systems (CRM contact, billing customer, fulfilment record).

Subscription Item. A line within a subscription. For multi-product bundles, each component is a subscription item. Items can be modified independently — a customer adding ten seats to the user-licence component while leaving the consumables component unchanged.

Billing Schedule. The recurring billing pattern for a subscription. Monthly, quarterly, annually, custom. The billing schedule drives invoice generation in the integrated billing platform.

Entitlement. The downstream consequence of an active subscription. When a subscription is active, the customer is entitled to specific products, features, or services. The entitlement is consumed by your application — it is the answer to the question “what is this customer allowed to do today?”

A clean implementation keeps these entities cleanly separated. The subscription is the commercial record. The entitlement is the operational record. The billing schedule produces the invoices. Conflating them produces brittle integrations and operational pain at scale.

Payment Provider Integration

Elastic Path subscription commerce delegates monetary processing to specialist payment and billing providers. The integration choice depends on the shape of your business.

Stripe Billing is the most common choice for SaaS-style subscriptions and works cleanly with Elastic Path through the standard payment integration patterns. Stripe Billing handles invoice generation, payment retry logic, subscription state synchronisation, and dunning. Your Elastic Path implementation creates the customer, the subscription, and the plan in Stripe; Elastic Path holds the catalogue and entitlement state.

Recurly is a strong choice when subscription complexity is high — multi-currency, multi-tax-jurisdiction, complex proration scenarios. Recurly’s domain model is built for subscription-first businesses and integrates well with Elastic Path’s offering model.

Chargebee sits in similar territory to Recurly with broader procurement-system integration and is a strong choice for B2B subscription businesses with complex contract structures.

ERP billing engines (SAP, Oracle, Microsoft Dynamics, NetSuite) are the right choice when subscription billing must align with enterprise financial systems for revenue recognition, audit, and consolidation. ERP integration is more involved but is the canonical posture for organisations with established financial system requirements. In an ERP-billed model, Elastic Path’s role is unchanged — catalogue, customer, entitlement — and the ERP becomes the billing system of record.

The integration pattern in all cases is the same: events flow between Elastic Path and the billing platform via webhooks and explicit API calls, and the business logic that resolves conflicts is implemented in your application’s orchestration layer. Composable architecture pays its dividend here — you build the orchestration once and can change billing providers without rebuilding the catalogue.

Proration, Mid-Cycle Changes, and the Operational Details

The single biggest source of B2B subscription pain is mid-cycle change handling. The patterns that work in production:

Define the proration model explicitly. Prorate-at-change versus prorate-at-renewal versus credit-on-next-invoice are all valid options, and each has different commercial implications. Choose deliberately for each subscription type and document the choice. Mixing models without clear rules produces invoicing surprises.

Treat downgrade and upgrade asymmetrically. B2B customers typically expect upgrades to take effect immediately and to be billed pro-rata. Downgrades are conventionally deferred to the next renewal date — partly to avoid mid-cycle revenue dilution, partly to give the seller a window to negotiate a retention plan. The platform configuration should support both behaviours per offering.

Manage entitlements on the change boundary, not at the next billing event. If a customer adds ten seats today, those seats should be entitled in your application today. The billing system catches up at the next invoice cycle; the entitlement system reflects the change immediately. Coupling entitlement state to billing state creates a class of bugs that are hard to diagnose later.

Provide clear customer-facing previews of mid-cycle changes. Before applying an upgrade or seat-count change, show the customer the prorated charge, the next invoice impact, and the effective date. B2B buyers strongly prefer predictability over surprise, and a transparent change preview reduces support ticket volume measurably.

Dunning, Recovery, and Churn

Failed renewals are a fact of life. Card expiries, insufficient funds, declined transactions — they happen even in mature B2B accounts. The dunning sequence — the structured attempt to recover failed payments — is a standard feature of every billing platform and should be configured deliberately.

The patterns that work:

• Three to five retry attempts spread across the first ten days of the renewal cycle, with smart-retry logic that times retries based on payment provider success patterns.
• Active customer outreach alongside automated retries. For B2B accounts, a failed renewal is often a procurement issue (the purchase order has expired, the budget has been re-categorised, the buyer has changed) rather than a payment issue. Direct contact with the account owner resolves these faster than retry logic ever will.
• Grace periods before service interruption. B2B customers expect a window of continued service while billing issues are resolved; the typical pattern is seven to fourteen days post-renewal-failure before service is paused.
• Clear escalation to dispute resolution if a customer disputes a renewal. Subscription terms must be clearly evidenced, and your platform should be able to produce the evidence chain on demand.

The metrics to monitor:

• Voluntary churn rate (customer-initiated cancellations).
• Involuntary churn rate (failed renewals not recovered).
• Net revenue retention — the most important single metric for B2B subscription health.
• Renewal-cycle support ticket volume — a leading indicator of friction in the renewal process.

Customer Self-Service

B2B subscription customers expect self-service surfaces for the subscription operations they perform routinely. The minimum viable surface:

• Current subscription state — what is active, when does it next bill, what does it cost.
• Seat or quantity management — add and remove subscription quantities subject to plan-level rules.
• Invoicing history — invoices generated, payments made, outstanding balances.
• Payment method management — update card details, change payment terms.
• Plan change — upgrade, downgrade, switch billing frequency (subject to commercial rules).
• Cancellation and pause — initiate cancellation or pause with appropriate workflows.

A well-designed B2B self-service portal handles the routine 80% of customer-initiated subscription operations without contact, freeing the account management team to focus on strategic conversations. Elastic Path’s API surface supports all of these operations directly; the work is presenting them in a buyer-friendly interface that aligns with the rest of your buyer experience.

Reporting and the Metrics That Matter

Subscription commerce produces a different reporting surface than transactional commerce. The standard reporting set:

• MRR and ARR — monthly and annual recurring revenue, broken down by plan, by segment, by region.
• Net revenue retention — the rate at which existing customer revenue grows or contracts over a period, before new customer revenue.
• Gross revenue retention — net revenue retention excluding upsell.
• Churn rate — percentage of customers cancelling per period.
• CAC payback period — how long it takes for a customer’s accumulated revenue to recover their acquisition cost.
• LTV — total expected revenue from a customer relationship.
• Cohort analysis — how customers acquired in a specific period are performing over time.

These metrics depend on subscription data being clean and consistent across systems. Elastic Path’s role is to be the source of truth for subscription state — what plans exist, what subscriptions are active, what their current value is. Reporting tools (Looker, Tableau, Power BI, native data warehouse builds) consume this data, often via a data warehouse pipeline that joins subscription state with billing realisation and CRM relationship data.

For organisations standing up subscription commerce for the first time, agreeing the reporting taxonomy at the start of the build is more valuable than any specific reporting tool choice. The taxonomy is what determines whether finance, customer success, and sales talk about the same thing when they say “MRR” or “churn.”

How McKenna Approaches Subscription Commerce Engagements

McKenna Consultants delivers Elastic Path subscription commerce engagements as a packaged build with clear phases:

Discovery. Subscription commerce architecture review, integration mapping (billing platform, CRM, ERP, fulfilment), data model design, reporting taxonomy definition.

Foundation. Catalogue setup with subscription offerings, pricing model implementation, billing platform integration, basic subscription lifecycle (create, renew, cancel).

Mid-cycle and self-service. Mid-cycle change handling with proration, customer self-service portal, dunning configuration.

Advanced. Account hierarchy modelling for complex B2B accounts, ERP integration where relevant, reporting pipeline build.

A typical end-to-end engagement is sixteen to twenty-four weeks. Smaller engagements — adding subscription commerce to an existing Elastic Path catalogue, or replacing a brittle subscription extension with a clean integration — are six to twelve weeks.

McKenna is a UK-based Elastic Path consultancy with deep B2B commerce experience across industries — manufacturing, distribution, professional services, industrial technology. If your organisation is building or evaluating subscription commerce on Elastic Path, contact us to discuss your situation.