E-commerce software · Configured implementation

Software E-commerce & Licence Delivery Software

This solution sets up a store for selling software, with editions, licence keys, downloads and renewals held against each order. It suits publishers who sell direct and resellers who sell other vendors’ products. The storefront runs on a commerce platform that discovery selects, with the licence layer arranged around it.

Discuss your requirement The business view

Product status

Configured implementation on a commerce platform chosen in discovery

A commerce platform is picked for the store during discovery, and a licence and download layer is arranged around your products. GullySystem has no product that sells software, 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

One record should say what each buyer may use. A key, a download link and an invoice then trace back to the same order, not to three separate inboxes.

It covers the store, the licence record, the customer area and renewals. It does not write the licence check inside your product, trace pirated copies or support the software itself.

Catalogue managers
Licence desk staff
Finance and accounts
Resellers and partners
Customer administrators

Modules

What is in the system.

Storefront

A consumer store, a business buying page or both, with edition, platform and licence type as the buyer’s choices.

Licence record

Holds the key or account, edition, seats, term and activations against each order and customer.

Key pool and issuance

Loads keys in batches, issues one per seat and shows how many remain for each product.

Customer download area

Signed-in access to installers, release notes, keys and invoices, limited to the versions each licence covers.

Renewals and upgrades

End dates, reminders and upgrade prices worked out against the licence already held.

Orders and invoices

Orders, tax invoices, company details and refunds kept beside the licence they relate to.

Workflows

How the work runs through it.

From order to key

The buyer picks an edition and seats and pays. The system draws the keys, saves them to the order, sends the invoice and opens the download area.

Renewal

A reminder goes out before the term ends. The buyer renews from the customer area, and the end date moves on the same licence record.

Refund after activation

Support sees the activation count and the publisher’s refund rule, records the decision and revokes the key where the source allows.

Catalogue and product data

What each product record holds.

Editions and platforms

Each edition lists the systems and versions it runs on, so a buyer picks a compatible one.

Licence types

Perpetual, term and per-seat licences are separate options with their own seat counts and durations.

Release notes and files

Installers and notes are attached by version, and older versions stay open where your terms allow.

Pricing and order rules

How prices and orders are set.

Seat and term pricing

Prices follow the seats and years chosen, and volume breaks are set as rules.

Quotes for businesses

A firm can request a quote with company and tax details and pay against it later.

Upgrade pricing

An upgrade is priced against the licence already held, using rules you supply.

Stock and fulfilment

From stock to the doorstep.

Key pool counts

The pool shows keys left for each product and warns the licence desk before it runs low.

Where keys come from

Keys come from a batch you load, or are requested from a vendor’s service after we have read its documentation and tested access.

Delivery record

Each key sent is logged with its time, address and order, so a lost key can be resent from the record.

Payments, returns and refunds

Taking money and giving it back.

Payments

UPI, cards and net banking, taken by the gateway your company already uses.

Showing other currencies

Several currencies can be displayed. Whether you can collect in them is for the provider and the bank to say.

Refunds and revocation

A refund is booked against the original order, and the key is revoked or flagged if the publisher’s system accepts that.

Admin controls and reporting

What the team can see and change.

Roles

Catalogue staff, the licence desk and finance each reach only the screens their work needs.

Approvals

A refund after activation, or a large discount, waits for an approver whose decision stays on the order.

Reports

Orders by product and edition, keys remaining, licences ending this quarter and refunds by reason.

Integrations

What it connects to, and on what terms.

Payment gateway

Linked once the gateway’s documentation has been read and a test payment has gone through.

Publisher or vendor licence service

Keys are requested or checked through it after its access, limits and terms are confirmed.

Accounting software

Invoices and receipts pass to the accounts package as exports your accountant can import.

Email and WhatsApp

Delivery and renewal notices go out by email, with WhatsApp added where a registered business number exists.

Deployment

How it is set up and run.

Platform chosen in discovery

The commerce platform is selected against your catalogue, volumes and team, and the proposal names it.

Hosted and managed

Hosting is arranged with you, whether on our servers or in your own cloud space, and the proposal says which.

Customisation boundaries

What can change, and where the edge is.

What can change

Licence types, renewal rules, approval steps, invoice wording and page design follow your business.

Where the edge is

The licence check inside your own product stays with your engineers. The store records and issues licences only.

Migration and training

Moving over and getting people ready.

Existing keys and customers

Customer lists, issued keys and end dates are read from your sheets or billing tool, then compared with your own totals.

Training

Catalogue staff and the licence desk practise on your own products in short sessions.

Support scope

What support covers.

Scope

Fixes and minor changes are covered by a written support note that names who to call.

Outside scope

A new product line, a new licence model or a second storefront needs its own proposal.

Subcategory coverage

Where each software subcategory is covered.

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

Business Software
Its own solution page
Quote-led buying, approvals, purchase orders and partner pricing need their own flow, which a card-checkout store does not provide.
Productivity Software
Covered on this page
Single-seat and small-pack licences, key delivery and renewals are what the category solution already holds.
Security Software
Covered on this page
Device-count keys, activation records and renewal reminders are already in the category licence record, and the extra rules are settings.
Creative Software
Covered on this page
Large installers, hardware limits and educator pricing are listing details and rules inside the category solution’s catalogue and pricing.
Software Subscriptions
Its own solution page
Plans, entitlements, proration and failed-payment recovery are a billing system of their own, unlike one-off licence sales.

Subcategory	Software	Why
Business Software	Its own solution page	Quote-led buying, approvals, purchase orders and partner pricing need their own flow, which a card-checkout store does not provide.
Productivity Software	Covered on this page	Single-seat and small-pack licences, key delivery and renewals are what the category solution already holds.
Security Software	Covered on this page	Device-count keys, activation records and renewal reminders are already in the category licence record, and the extra rules are settings.
Creative Software	Covered on this page	Large installers, hardware limits and educator pricing are listing details and rules inside the category solution’s catalogue and pricing.
Software Subscriptions	Its own solution page	Plans, entitlements, proration and failed-payment recovery are a billing system of their own, unlike one-off licence sales.

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 software e-commerce.

Common questions

Questions about this solution.

Is this a ready-made product?

No. Each seller gets a store assembled on the platform that discovery picks, with the licence layer arranged around their own products.

Is there a published price or a demo?

Neither. No price list, trial or demonstration is published, and the cost arrives in a written proposal after discovery.

Does it stop people sharing one key?

Not on its own. The store records activations if your product reports them. Blocking shared keys needs a check inside the product, which is separate work.

Will it talk to our licence server?

Where the server has an interface we can use. We test its access before promising what can be connected.

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