Development Agency
Contact Sign in Get a project quote

Service

Tyre and parts e-commerce development

For owners of tyre fitting centres, parts retailers and motor factors who want an online shop that sells by tyre size or registration, knows which branch has the stock, books the fitting bay and prices trade customers correctly, built around how the counter already works.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A tyre and exhaust centre with two branches sells from a supplier price file that the counter staff search on a second screen, quoting by phone and writing the size on a pad.

  • A customer orders online from a generic shop template that does not know tyre sizes, so half the orders arrive with the wrong size and the fitter finds out when the car is on the lift.
  • Stock is in a spreadsheet per branch; a tyre shows as available online because the other branch has it, and the customer is told on arrival that it will be tomorrow.
  • Fitting appointments are in a diary with no link to the order, so two customers arrive at the same bay at nine.

Where it gets harder

A motor factor serving garages has forty trade accounts, each on a different discount, and the prices are in the owner's head and a photocopied sheet.

  • A garage rings for a part, the counter finds it in three catalogues with three different fitments, orders from the supplier if it is out, and nobody tells the garage when it lands.
  • Click-and-collect is a note on the counter.
  • Deliveries go out in a van with a handwritten list.
  • At month end the trade statements are typed from invoices, and the owner cannot say which lines sell, which branch is overstocked, or which supplier orders are still outstanding.

Scope of the service

What the build covers

A custom tyre and parts build normally covers:

  • A vehicle record keyed By registration so a customer's car is remembered with its tyre sizes and fitment details, with an optional lookup from a vehicle-data provider
  • Tyre search by width Profile and rim or by registration, drawing on the supplier price and availability files the business already receives
  • A parts catalogue with fitment data from configured supplier sources So a part is offered only where the data says it fits
  • Stock per branch With online availability showing which branch holds it and when it can be fitted or collected
  • Fitting appointments with bay capacity per branch Booked at checkout and linked to the order
  • Click-and-collect and delivery with zones and cut-off times
  • Trade accounts with pricing tiers Credit terms and monthly statements
  • Supplier ordering For out-of-stock items with the customer told when the order lands
  • The standard shop foundation of cart Checkout, payment through a provider, discounts, order status, returns and customer accounts

How discovery works

Discovery follows one retail tyre order and one trade parts order from search to fitted or collected with you: which supplier files you receive and how often, how fitment is checked today, how bays are allocated, what each trade tier gets, how deliveries are routed and what the monthly statement must show. Each becomes a named stage in the scope document: search by size or registration, order, fitting slot, fitted or collected.

Deliberately out of scope

  • The supplier catalogues and fitment data themselves, which come from the suppliers you contract with
  • Wheel alignment and diagnostic equipment
  • Accounting
  • The workshop job card for mechanical repairs, which belongs to the repair workshop topic

When the scope grows

Scoping scenario

A motor factor with three branches, two delivery vans, forty trade accounts on five tiers, supplier feeds from four distributors and a growing retail tyre trade needs branch stock with transfers, fitment data merged from several suppliers, trade pricing by tier and customer, van delivery runs with proof of delivery and statements per account. That is a different build from a single tyre bay selling online, and the scope document says so.

Deliverables

