Recharge Pricing: Calculate Your Effective Subscription Cost

Recharge pricing needs a consistent order denominator

Recharge pricing becomes comparable when every proposal uses the same paid-order population and the same definition of billable activity. The useful output is an effective cost per paid subscription order, with merchant operating costs shown separately. A monthly platform fee cannot answer that question, and dividing by every active subscriber produces a different measure altogether.

For a Shopify Plus or paid-platform operator doing $3M–$30M in revenue, the decision is usually an investment in an existing subscription business. You need to know what the agreement charges for, what your team must still do and which improvement makes the added commitment worthwhile. A feature catalogue does not establish any of those economics on its own.

The proprietary worksheet here controls the denominator before comparing costs. It distinguishes billable events used to reconstruct the vendor invoice from paid orders used to evaluate the programme. It also isolates the break-even point of a different quote. Those distinctions prevent a cheaper-looking plan from winning because its comparison quietly counted a different set of orders.

This evaluation is not for a brand below that revenue floor or a business still testing whether customers want repeat deliveries. A mature merchant with a straightforward, satisfactorily performing subscription operation also should not buy extra complexity merely because a proposal contains more features. Procurement needs an identified problem and an owner prepared to act on it.

What does the Recharge pricing page establish?

Recharge’s official pricing page presents subscription plans with monthly charges and transaction-based fees, alongside a custom volume-based option. Use those charge categories to structure a quote request. Put the applicable rates from your written proposal into the worksheet instead of treating a copied public rate card as a complete account-specific agreement.

The public page also distinguishes plan scope and discloses a separate per-message-segment charge for Concierge SMS. It describes implementation and migration support within its higher-tier offering. These disclosures make a practical point: a feature’s presence in a plan and the total cost of using it are separate questions. Confirm the exact scope and usage treatment in the proposal.

A comparison should not assume that an advertised support inclusion covers all merchant implementation work. Ask Recharge which deliverables its team owns, which dependencies your team must provide and what constitutes completion. Those answers matter more than the word “included” when an engineer still needs to investigate a legacy integration or a subscription manager must approve customer-facing behaviour.

For recharge shopify pricing enquiries, request an explicit separation between Recharge charges and charges from Shopify, payment providers or other connected services. Ask the relevant provider to confirm each line rather than assuming that similarly named fees replace one another. The cost model should show the full programme budget without attributing every subscription-related payment to Recharge.

Which export should you send with a quote request?

Send a representative activity export organised around charge events, not a screenshot of subscriber growth. Include the period, currency and filters used to create it. A commercial proposal is easier to audit when the vendor can show exactly which rows enter its calculation and finance can reproduce those totals from the same source data.

Separate initial subscription checkouts, recurring renewals, add-on purchases, unsuccessful attempts and refunded charges. Add prepaid collections and their associated fulfilment records as distinct categories when relevant. These are proposed classifications for asking billing questions, not claims that every category is billable. Leave an unanswered inclusion rule marked metric to confirm until the vendor supplies a written definition.

The input sheet should make the proposal reproducible, including the categories excluded from billing.

Preserve the distinction between a subscriber, an agreement, an order and a charge. A customer can have several agreements; an agreement can exist without a paid order in a particular period. A fulfilment record may represent delivery of goods paid for previously. Combining those records into a single count makes effective-cost comparisons hard to interpret even before vendor pricing enters the model.

Ask for a sample invoice calculated against the export. Require explanations for differences between your expected counts and the vendor’s result. Resolve those differences before asking for a discount: a reduction applied to an unknown base is not yet a dependable saving. Procurement should keep the accepted sample with the contract so future billing reviews have a reference calculation.

Calculate effective platform cost and effective operating cost separately

Define effective platform cost per paid subscription order as the relevant Recharge charges divided by the consistently defined paid-order count for the same period. Keep any other provider charges outside this measure. A platform-specific measure lets you compare commercial proposals without concealing their differences inside fulfilment or marketing spending.

Define effective subscription operating cost per paid order more broadly. Add the merchant labour, connected services and recurring maintenance required to run the programme, then divide by the same paid-order population. Label this measure clearly. A lower platform cost can coexist with a higher operating cost if the proposed configuration requires more staff time or outside support.

Use a cost sheet with named inputs: fixed platform charge, quoted percentage rate, agreed billable revenue, quoted event fee and agreed billable event count. Add contracted usage charges and adjustments as their own lines. Avoid a single blended rate until the underlying components reconcile; the blend is an output for comparison, not a replacement for the invoice logic.

The proposed calculation is:

