Features
Six systems that make a subscription programme work
Selling a subscription is the easy part. Keeping it alive through the second, sixth and twelfth billing cycle is where the revenue is, and it is what each of these is built for.
Feature areas on this page
Feature 01
Subscription plans & schedules
Sell anything in your catalogue on a schedule
Build plans on top of the products you already sell. Set delivery frequencies, minimum commitments, prepaid terms and subscriber discounts, then apply a plan to a single variant or a whole collection at once.
- Weekly, monthly and custom interval schedules
- Percentage or fixed subscriber discounts
- Prepaid terms and minimum cycle commitments
- Apply a plan per variant or across a collection
Why it matters
The shape of a plan decides how long a customer stays, so changing it should take minutes rather than a developer ticket.
Feature 02
Checkout widget & embedded UI
A storefront selector that looks like your theme
Add a one-time or subscribe selector to product pages as a theme app block. It picks up your theme fonts, colours and radius, shows the subscriber price against the one-time price, and hands the cart to native Shopify checkout.
- Theme app block, no theme code to edit
- Frequency selector with live price comparison
- Inherits theme typography, colour and corner radius
- Keyboard and screen reader accessible by default
Why it matters
The subscribe option is where the decision is actually made, so it has to look native and render without shifting the page.
Feature 03
Customer portal
Let subscribers manage their own deliveries
Subscribers sign in to skip a delivery, change frequency, swap a product, update a card or pause. You decide which of those actions are available, and every change is written to the subscription history.
- Skip, pause, reschedule and swap products
- Self-serve payment method and address updates
- Per-action permissions you control
- Pause and delay offered before a cancellation completes
Why it matters
Most cancellations begin as a request to pause or delay, so handing that control to the customer is what keeps the subscription alive.
Feature 04
Automated billing & retries
Recurring charges that recover themselves
subi queues every billing cycle, charges the saved payment method, and handles what happens when it fails: staged retries, a dunning sequence with a recovery link, and card expiry notices sent before the charge is even attempted.
- Scheduled charges with a visible upcoming queue
- Staged retry windows after a decline
- Dunning emails carrying a one-click recovery link
- Card expiry notices ahead of the next cycle
Why it matters
Failed payments, not cancellations, are where most subscription revenue quietly disappears.
Feature 05
Order management
Recurring orders inside your normal fulfilment flow
Every renewal creates a standard Shopify order, tagged as a subscription and linked back to its contract. Edit an upcoming order, change quantities, add a one-off discount or move the date without disturbing the rest of the cycle.
- Renewals create native Shopify orders
- Subscription tags that Flow and fulfilment rules can read
- Edit or reschedule the next order without changing the plan
- Full contract and change history on every subscriber
Why it matters
Your warehouse or 3PL should never need a second system to pick a recurring order.
Feature 06
Reporting & analytics
See what recurring revenue is actually doing
Track recurring revenue, active subscribers, average subscription length, churn and payment recovery across any date range, then break each number down by plan and by product to find the schedule that holds customers longest.
- Recurring revenue, active subscribers and churn over time
- Cohort retention by plan and by product
- Failed payment and recovery reporting
- CSV export for your own reporting stack
Why it matters
Subscription decisions are only ever as good as the retention data sitting behind them.
See these six working on your own catalogue
A demo runs against your products, not a sandbox store. We build a plan, publish the widget to a preview theme, and run a test billing cycle so you can see the retry logic actually fire.
