Inventory, bookings and payment schedules: where real estate sales data breaks

How the data usually lives today

A typical mid-size developer runs sales on four things: an inventory sheet maintained by the sales coordinator, a CRM where channel partners and sales executives log enquiries, a price sheet circulated as a PDF, and a collections sheet in accounts that drives demand letters. Each one is reasonable on its own. The trouble is that a unit’s real state is spread across all four, and they update at different speeds.

An illustrative example: one unit’s journey

Consider a hypothetical residential project in Thane with two towers. Follow unit B-1204 over three weeks. All names, prices and dates are invented.

Hold. On Monday, a sales executive puts B-1204 on a 48-hour hold for a family visiting the site. They mark it “Hold” in the CRM. The inventory sheet still shows “Available”, because the coordinator updates it in the evening.

Double-sell risk. On Monday afternoon, a channel partner checks the inventory sheet, sees B-1204 available and promises it to another buyer at the previous week’s price, because the PDF price sheet they have is from before the floor-rise revision. Two people now believe they have the unit, at two different prices.

Booking. On Wednesday, the first family pays a booking amount. Accounts creates a payment schedule in the collections sheet: 10% on booking, then construction-linked instalments. The CRM status changes to “Booked”. The channel partner is told the unit is gone, and an awkward call follows.

Cancellation. Two weeks later, the family cancels after a loan rejection. Sales marks the CRM “Cancelled”. The inventory sheet is updated to “Available”. But the collections sheet still holds the old schedule, and the next demand letter run picks up the slab-completion instalment for B-1204 against the cancelled buyer.

Rebooking. A new buyer books B-1204 at the revised price. Accounts creates a second schedule. For a few days, the unit has two live schedules, one for a buyer who has left, and the demand letter for the new buyer uses the old total because someone copied the row.

Nothing in this story requires a careless employee. Every error comes from status, price and schedule living in different places.

The single unit record

The remedy is to treat the unit, not the lead or the sheet, as the centre of sales data. One record per unit should hold:

• Status: Available, Held (with expiry), Booked, Agreement executed, Cancelled (pending refund), Registered.

• Current price: base rate, floor rise and other charges as of today, with the effective date.

• Current buyer link: exactly one active buyer or none.

• Active payment schedule: exactly one, tied to the active buyer.

• History: every status change, who made it and why.

Then define who can change each status. An illustrative set of rules:

1. Any sales executive can place a hold, which expires automatically after a set time.

2. Only the sales head can extend a hold or override another executive’s hold.

3. A booking requires a recorded payment reference from accounts.

4. A cancellation requires the sales head’s approval, and it closes the active schedule before the unit returns to Available.

5. Only the pricing owner can change price, and the change is effective from a date, never backdated silently.

A test for your current setup

Run these questions on your own data this week:

• Can you name one place that shows every unit’s status right now?

• If two people try to hold the same unit at the same minute, what stops the second one?

• When the price changes, how many documents need updating, and who confirms they were?

• After a cancellation, what closes the old payment schedule and stops its demand letters?

• Can you see, for any unit, every status change and who made it?

• Do channel partners see live availability, or a copy?

If you answer “a person remembers” to two or more, the process depends on individuals rather than on the record.

When a focused system is justified

If your project has a few dozen units, one coordinator and little channel-partner activity, a well-locked sheet with these status rules may be enough. Tighten permissions and add a hold expiry first.

A focused system earns its cost when several people book in parallel, channel partners need live availability, and demand letters must follow the active schedule without manual copying. At that point, a unit-centred system with sales, collections and documents reading the same record removes whole categories of error. It does not need to replace your accounting software; it needs to be the single source for unit status.

Where SolvTree fits

This maps to our custom systems and AI-native ERP work for real estate: unit inventory, bookings, cancellations and payment schedules on one record, with status rules your team agrees. We usually start with inventory and holds for one project before connecting collections and demand letters.

Next step: If you want to see where your own sales data could break, book a free 30-minute operational audit and we will map one unit’s journey from enquiry to registration with you. The report is yours to keep.