Recharge cost = fixed charge
              + quoted revenue rate × agreed billable revenue
              + quoted event fee × agreed billable events
              + other contracted usage charges
              + invoice adjustments

Effective platform cost = Recharge cost ÷ paid subscription orders

Effective operating cost = (Recharge cost + recurring merchant costs)
                           ÷ the same paid subscription orders

Keep the paid-order denominator constant across proposals even when billable event rules differ. If a vendor counts an event differently, that difference belongs in its invoice calculation. Changing the denominator as well would make the comparison easier to manipulate and harder to explain. Finance should be able to point to the same underlying set of paid orders for every result.

A month with no paid orders requires a different presentation: report absolute cost and explain the absence of activity. Do not invent a cost-per-order value by dividing through an estimated subscriber count. A prepaid programme may also need a separate cost-per-fulfilled-order view, but that measure should remain explicitly labelled rather than silently replacing the paid-order definition.

The hidden costs are often work, usage and incentives

The line items missing from a headline fee are not automatically undisclosed vendor charges. Some belong to the merchant because adoption creates work. Others are separate usage charges or costs of the retention strategy itself. Keeping those categories distinct makes the article’s cost analysis fair to the vendor and more useful to the person approving the budget.

Implementation labour includes requirements gathering, catalogue decisions, subscription data preparation and review of the proposed customer experience. Estimate those tasks with the people doing them. A vendor migration service may reduce effort, but finance should only remove an internal task when the written scope actually transfers responsibility and the receiving party has accepted it.

Integration ownership needs a budget beyond launch. Identify the systems that depend on subscription events and assign a person to investigate discrepancies. Ask your technical team which dependencies require custom work and which can be supported through the proposed configuration. The presence of an integration in a catalogue does not answer your organisation’s responsibility for monitoring its business outcomes.

Customer service preparation is another real deliverable. Agents need to recognise an agreement, understand the customer-facing changes and know when to escalate a billing exception. Budget time to rehearse the scenarios your programme allows. A support team that cannot explain a renewal adjustment may create refunds or repeated contacts that never appear on the platform invoice.

Messaging costs should follow billable usage rather than campaign labels. If your proposal charges by message segment, ask for an estimate using the actual content and markets you plan to serve. Keep the vendor-confirmed unit beside the forecast. A spreadsheet row labelled “messages” is insufficient when the commercial unit is more specific than the operator’s everyday vocabulary.

Retention incentives belong in contribution calculations. A discount, free product or shipping concession changes the economics of the saved renewal. Record those costs against the audience receiving the offer, including any associated fulfilment expense. Do not credit the programme with full-price retained revenue while hiding the incentive in a separate marketing budget.

Require every claimed saving to name the invoice, task or expense that disappears. “Included in Recharge” is not a saving until your team can retire the existing cost without leaving an operating requirement uncovered.

When does a higher-cost proposal become cheaper in practice?

A higher fixed charge can be economically preferable if its variable charges or genuinely avoidable operating costs are sufficiently lower. Calculate the crossover from the written proposals using the same revenue and event assumptions. Treat any additional commitment as part of the comparison, especially if the forecast volume that justifies it is not yet established.

For the plan decision, compare the extra fixed commitment with variable-charge savings at the projected activity level. Add evidenced labour or service savings only when their removal is feasible. If the higher-cost proposal also enables a valuable new workflow, evaluate that contribution separately so you can distinguish a billing saving from an unproven performance improvement.

The proposal with the lowest effective cost at forecast volume may not have the lowest downside exposure.

Calculate the crossover using both collected revenue and event count when both drive charges. Average order value links those variables but is not guaranteed to stay fixed. A plan that works well for larger renewal baskets can look different after customers move to smaller, more frequent deliveries. Ask the model to show that change instead of hiding it in a blended average.

Run a downside scenario in which subscription collections weaken while fixed commitments continue. Keep the assumptions internally consistent: weaker collections can reflect fewer paid orders, lower order value or both. The scenario should explain the mechanism. A generic revenue haircut applied without changing transaction counts may describe a different business from the one you are evaluating.

Compare alternatives without manufacturing a rate card

Compare Recharge, an incumbent platform and a credible alternative only after each proposal meets your non-negotiable operating requirements. Use the same exported activity, evaluation period and merchant labour assumptions. A named alternative with an unknown scope is not yet a comparable quote, even if a public monthly price looks attractive in a search result.

Your requirements should describe subscriber outcomes rather than vendor terminology. For example, state how a customer must be able to change an upcoming delivery and which downstream records must reflect that decision. Ask each vendor to demonstrate the required behaviour using your scenario. Record any custom work or operating workaround before ranking the commercial options.

