E-commerce software · Custom software solution

Stock Photo E-commerce & Licensing Software

This solution runs a stock photo library: contributors upload, reviewers approve, buyers search and licence images by size and use, and contributors see what they earned. It records the licence granted for every download, and it is written around each library’s own licence tiers.

Discuss your requirement The business view

Product status

Custom software solution, built to your requirements

A contributor library, search, licence certificates and royalty statements go well beyond a shop that sells files. The system is written for your library and your licence tiers, with payment taken by your gateway.

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 stock library sells a right to use a picture, and a buyer later needs proof of that right. Each download therefore creates a licence record naming the image, the tier, the buyer and the date.

The solution covers contributors, review, search, licensing, downloads and royalties. It does not judge copyright, decide whether a release is valid in law or remove disputed images without your staff.

Contributors
Image reviewers
Buyers and design teams
Licensing and support staff
Finance team

Modules

What is in the system.

Contributor portal

Photographers upload images, add titles and keywords, attach releases and follow each image’s review status.

Review queue

Reviewers approve, reject or ask for changes, with a reason that returns to the contributor.

Search and browse

Buyers search by keyword, colour, orientation and people or no people, and save collections.

Licence tiers and certificates

Each download is issued under a tier, and a licence document names the image, the use and the buyer.

Royalty statements

Sales are totalled by contributor and image each period, with the rate shown.

Workflows

How the work runs through it.

Upload to listing

A contributor uploads a photo, adds keywords and a release if people appear, and a reviewer approves it for sale.

Search to download

A buyer searches, previews a watermarked image, chooses a size and licence, pays and downloads the clean file.

Takedown request

A complaint about an image is logged, the image is hidden while your staff review it, and the outcome is recorded.

Catalogue and product data

What each product record holds.

Images and keywords

Each image carries a title, keywords, categories, orientation and dominant colours, so search can use them.

Release records

Model and property releases are attached to the image and visible to reviewers, not to buyers.

Previews and sizes

A watermarked preview is public. Clean files are held at several sizes and served only after licensing.

Pricing and order rules

How prices and orders are set.

Licence tiers

Web, print and extended tiers carry their own prices and permitted uses.

Credit packs

A buyer can purchase credits and spend them on downloads, with the balance shown.

Team licences

A firm buys one licence for a named team and sees the team’s downloads together.

Stock and fulfilment

From stock to the doorstep.

Secure file delivery

Clean files are served through links that expire, and re-downloads are limited to the licensed buyer.

Download history

Each licensed image is listed in the buyer’s account with its certificate.

Large library storage

Storage and delivery are sized for tens of thousands of images, and sized again as the library grows.

Payments, returns and refunds

Taking money and giving it back.

Payments and credits

Single purchases and credit packs are paid through your gateway and recorded against the buyer.

Refunds

A refund withdraws the licence and the buyer’s access to that file, and the reason is recorded.

Contributor payouts

Statements show what is owed. Paying contributors is done by your finance team through your bank.

Admin controls and reporting

What the team can see and change.

Review and takedown log

Each decision on an image is kept with the reviewer and the reason.

Sales by image

Which images sell, at which tier and to which kind of buyer.

Contributor earnings

Totals by contributor and period, with the rate applied.

Integrations

What it connects to, and on what terms.

Payment gateway

Single and credit purchases are taken through the gateway you use, after its test mode has been exercised.

Image delivery network

Previews and files are served from storage suited to large images, once its pricing and limits are understood.

Accounting software

Sales totals and contributor payables are exported for your accountant.

Deployment

How it is set up and run.

Written for your library

The system is developed around your tiers and review rules, and the proposal states who owns the code.

Cloud hosting

Hosting is planned with you early, because image storage and delivery drive most of the running cost.

Customisation boundaries

What can change, and where the edge is.

Rules as settings

Tiers, review criteria, watermark style and royalty rates are changed from the admin area.

Where the edge is

Judging copyright, releases and takedown disputes stays with your staff and your legal adviser. The software records their decisions.

Migration and training

Moving over and getting people ready.

Bringing a library in

Existing images, keywords and contributor details are read from your archive and sampled before bulk import.

Training

Reviewers and licensing staff practise on real uploads, takedowns and licence queries.

Support scope

What support covers.

After launch

A support note names the contacts, the response hours and how fixes are released.

New work

New tiers, new contributor types or video are scoped as separate pieces of work.

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 stock photos e-commerce.

Common questions

Questions about this solution.

Is it a ready-made photo marketplace?

No. It is software written for your library. The proposal explains what is new and what is reused from our earlier work.

Does the software detect stolen images?

No. It records releases, reviews and takedown requests. Detecting copied work needs a separate service and human review.

Can contributors be paid automatically?

The system works out what each is owed. Transfers are made by your finance team, or through a payout provider once its terms and your registration are checked.

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