Unit inventory (SPA)
Apartments, offices and shops as records with their own fields: block, floor, m², type, aspect, price, status.
In property you do not sell a product, you sell a specific unit. Which apartment went to whom, at what price and on what payment plan has to live in the system.
At a glance
What comes up with firms selling projects:
The structure we build with developers and agencies:
Apartments, offices and shops as records with their own fields: block, floor, m², type, aspect, price, status.
Unit status (available, optioned, sold) tracked centrally so clashes are prevented.
A project-level pipeline with interest, viewing, option, contract and title stages.
Deposit and instalment plans attached to the deal with automatic due-date reminders.
Conversion reporting for listing portals, social media and field sources.
Handover, keys and warranty requests run as a separate process.
The standard CRM structure does not fit property sales, because what is sold is a specific unit. Block A, 7th floor, three-bedroom; with its own price, its own aspect and its own status.
With Smart Process Automation we define units as their own record type. Each has its own fields, its own status stages and a Kanban view, and can be linked to customer records.
Optioning the same apartment to two buyers costs you a customer and your reputation. With a list kept in Excel it is unavoidable.
Run through unit records, an option becomes a status change; the second agent sees it immediately. When the option period expires the unit returns to available automatically and the agent is notified.
Work does not stop when the contract is signed; deposits, interim payments and instalments have to be tracked. Once that tracking falls into a spreadsheet, delays are noticed late.
We attach the payment plan to the deal. Reminders go out before instalments fall due and a task opens for the owner when a payment is late. Collection status can be reported.
When post-handover requests; snagging, warranty, faults; land with the sales team, sales slows down and the requests get lost.
We route them into their own pipeline with its own stages, owners and SLA. The customer record stays the same, so who bought which unit and what happened afterwards is visible in one place.
The standard status structure we use on unit records.
| Status | Meaning | Automatic behaviour |
|---|---|---|
| Available | Open for sale | Appears in the list and on the sales office screen |
| Optioned | Held for a buyer for a set period | Released automatically when the period ends |
| In contract | Paperwork under way | Reminders for missing documents |
| Sold | Contract completed | Payment plan tracking begins |
| Handed over | Keys delivered | The post-handover pipeline opens |
| Blocked | Withdrawn from sale | Hidden from the list, reason field required |
How would this work in your process?
In a free 30-minute call we listen to your workflow and map out how this would run in your company.
The order we follow with firms selling projects:
Unit fields, statuses and project hierarchy are defined.
The existing unit list is imported from Excel.
Stages, option rules and assignment logic are built.
Payment tracking and the post-handover process are built.
Sales office and management training, then the switch.
The modules we most often roll out alongside this one; they reinforce each other in the same setup.
Collecting leads is the easy part. Responding quickly, assigning correctly and following up consistently is where deals are won. We build Bitrix24 around those three things.
When the pipeline is unclear, nobody knows which deals are moving and which are stuck. We design your stages around your real sales process and make the next step visible on every card.
When quoting, invoicing, terms and collection live in separate tools, cash slows down. In Bitrix24 we keep all of those steps on the same customer record.
Whichever channel a service request arrives through, it should land in the same queue with an owner and a deadline. That is exactly how we configure the Bitrix24 Contact Center.
In health tourism running ads is easy; turning the leads into treatments is not. The difference sits in your reachability rate, your speed to first contact, and knowing which form actually brings patients.
The most expensive loss in a clinic is a no-show. The second is a check-up nobody remembered. Systematic reminders solve most of both.
In e-commerce the profit is in the second order. Yet most stores know the customer as an order number rather than as a person.
Yes. We import the unit list with field mapping, preserving block, floor, type, m², price and status. After the import the inventory is managed in Bitrix24.
Yes. We manage portfolio listings as unit records too, with owner, commission rate and mandate period fields. Rules can also be built to match buyer requirements to listings.
If the portal sends email notifications or has an API, yes. For email-based notifications we connect the mailbox and create records automatically; where there is an API we build a direct integration.
Yes. If your accounting program has an API or a ready Market app, collection data can be synchronised both ways so the due-date tracking in the CRM matches real payments.
Yes. The Bitrix24 mobile app shows unit availability, lets you create customer records and log visit notes. It tends to be the most used feature for field teams.
Book a free intro call and we'll walk through your process and show which settings fit you.