A competing proposal may include a different allocation of implementation or ongoing support. Normalise those differences explicitly. Do not assume that “migration support” means the same deliverables across companies, or that an integration removes the same amount of internal work. The Skio pricing evaluation offers a separate procurement context, but your written proposals remain the source for this comparison.

The incumbent deserves an improvement case too. Price the work needed to address the identified retention problem on the current setup, where feasible. Switching platforms should compete with that option rather than with an artificially neglected baseline. Keep this article’s commercial decision separate from the specific payment-recovery workflow covered in Recharge dunning.

Migration spending needs an acceptance boundary

A migration budget should buy a reconciled operating programme, not merely records visible in a new account. Define acceptance around subscriber agreements, charge ownership and the downstream fulfilment result. Ask Recharge and any implementation partner to allocate responsibility for each deliverable in writing. An unowned gap is a cost uncertainty even when the quoted project price is fixed.

Build a representative acceptance set containing the agreement types your business actually uses. Include unusual historical offers, paused agreements and prepaid obligations where relevant. Compare source and destination values for products, quantities, prices, discounts and scheduled actions. These are proposed checks to agree with the vendor, not assumptions that every legacy field can migrate unchanged.

Payment continuity should have a provider-approved plan. Ask which payment references and authorisations can be used, how exceptions are identified and who contacts affected subscribers if action is required. Keep sensitive payment credentials outside the commercial worksheet. Your cost estimate should include the work required by the confirmed plan, rather than assuming an unrestricted export-and-import process.

Specify which system is allowed to initiate each renewal during cutover. Require a reconciliation that can reveal missed or duplicate activity and a named owner for investigating it. Avoid treating a clean record count as sufficient evidence: matching counts can conceal different prices, different next-charge dates or different obligations for the same subscribers.

Hold the transition budget open until the agreed evidence is complete. Separate vendor completion, internal acceptance and old-service termination so procurement can see why overlap costs remain. A rollback or containment decision should have a named owner and documented triggers. Do not assume the old configuration can resume safely after the new system has already processed live changes.

Judge the return using incremental contribution

The return on Recharge spending should come from additional collected contribution, demonstrable operating savings or a necessary business requirement. Revenue attributed to an intervention is a starting point, not the economic result. Deduct the variable cost of delivering the order, the incentive used to retain it and the additional cost of operating the intervention.

Separate voluntary retention work from failed-payment recovery. The customer intention, intervention and measurement differ, so combining the groups too early obscures the source of any improvement. A payment-recovery claim should also distinguish collections that would have occurred under the incumbent process from collections attributable to the change. Otherwise the new programme receives credit for baseline activity.

Use the subscription churn calculator to expose your programme assumptions, and consult the DTC consumables churn benchmarks for context when evaluating comparable businesses. Neither tool supplies a guaranteed uplift for the proposal. The forecast should identify the customers affected, the mechanism expected to change their behaviour and the evidence needed to validate it.

Keep classification changes out of the performance story. If the new setup labels a delayed order, pause or cancellation differently, reconcile that difference before claiming retention improved. Compare collected outcomes across a suitable renewal horizon. A customer agreeing to postpone a shipment should not be valued as though another paid renewal has already occurred.

AI-assisted recommendations do not remove the need for commercial controls. Keep refunds under human approval, reject automated actions based on unreliable records and involve a person when a wrong answer is more costly than review. Budget that oversight as operating work. An automation proposal is only valuable when the team can judge its results and intervene when necessary.

Buy the proposal your team can operate and defend

Approve a Recharge proposal when finance can reproduce the charge calculation, operations can own the required work and the business case survives conservative assumptions. For scaling brands, engineering and subscription management capacity have competing uses. Include that opportunity cost in the decision rather than assuming available software creates available people.

Negotiate the unresolved mechanism before negotiating the headline number. Ask for clear billable-event definitions, scope acceptance and commitment terms where those drive uncertainty. A commercial concession is useful when it changes the cost of the programme you actually intend to run. It is less useful when the proposal still leaves the operating requirement unanswered.

Defer the purchase when the expected benefit depends on an unowned workflow, unreconciled data or a retention problem caused primarily by product and fulfilment failures. A platform cannot establish demand for a replenishment cadence that customers do not want. Fix the underlying condition or narrow the project until the investment has a plausible, measurable purpose.

Recharge pricing is a subscription retention decision because the sustainable return depends on valuable repeat orders after all associated costs. A consistent denominator, a reproducible quote and a funded operating plan make that decision reviewable. The right proposal earns its cost through the subscription programme you can actually run, not the feature list you could potentially use.