Double-selling happens because status flags describe a belief, not a lock — the fix is enforcing availability at the database level, not asking agents to check more carefully.
Every real estate sales head has lived through this call: two agents, one unit, both with a buyer who thinks they've booked it. Somebody has to make an apology call, and it's never a good one. The strange part is that this keeps happening at teams that already use a CRM — sometimes an expensive one. So why doesn't the software stop it?
Why Double-Selling Happens in the First Place
It's rarely a training failure. It's a timing failure. A unit sits in a "shared" view — a spreadsheet, a WhatsApp group, a CRM's inventory tab — with a status column that says Available. Two agents look at that column within minutes of each other. Both see "Available." Both tell a buyer "yes." By the time either of them updates the status, the damage is done.
The system didn't fail because someone forgot to check. It failed because checking was ever the mechanism in the first place.
The Common (Broken) Fix: Status Flags
Most CRMs, including generic ones adapted for real estate, handle unit availability with what's called a status flag — a field on the unit record that says Available, On Hold, Booked or Sold. An agent reads the flag, and if it says Available, they act on it.
The problem is that a status flag is a description of the past, not a control on the present. It tells you what the system believed a moment ago — not what's true right now, and it does nothing to stop two people from acting on the same "Available" flag at the same instant.
This is a textbook race condition: two processes reading the same value, both deciding it's safe to proceed, before either one writes back a change. No amount of "please refresh before booking" training fixes a race condition. The fix has to happen underneath the interface, at the point where the actual booking gets written.
What "Database-Level Locking" Actually Means
A database-level lock doesn't ask "what does the status field currently say?" It asks the database itself, at the moment of booking, to hold that specific unit's row exclusively — so that a second, simultaneous booking attempt on the same unit is rejected by the database before it can ever be written, not caught afterward by a human noticing two bookings exist.
Practically, that means:
- The lock happens at the moment of the booking transaction, not on a periodic status check — there's no window of time where two "Available" reads can both succeed.
- It's structural, not procedural. No agent can accidentally bypass it by working fast, working offline-then-syncing, or skipping a refresh — the database itself refuses the second write.
- It works the same way whether five agents are looking at a unit or fifty. The lock doesn't get less reliable as your team or your lead volume grows, the way "someone checks the sheet" does.
What This Looks Like Day to Day
In practice, an agent selects a unit to book. If it's genuinely free, the booking goes through and the unit is locked to that transaction immediately — not "marked," locked. If another agent tries to book the same unit a second later, they get an immediate, honest rejection: this unit is no longer available, chosen by someone else, moments ago. Nobody has to discover the conflict during a follow-up call with an embarrassed buyer.
This is the actual mechanism behind REMEX's inventory module: unit holds and bookings are enforced with row-level database locks, not a status column an agent has to trust. Two agents physically cannot book the same unit — not "shouldn't," cannot.
The Real Cost of Getting This Wrong
Double-selling isn't just an awkward phone call. It's a canceled booking, a refund conversation, a buyer who now tells three friends not to trust your sales process, and — depending on your market — a compliance and reputation exposure with RERA-registered transactions. The fix is cheap to build into a system from the start and expensive to bolt on after the fact, which is exactly why so many CRMs built for other industries never get it right for property sales.