Skip to main content
GullySystem
E-commerce · Software

Software Solutions for Software Publishers and Resellers

Selling software online means delivering a right to use it, not a parcel. A buyer needs a key, an account or a download, and the seller must remember which edition, how many seats and what term were sold. This page covers publishers, resellers and marketplaces, and the records they need.

At a glance

Sell licences, keys and renewals online with every entitlement on record.

A software order ends in a licence, not a delivery. The buyer receives a key, a login or a link, and the seller must know which edition, how many seats and what term were sold.

Sellers range from publishers with their own licence server to resellers who buy key blocks from a vendor. The store has to fit whichever arrangement sits behind it.

Businesses and operating models

Publishers selling direct

A company sells its own product from its website. It controls the licence server, the pricing and the renewal terms.

Resellers and distributors

A seller buys keys or accounts from several vendors and resells them, often to firms that want one invoice for many products.

Marketplaces for add-ons

Several developers list products on one storefront. The marketplace takes the order, passes on the licence and settles with each developer.

Software sold with services

A product is sold with installation, training or a yearly support contract, so one order carries a licence and a service.

How an order moves

The workflow for software.

  1. 1

    Listing an edition

    Each product is listed by edition, platform and licence type. Perpetual, term and per-seat licences are separate options, not lines in a description.

  2. 2

    Choosing seats and term

    The buyer picks seats, years and add-ons, and watches the price change. A business buyer can ask for a quote.

  3. 3

    Paying and invoicing

    The order is paid and a tax invoice is raised in the company’s name where one is given.

  4. 4

    Issuing the licence

    A key is drawn from a pool, produced by the publisher’s service or created as an account. It is saved against the order.

  5. 5

    Download and activation

    The buyer signs in to an area holding installers, release notes and the key. Activations used and left are visible to the buyer and to support.

  6. 6

    Renewal, upgrade and refund

    A reminder goes out before the term ends. An upgrade is priced against the earlier licence, and a refund revokes the key where the publisher allows it.

Where it breaks

The challenges, and what they cost.

Keys sit in emails and sheets

Keys are pasted into messages by hand. A buyer who loses one writes to support, and no one can say which keys remain unsold.

Seats sold differ from seats used

An order for five seats becomes one key shared by twenty people. The publisher learns of it when support tickets arrive.

Refunds follow activation

A customer wants money back after the key has been used. With no record of activations, the decision is a guess.

Renewals lapse unnoticed

Terms end on dates held in a sheet. The customer loses access, or keeps it without paying, until someone looks.

Editions confuse buyers

A buyer picks the wrong edition, or an operating system the product does not support. A refund request follows.

Requirements to assess

What is specific to this trade.

These are requirements we would confirm in discovery. They describe what the solution may need to handle. They are not features that already exist.

  • The licence models in use: perpetual, term, per-seat, per-device or usage based
  • Where keys come from: a pool you hold, a vendor’s reseller service or your own licence server
  • Whether the publisher’s terms allow revocation and refunds after activation
  • Operating system, version and edition rules that each listing must state
  • Who may buy: individuals, firms, resellers or only approved partners
Recommended modules

What we would build for software.

Chosen from the commerce capabilities this business needs, not a list of everything.

Edition and licence catalogue

List each edition with platform, licence type, seat count and term, so price and delivery follow from the choice.

Licence issuance

Draw keys from a pool or request them from the publisher’s service, and save each against its order.

Customer download area

Give each buyer a signed-in page with installers, keys, invoices and activation counts.

Order and invoice management

Handle orders, tax invoices, company details and quotes in one record.

Renewals and upgrades

Track term end dates, send reminders and price an upgrade against the licence already held.

Refund and revocation

Record the decision, revoke or deactivate the key where the publisher’s system allows, and refund against the order.

Users and permissions

Who works in the system, and what each can do.

Catalogue manager

Lists editions and keeps platform notes and prices current. Cannot issue keys.

Licence desk

Resends keys, frees activations and handles revoked licences.

Finance and accounts

Reviews invoices and refunds and matches receipts to orders.

Reseller or partner

Orders at agreed rates for named customers and sees only its own orders.

Customer administrator

Downloads installers and invoices and sees seats bought and in use.

Integrations

What it would connect to.

An integration is confirmed only after its API, access and scope are checked. A connection that updates on a schedule is described as scheduled, not real-time.

  • A payment gateway that takes UPI, cards and net banking
  • A publisher’s or vendor’s licence or reseller interface, once its documentation is read and access tested
  • Your accounts package, fed with invoices and receipts
  • Email and, for firms with a registered business number, WhatsApp, for delivery and renewal notices
  • The customer login or single sign-on service your product already uses
Implementation

How the work runs, and what we need from you.

What you provide

  • Your product list with editions, platforms and licence types
  • The source of your keys and how many you hold or can request
  • Your renewal, upgrade and refund terms as written today

Map the entitlement

We begin with what a buyer is allowed to do after paying, and design the record around it.

Set up one product end to end

A single product goes from listing to key to renewal first, so the delivery path is proven.

Add renewals once delivery holds

Reminders and upgrade prices follow when keys are reaching buyers and the records agree with your own.

Deliverables

What you receive.

  • A catalogue structure for editions, seats and terms
  • A key issuance and delivery flow for the sources you use
  • A customer area for downloads, keys and invoices
  • Renewal and refund rules written down
  • A training session for your licence desk
Measurement

How progress is judged.

Measures are agreed against your own baseline. We do not promise a result in advance.

  • Orders that needed a key sent by hand
  • Licences whose end date is known and reminded
  • Refund requests settled from the activation record
India and international

Selling at home and abroad.

Currencies and display

Prices can be shown in several currencies, which is a display setting. Collecting and settling money in them is a matter for the payment provider and the bank.

Tax on digital supply

How tax applies to a licence sold across borders differs by country. The store applies the rules your adviser specifies, checked for each market.

Sales restrictions

A publisher may limit sales by country or by buyer type. The store holds the allowed list you give it and declines other orders.

Language and support hours

Installers, invoices and support replies may need the buyer’s language and time zone. Which languages are offered is agreed with you.

Suitable software

Software E-commerce & Licence Delivery Software

Configured implementation

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.

Read about the software
Common questions

Questions about software e-commerce.

Do you build the licence check that runs inside our product?

Not on its own. The store can issue and record keys. Enforcing them inside your application is product engineering work, scoped separately.

Can we resell another vendor’s software?

Where the vendor’s reseller terms and API allow it. We check what the vendor lets a reseller store, show and deliver before any listing goes live.

Can customers pay in other currencies?

Prices can be displayed in several currencies. Collecting money in those currencies is settled first with the payment provider, the bank and your registration.

Can a buyer download after the term ends?

That is a rule you set. Some sellers keep installers open and lock the key, and others close both.

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.