Development Agency
Contact Sign in Get a project quote

Service

Digital products store development

For creators, software vendors and template sellers who need a store designed around licences, file versions, download rules and buyer-location tax, rather than a physical-goods shop with shipping switched off.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A small software vendor or a designer selling templates usually starts with a payment link and a file attached to an email.

  • It works for the first hundred sales.
  • Then a customer asks for the file again six months later and support has to find the original order; another forwards the download link to a forum and the file circulates freely; a third bought a single-site licence and is running it on twelve sites, and nobody can tell.
  • A new version of the product ships and every past buyer has to be emailed by hand, with a fresh link, from a mailing list that was never quite in step with the order list.

Where it gets harder

Pricing is the next problem.

  • The vendor wants a personal tier, a studio tier and an extended licence, with upgrades between them, and the checkout tool only knows one price.
  • Sales to buyers in other countries need tax handled according to where the buyer is, and the spreadsheet for that is the part of the month everyone dreads.
  • Refund requests arrive for files already downloaded.
  • Preview samples live on a separate page that is often out of date.
  • The vendor spends more time administering files, licences and tax than making the next product.

Scope of the service

What the build covers

A custom digital products store build normally covers the catalogue, licensing, delivery and update core. The catalogue carries products with files, preview samples, version history and release notes, grouped into bundles where needed, with pricing models you choose per product: fixed, tiered by licence type, pay-what-you-want with a minimum, or upgrade pricing between tiers. Checkout runs through the payment adapter with configurable tax rules keyed to the buyer's location and evidence of it, discount codes and customer accounts. Delivery issues secure download links with expiry and download limits you set, generates licence keys per purchase in your own format or through your licensing library, and records every download against the order. Versioned files let you publish an update once; buyers on a current licence are notified and can re-download from their account, with a licence validation endpoint for software that checks in. Refund rules can depend on whether the file was downloaded. Where several creators sell through one store, creator accounts carry their own products, commission and payout statements.

We map your products first: what the files are and how large, how licences are expressed and enforced, how versions are released, which tiers and upgrades you sell, how tax by buyer location should be evidenced and recorded, and whether other creators sell alongside you. Each becomes a named stage in the scope document.

Deliberately out of scope

  • Deciding which tax regime applies to which buyer, which remains with you and your adviser and is expressed as rules you configure
  • Building the product you sell
  • Copy protection inside the files themselves

When the scope grows

Scoping scenario

A plugin vendor sells annual licences for one, five and unlimited sites, needs the plugin to validate its key against the store on activation, wants renewals billed automatically with a grace period, and must let a customer upgrade from one tier to another part way through the year paying only the difference. The validation endpoint, automatic renewals and prorated upgrades make this a custom build, and the scope document says so plainly.

Deliverables

What you receive

  • Discovery notes from walking through a purchase, a licence check, a version release and a tax report
  • A written scope document naming each workflow stage, the licence and pricing model, the tax rule approach and what is left out
  • Designs of the product page with previews, the checkout, the customer library and the release and licence screens
  • The build, deployed to your hosting or ours, with the payment provider and file storage connected
  • Migration of products, files, customers, orders and existing licence keys from your current tools
  • Training for the store owner and support staff, with a short written guide
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access to your current checkout tool, file storage, licence records and mailing list; the licence terms and tiers you sell today.

    Project stage: Onboarding

  2. Planning

    Discovery with the owner and whoever handles support; the licence model, delivery rules, version flow, tax rule approach and any creator accounts are written into the scope document.

    Project stage: Planning

  3. Design

    Product pages with previews and tiers designed for buyers; the customer library, release publishing and licence management screens designed for you and your support team.

    Project stage: Design

  4. Development

    Built in layers: catalogue and files first, then checkout and tax rules, then licences and delivery, then versions, notifications and any creator accounts.

    Project stage: Development

  5. Client review

    You and a few friendly customers buy, download, validate licences and receive an update release with the payment provider in test mode, and tell us where the flow breaks.

    Project stage: Client review

  6. Revisions

    Changes from the review are made and re-checked against the scope document.

    Project stage: Revisions

  7. Ready for launch

    Products, customers and licence keys migrated, payments and tax records verified against live accounts you control, download links tested from outside, launch checklist signed off.

    Project stage: Ready for launch

  8. Delivered

    Sales and downloads run through the store; hosting and maintenance continue under their own agreement if taken.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Card and wallet payment providers through the provider-independent payment layer
  • Object storage and content delivery networks for large files and fast downloads
  • Licensing libraries and software activation flows in your product
  • Email providers for receipts, licence delivery and update notifications
  • Accounting software for sales, refunds and tax reporting exports
  • Mailing list platforms for buyer segments by product and version
  • Code and asset repositories where releases are built

How we would approach it

Worked example

Concept demo

A plugin vendor with site-limited licences and automatic renewals

The situation

A plugin vendor sells annual licences for one, five and unlimited sites, needs the plugin to check its key against the store on activation and periodically afterwards, wants renewals billed automatically with a grace period before the licence stops validating, and must let a customer move up a tier mid-year paying only the difference.

Why it is a custom build

The custom route is needed because of the validation endpoint, automatic renewals and prorated upgrades, which go beyond the one-off purchase with a key and re-download model the package assumes.

The scope we would propose

  • Licence records with site allowances and activation counts
  • A validation endpoint the plugin calls with the key and site address, renewal billing through the payment adapter with retry and a configurable grace period, prorated upgrade pricing calculated from the remaining term
  • A customer library showing sites activated, renewal date and the current version to download

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of products and the size and type of files to deliver
  • Licence model: per purchase, per site, per seat, annual or perpetual
  • Whether your software validates keys against the store
  • Pricing models: tiers, upgrades, pay-what-you-want or bundles
  • Tax rule complexity by buyer location and the evidence recorded
  • Version release flow and update notifications
  • Creator accounts with commission and payouts
  • Hosting choice: your own hosting or ours

Start from a package

Digital downloads package

Secure downloads with expiry and limits, licence keys per purchase, versioned files with update notifications, previews, tiered or pay-what-you-want pricing and buyer-location tax rules for sellers of digital goods.

Custom build
View the package

FAQ

Frequently asked questions

When is the package enough and when do we need a custom build?

If one-off purchases with secure downloads, licence keys, versioned re-downloads, tiered or pay-what-you-want pricing and configurable buyer-location tax rules cover your store, the digital downloads package is the right fit and we quote for that. Key validation from inside your software, automatic renewals, prorated upgrades or creator accounts with payouts point to the custom route.

How is tax by buyer location handled?

Through rules you configure per product type and buyer location, with the location evidence you choose to collect recorded against each order and exported for your reports. The store applies the rules; which regime applies to which sale remains a matter for you and your adviser.

Can we stop download links being shared?

Links are signed, expire after a period you set and allow a number of downloads you set, and every download is logged against the order and the account. A buyer who needs the file again fetches it from their library after logging in rather than from an old link.

Can you move our existing customers and licence keys?

Yes. Customers, orders, files and existing keys are imported so past buyers can log in, see their purchases and download current versions, and existing keys continue to work. The scope document states what can be carried over once we have seen the data.

Who owns the store afterwards?

You do. The source code, products, files, customers and licence records are handed over at delivery. Hosting and maintenance are optional and agreed separately.

Get a project quote for digital products software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences