Your billing package
A tyre is a quantity
The serial is dropped at the first invoice — and with it the one fact that settles every later argument.
Every tyre has a serial. Most channel systems throw it away at the first invoice. Track the channel to the serial.
Your billing package
The serial is dropped at the first invoice — and with it the one fact that settles every later argument.
Your claims tool
Inspection on paper, pro-rata on a calculator, settlement by phone. The claim never meets the sale it came from.
Your scheme circular
A slab on one pattern and a rebate on a size range, settled from memory at each region.
Your distributor's godown
Where the serials actually are is a survey, not a query — until the audit.
The stock loop carries identity down the channel; the claims loop carries evidence back up it. Both write to the same ledger the dealer's credit lives on.
Claims loop
The returned tyre's serial, tread-depth reading, photos and defect finding are captured on a checklist, with the serial's own sale history already on the record. The claim computes its pro-rata value from the readings under the brand's rule, routes through approval, and settles as a credit note into the same ledger the dealer's account lives on — per line, rejections carrying reasons.
How the claims engine works →Pattern, size and category are real attributes on the product master, so a scheme scopes to exactly the slice it means and the server prices it the same in the officer's app, the dealer's portal and the counter. Consumption accrues against qualifying order lines, so the quarterly rebate settles from arithmetic the dealer can check.
Explore Rewards & Trade Schemes →The counter, the serial, the claim and the credit — each in depth.
Stock by pattern, size and serial; credit at the counter; claims dealers raise themselves.
Read the deep diveThe serial discipline durables brands run — the same ledger, aimed at the tyre counter.
Read the deep diveEvidence-first claims, decided line by line, settled as credit notes into the books.
Read the deep diveLimits enforced at order time; one ageing truth from the officer to the CFO.
Read the deep diveFor a tyre brand selling through a dealer network in India, a tyre is an awkward product for channel software: it is serialised like an appliance, claimed against like a vehicle part, discounted in slabs like FMCG, and sold through a channel that ends at a fitment shop the brand has never billed directly. Most tyre dealer management software picks one of those facts and ignores the rest — a billing package that treats a tyre as a quantity, or a claims tool bolted onto nothing. xMatix carries all four on one platform: serialised stock from plant despatch to the fitment counter, warranty claims settled from inspection evidence, schemes scoped by pattern and size, and credit that gates at the moment of order.
Tyres move plant → regional distributor → dealer → fitment counter, and each hop is a place identity and accountability traditionally leak. On xMatix every tier is a party on one master and every location is a node on one append-only stock ledger, so a despatch from the plant, the distributor's godown stock, the dealer's counter stock and the transfer between them are entries in the same books. Field teams work the dealer tier as planned, geo-verified beats — stock checks, order capture with schemes applied by rule, collections against invoices — the discipline durables brands run, aimed at the tyre counter. What the brand gets back is the view it has never had: where the stock actually is, tier by tier, without asking anyone to fill a sheet — and books that post themselves as the stock moves, GST on the line, e-way bills raised from the despatches that need them.
Every tyre carries an individual identity, and a channel system that drops it to a model-level count throws away the one fact that settles arguments. Units despatch as serialised lots; transfers clone the lot with identity intact; the dealer's sale binds serial to buyer. That is what makes the hard questions queries: which serials have sat unsold past a season, which dealer sold the tyre now coming back as a claim, whether the units in a disputed despatch were ever received. Ageing by serial and location surfaces the slow stock while a transfer or a scheme can still move it — before it becomes next year's write-off, or worse, a very old tyre sold as new.
Tyre warranty is pro-rata by construction — the settlement depends on measured wear — which means the claim is only as good as its evidence. On xMatix the claim starts from an inspection: the returned tyre's serial, tread-depth reading, photos and the defect finding captured on a checklist, the serial's own sale history already on the record. The claim computes its pro-rata value from the captured readings under the brand's rule, routes through approval, and settles as a credit note into the same ledger the dealer's account lives on — decisions per line, rejections carrying reasons. It is the same claims engine that runs automotive warranty claims, with the tyre inspection as the evidence.
Tyre schemes are never "10% off everything" — they are a target on truck radials, a slab on a pattern the plant needs to move, a quarterly rebate on a size range. Because the product master carries pattern, size and category as real attributes, schemes scope to exactly the slice they mean, and the server prices them identically in every order — the officer's app, the dealer's portal, the counter. Consumption accrues in a ledger tied to qualifying order lines, so the quarterly rebate settles from arithmetic the dealer can check rather than a regional interpretation they have to contest.
The dealer tier gets its own full treatment — credit and collections at the counter, stock by pattern and size, self-raised claims, a portal for ordering — on DMS for tyre dealers. The short version: the dealer sees their own catalogue at negotiated terms, their live outstanding, their claim status; the brand sees sell-through and exposure per dealer. Both are reading the same ledger, which is what keeps the relationship out of the argument business. Credit deserves the emphasis, because tyres are a working-capital trade: the fleet account buys sixteen at a time on terms, the dealer carries that credit, and the distributor carries the dealer's. Limits enforced at order save at every tier — with an approval path for the deliberate exception — keep the chain's exposure a set of live numbers instead of a quarter-end discovery, and collections allocated to specific invoices keep the ageing honest all the way up.
The last leg — dealer to fitment shop — is where visibility usually ends. Where dealers bill on the platform or through the portal, that secondary sale arrives at source: serial, buyer, date. xMatix does not pretend to be a vehicle-fitment lookup — the catalogue models patterns, sizes and variants, and what fits which vehicle stays the fitter's trade. What the platform adds is that when the sale happens, the serial's journey is complete, the warranty has a start date that is a fact, and the brand's secondary numbers are transactions rather than estimates.
Three different products answer to "tyre software", and buying the wrong one is common. This page is the third:
| Category | Who runs it | What it records |
|---|---|---|
| Tyre shop POS | One fitment shop | Counter billing, the shop's own stock, fitment jobs |
| Fleet tyre management | A transport fleet | Tyres per vehicle position, wear, rotation and replacement |
| Dealer network & secondary sales (xMatix) | The tyre brand and its distributors and dealers | Serialised stock across tiers, dealer orders and GST invoices, schemes by pattern and size, pro-rata claims, credit and collections, secondary sales |
Units despatch as serialised lots on an append-only inventory ledger; every transfer between plant, distributor and dealer clones the lot with serial identity intact, and the dealer's sale binds serial to buyer. Any serial's location and history is a query at any point, and in-transit units remain real, valued stock — with the e-way bill for each despatch in India that needs one raised from the same document.
The claim is raised from an inspection carrying the serial, tread-depth readings, photos and the defect finding. The pro-rata value computes from those readings under the brand's configured rule, the claim routes through approval, and settlement posts as a credit note against the dealer's account — per line, with rejections carrying reasons — in the same GST books the dealer's invoices live in.
Yes — pattern, size and category are attributes on the product master, and schemes scope to any slice of them: a slab on one pattern, a rebate on a size range, a target on a category. The server applies the same definition in every order channel and accrues consumption against qualifying lines.
Where the dealer bills on the platform or takes orders through the portal, the dealer-to-shop sale is captured at source with serial and buyer. The brand's sell-through is then a set of transactions, not a survey — and the warranty clock starts from a recorded sale.