What you receive

  • Discovery notes from following one retail tyre order and one trade parts order through your counter
  • A written scope document naming each stage, the data sources, the trade tiers and what is out of scope
  • Design of the size and registration search, the product page with fitting slot, the counter order screen and the trade account portal on phone and desktop
  • The build, deployed to your hosting or ours
  • Import mappings for the supplier price, stock and fitment files you name, tested against real files
  • Migration of customer and trade account records, open orders and stock counts from your current system, where practical
  • Training for counter staff, fitters, the branch manager and the owner, with a short written guide
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access, contacts, sample supplier files, the current stock spreadsheets, the trade price sheet and how fitting and deliveries are booked today.

    Project stage: Onboarding

  2. Planning

    Discovery with the owner, a branch manager and a counter assistant; the stage model, supplier data sources and scope document are agreed with a milestone plan.

    Project stage: Planning

  3. Design

    Clickable designs of the tyre search, the parts product page, the checkout with fitting slot, the counter screen and the trade portal, checked on the phones trade customers order from.

    Project stage: Design

  4. Development

    Built in stages: supplier imports and the catalogue first, then search and stock per branch, then checkout, fitting slots and collection or delivery, then trade accounts and supplier ordering.

    Project stage: Development

  5. Client review

    The counter runs a week of real orders alongside the old process, two trade accounts order through the portal, and staff tell us where fitment, stock or pricing does not match the shelf.

    Project stage: Client review

  6. Revisions

    Import mappings, search behaviour, bay rules and tier pricing are adjusted from the review and re-checked against the scope document.

    Project stage: Revisions

  7. Ready for launch

    Stock counted and loaded, trade accounts migrated with their tiers, payments tested with the provider, old product URLs redirected, checklist signed off.

    Project stage: Ready for launch

  8. Delivered

    The business runs on the new shop; optional maintenance and hosting continue under their own agreement.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Supplier and distributor price, stock and fitment files in the formats each one publishes
  • Vehicle-data providers for registration lookup of tyre sizes and fitment details
  • Card payment providers for retail checkout and trade account settlement
  • Carrier and courier services for delivery labels and tracking
  • Email and SMS providers for order updates, fitting reminders and collection-ready messages
  • Accounting software for invoices, trade statements and supplier purchases
  • Barcode scanners at the counter and in the stores for stock and picking

How we would approach it

Worked example

Concept demo

A three-branch motor factor with trade tiers and van delivery runs

The situation

A motor factor with three branches, two delivery vans and forty trade accounts received price and fitment files from four distributors and priced trade customers from a sheet.

Why it is a custom build

This needs a custom build because the catalogue is assembled from several suppliers' data with branch stock and trade pricing on top, which a general shop platform treats as an afterthought.

The scope we would propose

  • Scheduled imports from each distributor merged into one catalogue with fitment per part and the source recorded
  • Stock per branch with transfers between them and online availability showing the nearest branch
  • Trade accounts on five tiers with per-customer overrides, credit terms and a portal where a garage orders by registration and sees its own prices
  • Delivery runs per van with a route order, a proof-of-delivery signature and a message to the garage when the van is on its way
  • Supplier ordering for lines out of stock, with the customer told when the part lands

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Tyres, parts or both, and the number of supplier files to import and merge
  • Number of branches, stock transfers and whether stock is counted in the system
  • Fitting bays per branch and how fitting slots are allocated
  • Click-and-collect, delivery zones, van runs or carrier integration
  • Trade accounts, pricing tiers, credit terms and statements
  • Vehicle-data lookup for registration search
  • Volume of product, customer and order data to migrate and old URLs to redirect
  • Reporting for the owner such as margin by line and stock by branch
  • Hosting choice: your own hosting or ours

Start from a package

Tyre and parts shop package

Tyre search by size or registration, parts catalogue with configured fitment, stock per branch, fitting slots at checkout, click-and-collect, delivery, trade tiers and supplier ordering.

Custom build
View the package

FAQ

Frequently asked questions

Would the package do, or do we need a custom build?

A fitter or retailer with one or two branches, a couple of supplier files and standard trade tiers is usually well served by the tyre and parts shop package configured around your stock. Custom work is the honest answer for several suppliers to merge, van delivery runs, marketplace selling or a parts catalogue with unusual fitment rules. Discovery settles it before anything is quoted.

Where does the fitment data come from?

From the suppliers and data providers you already contract with. We import their files on a schedule and map them to your catalogue; we do not create fitment data ourselves, and the shop shows the source of each fitment so a mismatch can be traced back to the file.

Can customers search by registration?

Yes, where a vehicle-data provider is connected. The registration returns the vehicle and its tyre sizes or fitment details, the customer confirms, and the search is narrowed to what fits. Without a provider the customer searches by size or picks the vehicle from the catalogue.

How are fitting slots linked to orders?

A fitting slot is chosen at checkout from the bay capacity of the branch that holds the stock, and the order and the slot reference each other. If the stock has to come from a supplier, only slots after the expected arrival are offered.

Who owns the shop afterwards?

You do. Source code, catalogue, customer and trade account records and order history are handed over at delivery; hosting and maintenance are optional and separately agreed.

Get a project quote for tyres and spare parts software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences