Originally published at xameon.com.
Two showrooms, one shared “Excel stock list,” three salespeople on WhatsApp. By lunchtime the same Alphard is promised to two buyers. By evening nobody can say which branch still has the key. That is not a rare horror story for Malaysian recond groups—it is the default failure mode when multi-branch stock is a spreadsheet habit instead of an operational rule.
This guide focuses on stopping double bookings and lost units across showrooms. It complements the chassis discipline in One Car, One Record and the booking-to-disbursement map in From Booking to Disbursement. Soft product mention only: Xameon’s RecondOS treats multi-branch stock as part of the same vehicle timeline as digital VSO, not as a separate gallery app.
What “multi-branch recond stock” actually means
It is more than “we have two yards.” Operationally it means every unit carries:
- A durable identity (chassis number, not nickname or plate alone)
- A location (branch, yard, workshop, in-transit)
- A commercial status (available, reserved/booked, sold, on hold)
- Enough document / duty flags that sales know whether a promise is honest
Without those four, Branch B cannot trust Branch A’s “still available” message—and customers pay for the confusion.
How double bookings really happen
Blame rarely sits on one reckless rep. The pattern is structural:
- Laggy master sheet — Branch A updates Excel after closing; Branch B sold from yesterday’s copy
- Plate-first thinking — temporary or missing plates; two people mean different cars
- Chat reservations — “hold for my customer” in a group with no expiry and no chassis
- Transfer without status — unit driven to another branch; stock list still shows old yard
- VSO without stock lock — commercial paperwork starts while inventory still says available
- Weekend heroics — owner approves a deal by phone; nobody writes the reservation
Each path creates the same customer outcome: apology, upgrade scramble, or a refund fight.
Lost units are the quiet twin of double booking
Double booking is loud. Lost units are quiet and expensive:
- Keys in a salesperson’s drawer “for a viewing tomorrow”
- Car sent to workshop; no return-to-yard tick
- Inter-branch transfer noted on paper left on a dashboard
- Sold unit still listed because delivery was delayed and status never flipped
- “Display unit” that is actually reserved, so night security and day sales disagree
If you cannot answer “where is chassis X right now?” in under a minute, you do not have multi-branch control—you have multi-branch hope.
Operating rules that stop the bleeding (before software)
Software amplifies good rules; it cannot replace them. Start here:
Rule 1 — Chassis is the only public name
Internal nicknames (“red Vellfire near gate”) stay internal. Every booking, VSO, transfer, and handover cites chassis. Plates are attributes, not keys—especially pre-JPJ.
Rule 2 — One status vocabulary across branches
Agree a short list: Available / Reserved / Sold / Hold / In-transit / Workshop. Ban poetry (“soft book,” “VIP hold,” “almost sold”) unless it maps to a real status with an owner and expiry.
Rule 3 — Reservation needs expiry and owner
A reserve without a name and a clock becomes a zombie. Twenty-four or forty-eight hours is common; your policy can differ, but some expiry must exist.
Rule 4 — Transfer is a first-class event
Moving a car between branches is not a casual favour. Record from-location, to-location, who drove, and when status becomes Available at the destination.
Rule 5 — VSO implies stock lock
When a Vehicle Sales Order is issued for a chassis, commercial status cannot remain casually Available at another branch. Align stock with the VSO the moment terms are real.
Rule 6 — Physical audit beats dashboard pride
Weekly chassis walk: yard list vs system list. Mismatches are treated as incidents, not jokes.
What good multi-branch visibility looks like
Good is boring:
- Any authorised staff opens a chassis and sees branch, status, and who reserved it
- A second branch cannot silently book the same unit
- In-transit cars are visible as in-transit, not “missing”
- Sales stop asking “anyone hold this plate?” in the group chat
- Owners see which branch is overselling promises vs which is under-rotating stock
That visibility is the inventory half of a recond dealer management system. CRM follow-ups and digital VSOs only stay honest if stock truth is shared.
Where document flags meet stock flags
Recond is not retail fashion. A unit can be physically in Branch A yet commercially unsafe to promise because duty, inspection, or registration blockers exist. Multi-branch software that only shows photos and prices still allows bad promises.
Tie stock status to light operational flags—documents pending, duty pending, registration in progress—as described in the disbursement guide. Sales then sell reality, not optimism.
Soft fit: RecondOS multi-branch stock
Xameon’s RecondOS is built for Malaysian recond dealers who need multi-branch stock on the same thread as digital VSO/e-sign, LOU/COS related tracking, JPJ registration tracking, import duty, insurance, and payments/disbursements. The point is not a prettier catalogue. The point is that Branch A and Branch B stop negotiating with conflicting copies of truth.
Evaluate with two live scenarios in a demo: (1) attempt to reserve a unit already reserved elsewhere; (2) transfer a chassis and watch status follow the car. If your current sheet cannot survive those drills, you already know the gap.
Mini checklist for owners this week
- Pick ten chassis and verify branch + status in under fifteen minutes
- List every “hold” that has no expiry
- Count WhatsApp reservations that never reached a VSO
- Note the last double-booking apology and which rule broke
- Decide whether transfers are logged or tribal
If three or more items feel uncomfortable, multi-branch stock is your bottleneck—not “sales attitude.”
FAQ
Can two branches share one Excel file safely?
Only at very low volume with fierce discipline—and even then weekend lag bites. Shared sheets lack enforced status locks, audit trails, and chassis-level attachments. Most growing groups outgrow them.
Should we reserve by plate number?
Prefer chassis. Plates change or appear late in recond flows. Plate-only reserves are a classic double-book ingredient.
Does multi-branch stock replace JPJ systems?
No. Stock control is internal. JPJ registration remains on official channels; good dealer software tracks status beside inventory, it does not replace JPJ.
How does this relate to one record per car?
They are the same spine. One chassis record holds location, commercial status, VSO, and document milestones. Multi-branch is what happens when that record’s location field is taken seriously.
Soft next step
If double bookings or “where is the car?” chats are weekly events, map one bad week against the six rules above. Then see whether a dealer OS such as RecondOS would enforce status and branch on every chassis. Email Lwhee@xameon.com or use the contact page with how many branches and how you reserve units today—sheet, chat, or whiteboard.
Canonical: https://xameon.com/resources/multi-branch-recond-stock-double-booking-malaysia/
Contact: Lwhee@xameon.com · https://xameon.com/contact/
