E-commerce software · Custom software solution

Bicycle Parts E-commerce & Compatibility Software

A compatibility database links each part to the standards it needs: wheel size, axle, bottom bracket, brake type and drivetrain. Riders enter a bicycle or a standard and see parts that fit. It is written for sellers whose customers keep asking whether a part will work.

Discuss your requirement The business view

Product status

Custom software solution, built to your requirements

No current GullySystem product holds cycle component compatibility. The automotive parts product models vehicle fitment differently and is not extended here, so this part is new work.

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

Most returns of cycle parts come from a standard that did not match. This system holds the standards on each part and on each bicycle, so that a lookup can do the matching instead of a member of staff relying on memory.

It does not install parts or check that a combination is safe. It applies the compatibility entries your team records. It flags where none exist.

Parts catalogue editors
Online order desk
Workshop buyers
Riders
Owners

Modules

What is in the system.

Standards register

Wheel size, axle, bottom bracket, brake, headset and drivetrain standards.

Compatibility mapping

Parts linked to the standards they need and the bicycles they suit.

Bicycle lookup

A rider enters a model or standards and sees fitting parts.

Cross-references

Brand and part-number equivalents.

Workshop pricing

Trade prices and minimums for bicycle shops.

Workflows

How the work runs through it.

Lookup to order

A rider enters a bicycle, sees compatible parts and orders. The basket flags parts that need others.

Workshop reorder

A workshop repeats a list of parts at trade prices.

Catalogue and product data

What each product record holds.

Standards

Every part holds the standards it needs.

Part numbers

Brand part numbers and cross-references.

Dependencies

Parts that need other parts, such as a cassette and a chain.

Pricing and order rules

How prices and orders are set.

Retail price

Priced by part and brand.

Trade price

A workshop’s agreed price, visible only to that workshop.

Basket checks

Warns when a part has an unmet dependency.

Stock and fulfilment

From stock to the doorstep.

Stock by part

Counts by part number, with minimums.

Supplier orders

Reorders raised from low stock.

Unknown fits

A queue of lookups with no compatibility entry.

Payments, returns and refunds

Taking money and giving it back.

Payments

Online payment through a provider, and account billing for workshops.

Returns

Parts return against the order, with a reason, such as wrong fit or fault.

Admin controls and reporting

What the team can see and change.

Fitment gaps

Parts and bicycles with no mapping.

Returns by reason

Wrong-fit returns by part.

Integrations

What it connects to, and on what terms.

Supplier files

Catalogues from suppliers loaded after the file format is reviewed.

Courier

Small-parcel bookings through the carrier’s own system, after a trial shipment.

Storefront

A standard store reads parts and fitment from this system.

Deployment

How it is set up and run.

Delivered to order

Developed from your supplier catalogues. Hosting sits with us or with you.

In stages

Standards and fitment first, then trade pricing.

Customisation boundaries

What can change, and where the edge is.

Rules you own

Standards, dependency rules and cross-references are your entries.

Edges

Whether a combination is safe is the mechanic’s call. The software cannot make it.

Migration and training

Moving over and getting people ready.

Loading the catalogue

Parts and standards are loaded from supplier files, then tested against a sample of lookups.

Training

Editors and the desk practise on the unknown-fit queue.

Support scope

What support covers.

Included

Lookup and data-model corrections are covered, with the response hours spelled out in the agreement.

Not included

Further product ranges or new channels are priced separately when needed.

What already exists.

Wholesale and B2B Ordering Software

A price-list ordering portal for dealers and retailers, wired to stock, credit limits and dispatch.

Learn more

Services

How it gets built.

For the business side, see Software solutions for bicycle parts e-commerce.

Common questions

Questions about this solution.

Could a current GullySystem product do the matching?

No. Cycle compatibility is new development. GullySystem’s auto parts product is built around vehicle fitment and is not stretched to cover it.

Is a fit certain once the lookup shows a part?

No. It shows parts whose standards match. The seller’s entries decide what shows, and a mechanic confirms the fit.

Can workshops get trade prices?

Yes. A workshop signs in and sees its own prices and minimums.

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