E-commerce software · Custom software solution

Software Subscription E-commerce & Billing Software

This solution runs the commercial side of a subscription product: plans, seats, add-ons, renewals, invoices and what each account is entitled to use. Your product asks it what a customer may do, and it answers from the plan. It is written separately for each product.

Discuss your requirement The business view

Product status

Custom software solution, built to your requirements

The plan, entitlement and renewal logic is written around your own product, because plans and limits differ from one product to the next. A payment provider’s recurring billing is used where it fits, confirmed in discovery.

There is no published price, free trial or live demo for this solution. Scope and cost are settled in a written proposal after discovery.

Purpose and users

A subscription is a promise that changes every month: a seat added, a plan upgraded, a card that fails. The product must always know what the customer may use, and billing must match.

The solution holds plans, entitlements, invoices and renewals. It does not host your application, measure its usage unless your product reports it, or write your product’s feature switches.

Product and pricing owners
Billing and finance team
Customer success
Account administrators
Your engineers

Modules

What is in the system.

Plan and add-on catalogue

Plans, seat prices, usage limits and add-ons are defined once and priced by billing period.

Entitlement service

Your product asks what an account may use and receives the answer from the plan it is on.

Subscription lifecycle

Starts, upgrades, downgrades, pauses and cancellations are recorded with their effective dates.

Invoicing and collection

Recurring invoices, proration, failed-payment retries and receipts are raised from the subscription.

Account portal

An administrator changes plan, adds seats, updates payment details and downloads invoices.

Workflows

How the work runs through it.

Sign-up to active

A buyer chooses a plan and seats and pays. The account is created, the entitlements are set and the product is told.

Mid-term change

A seat is added or a plan upgraded. The charge is prorated, the invoice is raised and the entitlement changes from that date.

Failed payment to recovery

A charge fails, retries follow a schedule, and the account moves to a grace state before access is restricted.

Catalogue and product data

What each product record holds.

Plans, seats and add-ons

Each plan lists what it includes, and seat prices and add-ons are separate lines.

Usage limits

Limits such as projects, storage or messages are set on the plan and compared with the usage your product reports.

Billing periods

Monthly and yearly prices are held side by side, with the discount for annual terms set by you.

Pricing and order rules

How prices and orders are set.

Proration rules

The way a mid-term change is charged is written down and applied the same way each time.

Coupons and negotiated rates

A customer on a special rate keeps it through renewals until you change it.

Tax and invoice details

Company names and tax identifiers are kept on the account and printed on every invoice.

Stock and fulfilment

From stock to the doorstep.

Entitlements, not stock

What an account may use is stored as a set of limits and switches, changed whenever the plan changes.

Grace and restriction

A lapsed account moves through states you define, such as warning, read-only and suspended.

Notifying the product

The product is told of every change through a signed message, with a retry if it does not reply.

Payments, returns and refunds

Taking money and giving it back.

Recurring payment

Card and mandate-based payment are used where the provider and the buyer’s bank support them.

Refunds and credits

A refund or credit note is raised against a named invoice, and the reason is recorded.

Cancellation

A cancellation takes effect at the end of the paid term or at once, as your terms state.

Admin controls and reporting

What the team can see and change.

Revenue by plan

Active subscriptions, seats and billed amounts by plan and period.

Churn and failed payments

Cancellations by reason and failed payments by stage of recovery.

Audit log

Every plan or entitlement change, with the person or system that made it.

Integrations

What it connects to, and on what terms.

Your product

A documented interface for asking what an account may use and for receiving change messages.

Payment provider

Recurring billing and mandates, after the provider’s documentation, limits and your registration have been checked.

Accounting software

Each invoice and credit note is exported to the accounts package for your accountant.

Deployment

How it is set up and run.

Built to order

The service is written against your plans and your product’s needs, and the proposal states who owns the code and the data.

Hosted

The service can run on servers we look after, or inside the cloud subscription your company already holds.

Customisation boundaries

What can change, and where the edge is.

Plans change often

Plans, limits and prices are data, so changing them does not need a release.

Where the edge is

Feature switches inside your product, and any measuring of usage, are done by your engineers against the interface we supply.

Migration and training

Moving over and getting people ready.

Moving current subscribers

Active customers, plans, seats and renewal dates are read from your present billing tool and reconciled before the first cycle runs.

Training

Finance, customer success and your engineers each get a session on the part they will use.

Support scope

What support covers.

Scope

Fixes and minor changes go through a named contact, under terms set out before go-live.

Outside scope

A new billing model, such as usage-priced invoicing, is scoped and priced when you ask for it.

What already exists.

No existing GullySystem product covers this requirement on its own. It would be built, as described above.

Services

How it gets built.

For the business side, see Software solutions for software subscriptions e-commerce.

Common questions

Questions about this solution.

Do you provide the payment processing?

No. Payment is taken by a provider with whom you have an account. This service decides what is billed and what each account may use.

Can it enforce limits inside our product?

Not on its own. It tells the product what the account is entitled to. Enforcement is done by your code.

Is there a template we can start from?

There is no ready product for this. The system is written for your product, and the proposal says which parts come from earlier work.

Requirement discussion

Talk through your commerce requirement.

Describe what you sell, where you sell it and what is slowing you down. An engineer will reply within one business day.

No obligation
A reply within one business day
Your details stay private