Skip to main content
GullySystem
E-commerce software · Existing product, extended

Automotive Parts E-commerce & Dealer Ordering Software

This solution puts an online store and a workshop ordering area in front of the parts shop’s own records. The site reads part numbers, fitment, stock and trade prices from that system. Each business gets its own storefront set-up. The shop side is in place already.

Product status

Existing GullySystem product, with the online storefront configured around it

At the counter, GullySystem’s Auto Parts Shop Management Software already holds part numbers, vehicle fitment, rack stock, garage credit and bills. The storefront and trade ordering are configured around it.

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

The site and the counter read one part record. A sale in either place then moves the same stock, and a garage’s balance is the same on both.

It covers the storefront, workshop ordering and the link to the shop system. Fitment data comes from a supplier or your own records, and the software does not create it.

  • Parts counter staff
  • Workshop buyers
  • Catalogue managers
  • Warehouse staff
  • Owners
Modules

What is in the system.

Storefront

Search by vehicle and by any part number.

Workshop ordering area

Trade prices, credit and order history for registered garages.

Part record

Numbers, fitment, prices and stock, all read from the parts shop product.

Order handling

Web orders flow into the same billing and rack picking as the counter.

Returns and claims

Wrong-fit returns and supplier claims against the original bill.

Workflows

How the work runs through it.

Vehicle to order

A buyer picks a vehicle, finds the part, orders and is billed from the shop system.

Workshop order

A garage signs in, sees its prices and balance, orders and the bill posts to its ledger.

Wrong-fit return

A part is returned against the bill, goes back to its rack and the bill is adjusted.

Catalogue and product data

What each product record holds.

Part numbers

OEM, aftermarket and supplier numbers on one record.

Fitment

Makes, models, years and variants linked to each part, so a search by vehicle returns only parts that suit it and hides the rest.

Kits

Listed as parts stocked one by one.

Pricing and order rules

How prices and orders are set.

Retail and trade prices

Set by brand or category, with discount slabs by customer type.

Credit limits

Each garage has a limit and due days, and the site refuses an order over the limit.

Customer back-orders

Parts not on the shelf are recorded with an advance and a call when stock arrives.

Stock and fulfilment

From stock to the doorstep.

Rack stock

Quantity by rack and bin, read by the site on a stated timetable.

Supplier orders

Raised and received against the purchase bill.

Packing

Carrier and packing choice by weight and fragility.

Payments, returns and refunds

Taking money and giving it back.

Payments

Card, UPI and cash on counter; credit orders post to the garage ledger.

Returns

Taken against the original bill, with the part sent back to its rack.

Warranty claims

A faulty part is logged against the sale and the supplier bill until settled.

Admin controls and reporting

What the team can see and change.

Roles

Four screens, four jobs.

Approvals

Orders over a credit limit wait for the owner.

Reports

Sales, credit ageing and returns by reason, from the parts shop product and the site together.

Integrations

What it connects to, and on what terms.

Parts shop product

The source of stock, bills and garage credit.

Supplier catalogues

Fitment and numbers loaded by file.

Couriers

Trialled before they are switched on.

Deployment

How it is set up and run.

Hosted for you

Run on infrastructure we manage or on an account you own.

One make first

A single make is published first.

Customisation boundaries

What can change, and where the edge is.

What can change

Trade rules, pricing slabs, order stages and page design.

Where the edge is

Fitment accuracy depends on the data supplied. The software does not create it.

Migration and training

Moving over and getting people ready.

Moving data

Parts, stock and garage balances come from the shop system, with fitment loaded from files.

Training

A session for the counter, the catalogue team and the warehouse.

Support scope

What support covers.

Scope

Fault fixes and small changes, with contacts and hours in the agreement.

Outside scope

Adding a marketplace, selling into another country or switching fitment source is priced as fresh work.

Subcategory coverage

Where each automotive parts subcategory is covered.

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

  • Engine Parts

    Covered on this page

    Engine fitment, cross-references and kits are what the category solution already holds.

  • Braking Parts

    Covered on this page

    Axle sets, position fields and a return rule are configuration of the category solution.

  • Suspension Parts

    Covered on this page

    Variant fitment, pairing and heavy carriage are configuration of the category solution.

  • Vehicle Lighting

    Covered on this page

    Dual search, side and period fields and packing rules are catalogue configuration in the category solution.

  • Batteries

    Its own solution page

    Date codes, an exchange ledger and hazardous carriage are a different data model from ordinary parts.

Common questions

Questions about this solution.

Does the shop need to change its software?

No, if it already uses the parts shop product. The online side is configured around it.

Is the online store part of the product?

No. The product covers stock, fitment, credit and bills. The storefront and trade ordering are configured on top, and priced after discovery.

Where does fitment data come from?

From a supplier or from your own records. The software holds and searches it but does not create or verify it.

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.