Skip to main content
GullySystem
E-commerce software · Configured implementation

Digital Downloads E-commerce & Secure Delivery Software

Here is a shop for downloadable products, with licence terms, expiring links and a personal library for each buyer. It suits creators, studios and libraries selling files, not parcels. Each seller’s shop is assembled separately, and the delivery layer is arranged around that seller’s own files and licences.

Product status

Configured implementation on a commerce platform chosen in discovery

Discovery selects the commerce platform for the shop, and a secure delivery and licence layer is added for your products. No existing GullySystem product sells downloads, so none is named.

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 download sale has no stock and no courier, so the whole risk sits in the file link and the licence. The system should know who bought which file, under which terms, and who may fetch it again.

It covers the catalogue, licences, delivery, libraries and refunds. It does not make the files, judge copyright or stop a determined buyer from sharing what they have downloaded.

  • Content managers
  • Creators and contributors
  • Support staff
  • Finance
  • Buyers with a library
Modules

What is in the system.

Storefront

A shop for single files, bundles and packs with previews, licence choice and clear file details.

File and version store

Holds each file in its formats and versions, apart from the public preview.

Secure delivery

Issues expiring links with a download limit, tied to the buyer’s order.

Buyer library

A signed-in page listing every purchase, its licence and the latest version of each file.

Licence records

Keeps the licence type, wording and date the buyer saw, for each order.

Refund and access control

Withdraws access when a refund is made or a licence ends.

Workflows

How the work runs through it.

Purchase to download

The buyer picks a file and a licence, pays, and receives an expiring link and a library entry in one step.

New version released

A creator posts a corrected or improved file. Buyers entitled to it are notified and fetch it from their library.

Refund and withdrawal

Support issues a refund. The order’s links stop working and the licence record is marked as withdrawn.

Catalogue and product data

What each product record holds.

Files, formats and previews

Each product lists its formats and sizes and carries a preview that does not reveal the full file.

Licence options

Personal, commercial and team licences are options with their own wording and price.

Bundles

Products are grouped into bundles priced below the sum of their parts, with rules you set.

Pricing and order rules

How prices and orders are set.

Licence-based prices

The price follows the licence chosen, and the licence wording is stored with the order.

Coupons and bundles

Offers are applied by rule and recorded, so a discount can be explained afterwards.

Pre-orders

A forthcoming file is sold ahead of release and delivered on the day.

Stock and fulfilment

From stock to the doorstep.

Link rules

Links expire after a set time and a set number of downloads, and support can reset either by support.

Large files

Large files are served from storage suited to them, with resumable transfers.

Per-copy marking

Where the file type allows it, the buyer’s details are placed inside the copy before delivery.

Payments, returns and refunds

Taking money and giving it back.

Payment

Payment is collected through the gateway your company holds, and orders are marked paid only on confirmation.

Refunds

A refund withdraws the licence and the links, and the reason is recorded.

Disputed payments

Where a card payment is disputed, the order record, licence and download log are available as evidence.

Admin controls and reporting

What the team can see and change.

Roles

Content managers, support and finance each see the screens that suit their job.

Download log

Each download is logged with the time, order and address, so misuse can be examined.

Reports

Sales by product and licence, downloads per order and refunds by reason.

Integrations

What it connects to, and on what terms.

Payment gateway

Linked once the gateway’s test mode has been used end to end with your account.

File storage and delivery

Storage able to serve large files, with its costs and limits understood first.

Accounting package

Invoices and refunds pass to your accountant as exports.

Email service

Receipts, links and update notices are sent with delivery records kept.

Deployment

How it is set up and run.

Platform selected in discovery

The platform is picked against your volume, file sizes and team, and the proposal names it.

Hosting

Hosting is arranged with you, and large-file storage is priced separately because it grows with the catalogue.

Customisation boundaries

What can change, and where the edge is.

Rules you control

Licence wording, link limits, coupon rules and bundle prices are changed by your own staff.

Where the edge is

The software cannot stop a buyer from passing on a file. It limits links, marks copies where possible and records downloads.

Migration and training

Moving over and getting people ready.

Moving a catalogue

Files, titles and past orders are read from your present shop or folders and counted against your own list.

Training

Content managers and support staff practise uploading, releasing a new version and handling a refund.

Support scope

What support covers.

After go-live

A written support note names the contacts and how fixes reach the live shop.

New work

A subscription library, a contributor marketplace or a mobile app is scoped as separate work.

Subcategory coverage

Where each digital downloads subcategory is covered.

Each subcategory is either covered by this solution or has a page of its own where its software requirements differ.

  • E-books

    Covered on this page

    Formats, ISBN records and per-copy marking are catalogue and delivery settings that the category solution already provides.

  • Design Templates

    Covered on this page

    Software-version compatibility and licence wording are listing details that the category catalogue and licence fields already hold.

  • Stock Photos

    Its own solution page

    Contributors, review, release records, licence certificates and royalty statements make this a library system, unlike a shop selling one creator’s files.

  • Graphics

    Covered on this page

    Pack and single-asset licensing, format listings and download credits are options in the category catalogue and pricing, not a separate system.

  • Audio Assets

    Covered on this page

    Preview streaming, use-based licences and certificates are listing and licence settings that the category solution holds for every digital file.

  • Printable Products

    Covered on this page

    Paper-size variants, personalisation fields and low-price high-volume orders suit the category catalogue and delivery without a separate flow.

Existing products

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 digital downloads e-commerce.

Common questions

Questions about this solution.

Is this a product we already sell?

No. Each seller gets a shop assembled for them, with the delivery layer arranged around their own files.

Do you publish a price or a demo?

Nothing is published about price, trials or demonstrations. A written proposal sets the cost after discovery.

Can it stop a buyer sharing the file?

Not on its own. It limits links, can mark copies and keeps a download log. A buyer who passes on a file cannot be prevented by software.

Can we sell the same files by subscription?

Yes, if you want it. A subscription library needs its own plan and entitlement rules, which are scoped alongside the shop.

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

Only your name, contact details and a short description are required.

Your details stay private. Privacy policyProtected by reCAPTCHA.