Tools and providers
Part of Which subscription commerce tools and providers fit a UK retailer's stack?
Check these criteria before subscription commerce software selection
A step by step guide to subscription commerce software selection, from requirements mapping and data protection checks to vendor scoring and total cost.
What to take away
- The decision is which platform your team can operate, audit and leave without losing subscribers or billing history.
- Requirements come before demosbilling models, tax, dunning, entitlement, payment methods, authentication, security, data flows and reporting.
- Cost the platform over three years, including payment fees, migration and internal time.
- Check your lawful basis for subscriber data, and safety evidence for any physical goods you ship.
- Shortlist on written answers, then run a paid pilot with the two strongest candidates.
Decide what must work on day one
Subscription commerce software selection starts with the flows your business already promises customers. A monthly coffee box and a software seat break in different places. Write each flow as a sentence: what starts it, what the customer pays, and what happens when a card fails. That list becomes the requirement document you send to vendors, and it keeps demos honest.
Map each customer flow
- What starts the flow
- What the customer pays
- What happens when a card fails
Integration decides most failed projects. If paid social drives sign-ups, the platform must pass purchase events back to Meta's advertising and catalogue tools. Read the official Meta Business Help Centre documentation before you promise tracking to the marketing lead.
For a wider view of the market and where each tool type fits, the subscription commerce tools and supplier guide maps the categories before you shortlist.
The market splits into all-in-one subscription-management platforms (for example Recurly, Chargebee and Zuora), payment-service-provider billing (for example Stripe Billing and GoCardless), and ecommerce subscription apps (for example Recharge and WooCommerce Subscriptions). Use the criteria below to compare the categories, not the sales demo.
Turn the flows into a written requirement list
Number the requirements once, then send the same list to every vendor. Use the categories below to build that list.
Written requirement list
- Billing models now plus two in 18 months
- Payment methodscard, Direct Debit, wallets
- UK VAT and overseas tax handling owner
- Dunningretries, emails, grace, pause
- Entitlementhow access is granted and revoked
- Monthly reporting and finance export format
Subscription-specific criteria to add
- Billing modelsproration on plan changes, trials and trial-to-paid conversion, upgrades and downgrades, and usage-based billing.
- Dunning and payment recoveryretry schedules, card updater services, involuntary churn reporting, and configurable dunning emails or grace periods.
- Entitlement and access controlhow active, paused, past due, cancelled and grace-period states map to access, plus team and customer portal roles.
- Tax and VATVAT calculation and invoices for UK sales, VAT on digital services for EU customers, US sales tax, and tax-tool integrations. Check HMRC-compatible records.
- Payment methodscards, Bacs Direct Debit, SEPA and wallets. For each, test setup, mandate or token handling, and failure paths.
- Authentication and regulationStrong Customer Authentication readiness under PSD2, including 3-D Secure flows for recurring payments and re-authentication.
- Security and compliancePCI DSS scope and evidence, ISO 27001 or SOC 2 certifications, and UK GDPR retention, breach notification and data-location terms.
- Commercial termsthree-year total, platform fees, payment processing, per-order fees, minimum monthly charges, overage rates, implementation, migration, internal hours and exit fees.
- Reporting and reconciliationMRR, churn, failed payments, tax and reconciliation reports; sample CSV and API exports, and billing-history retention.
- Exit and portabilityexport rights for subscriber and billing history, data formats, deletion timelines, and contracted response times by severity.
Integration and data mapping
Note your ecommerce platform, warehouse, CRM and finance system. Decide which system holds the customer record, and what happens to it at cancellation.
Support and exit terms
Ask for contracted response times by severity, not sales promises. Check export rights for subscriber and billing history, the data formats offered (CSV, API), deletion timelines, and what happens to integrations at termination. Read these terms before signature.
Cost the whole thing over three years
Ask every vendor for a three-year total, not a monthly headline. Include platform fees, payment processing, tax tools, implementation, migration and your own staff time. For example, a team paying £400 a month in platform fees, with card costs at 1.5% of revenue, should still add migration and internal hours. Those figures are illustrative, not quotes.
Watch for per-order fees, minimum monthly charges and overage rates. Ask for the rate card and a worked example at your forecast volume, because those clauses decide your margin at scale.
Check data protection and product safety before you sign
Subscriber data needs a lawful basis before you collect it. The ICO guidance on lawful basis explains the six options, including consent and contract. Under UK GDPR, agree retention periods for billing and subscriber data, breach notification terms, and where data is stored. Ask vendors for their PCI DSS scope and compliance evidence, security certifications such as ISO 27001 or SOC 2, and what happens to data at cancellation.
If you ship physical goods, safety evidence belongs in the procurement pack. The product safety research collection on GOV.UK gathers government research on product safety, useful when you judge what a fulfilment partner must demonstrate.
Score the shortlist and pilot the two leaders
Score each vendor against the written requirements, and mark anything unanswered as a risk. Before you send a questionnaire, the vendor due diligence process sets out what to verify about ownership, security and financial standing.
Then run a paid pilot for 30 days with two vendors. Test a failed payment, a plan change and a cancellation. Compare the reports each produces, because reporting gaps surface late.
Agree who owns the platform after launch
Selection ends with an owner. Name the person accountable for renewals, incidents and vendor meetings, and put it in their role description. Platforms without an owner drift.
Common questions
How long should subscription commerce software selection take?
For a mid-sized operator, six to ten weeks is realistic. Allow two weeks for requirements and three for shortlisting.
Do we need a formal request for proposal?
Only if your procurement rules demand one. A questionnaire plus a paid pilot often answers more than a long tender.
Can we run two platforms at once?
Rarely for long. Dual running doubles reconciliation work, so treat it as a bridge with a fixed end date.
What most often derails a platform project?
Unmapped data flows and an unpriced exit. Both surface after signature, when your options have narrowed.
