Skip to content
Guides

Off-Plan Inventory Management: The Unit Status Lifecycle Explained

17 November 2026·8 min read
Unit status lifecycle diagram from Draft and Unreleased through Management Block, Available, Block Pending and Blocked.

Off-plan inventory management is the discipline of controlling which units exist, which are for sale, at what price, to whom, and in what state. The unit status lifecycle is its backbone: every unit moves from Draft through approval and release to Available, then through block, reservation and SPA to Sold, and only returns to stock through a controlled termination and repricing step.

This article is part of the developer CRM requirements playbook. It follows a unit from upload to release, through its sales statuses, and back to stock.

The inventory hierarchy

LevelWhat it representsExamples of what lives here
Project or communityThe development as marketedCurrency, master payment plans, default milestones
Phase or sectorA release or sub-divisionLate payment fee rules, discounts, escrow account, completion date
Building or sectionA physical structure or land parcelBuilding name, floors
UnitThe sellable propertyUnit code, type, area, price, status

Put each setting at the lowest level that is still shared. A late payment fee rule that differs between two phases cannot live on the project.

Unit types and their required fields

Property types and unit classification: apartments, villas and townhouses, and plots, each with its own attributes and classification fields.
Property types and the fields each one needs. Open the full-size diagram
TypeRequired fields
Unit (apartment)Building name, floor number, unit code, unit type, unit model, unit category, property usage
Villa or townhouseAs for apartments, plus outdoor areas such as plot and garden
Plot or landLand use, saleable area, total area, plot number

Make the upload template enforce these per type. A plot uploaded with a floor number and no land use will fail later, at SPA generation.

Upload and approval

Inventory upload and approval: the project team uploads a batch, sales operations reviews, finance approves to Unreleased, the sales operations manager approves to Management Block, and units are released to Available.
The approval chain from upload to release. Open the full-size diagram
  1. The project development team uploads an inventory file against a phase or sector, using a predefined template. Some fields are mandatory for every community.
  2. The upload validates each row and reports errors in detail.
  3. Each upload gets a batch name, so a wrong batch can be found and deleted as a whole.
  4. Units start in Draft and are submitted to a sales operations executive for review.
  5. Finance approves the data and prices. Status becomes Unreleased. Finance can reject the batch for re-upload.
  6. The sales operations manager approves. Status becomes Management Block.
  7. Units are released for sale, in a batch or one by one. Status becomes Available.

Finance approving before sales operations is deliberate: prices and areas drive invoices and escrow later, so they are checked first.

The unit status lifecycle

Unit status lifecycle: Draft, Unreleased, Management Block, Available, Block Pending, Blocked, Reservation Pending, Reserved, SPA In Progress, Sold, Termination in Progress, To Be Released and Void, with the approvals that move a unit between them.
Every unit status and the event that moves a unit to the next one. Open the full-size diagram
StatusMeaningMoved by
DraftUploaded, not reviewedProject team
UnreleasedFinance approved, not yet releasedFinance
Management BlockApproved but held back on purposeSales operations manager
AvailableReleased and visible to the sales teamSales operations or MIS admin
Block PendingA salesperson asked to hold it for a customerSales executive
BlockedHold approved for a customer or purposeSales manager or director
Reservation PendingReservation submitted, awaiting approvalsSales executive
ReservedReservation approved and money confirmedFinance
SPA In ProgressSPA started after reservation or down paymentSystem or sales operations
SoldSPA approved by financeFinance
Termination in ProgressCancellation started after SPACredit control or CRM
To Be ReleasedTermination or cancellation approved; awaiting repricingApproval chain
VoidInvalid unit, removed from saleSales admin

Three transitions deserve explicit rules:

  • Expiry. A blocked unit returns to Available when the block expires. See unit blocks and the block and reservation process.
  • Rejection. A rejected reservation or an SPA rejected before registration returns the unit to Available, not to Blocked.
  • Return to stock. A sold unit never jumps to Available. It goes through Termination in Progress and To Be Released, and an administrator reprices it before release to stock.

Void is only allowed from Draft, Unreleased or Available. Voiding a reserved unit would orphan the buyer's money.

Allocation groups

Allocation groups decide who sees and books what.

  • Typical groups: a regional team, a VIP group, general inventory, broker inventory and the customer portal.
  • The director of sales adds and removes users.
  • Units are assigned to a group or to named users.
  • Only members of the assigned group can view and book those units.

The broker group is where most disputes start. If a unit is in the broker group, every broker in it sees the same availability at the same time; if it is not, no broker should be able to request it.

Updating inventory and prices

  • Updates can be individual or in bulk: download, edit, re-upload.
  • Units in Unreleased or Management Block can be updated by the MIS admin.
  • Every change needs finance and sales operations manager approval and keeps a full history.
  • The selling price carries a comment and a revision number, and field history is tracked.
  • Price changes by anyone other than a system administrator go through an approval workflow.
  • An approved price applies to all future transactions, never to existing reservations.
  • Currency is inherited from the project.

What administrators can do

The MIS admin or sales operations role typically can:

  • release units to Available, keep them in Management Block, or move Available units back to Management Block;
  • link and release units to predefined campaigns;
  • assign inventory to sales teams and brokers;
  • set sales and turnover targets by project, phase or sector;
  • export the full inventory to Excel.

Keep these rights narrow. A user who can both change a price and approve a reservation can sell a unit at a price nobody approved.

Approaches compared: where inventory lives

Inventory native in the CRMInventory mastered in an existing property or ERP system
StrengthsOne source of truth, real-time status, full control, unified reportingReuses an established system, strong finance integration, existing processes
WeaknessesNeeds data migration, master data may be duplicated, complex ERP syncIntegration complexity, sync delays, split ownership, dual maintenance
Best forNew implementations and a single-platform strategyDevelopers with a large existing investment and strict finance controls, or a phased migration

Whichever you choose, the unit status must have one master. Two systems that can both set a unit to Reserved will eventually sell it twice.

Common mistakes

  1. Statuses as free text. Use a fixed list with allowed transitions.
  2. Releasing before finance approval. Prices published before approval end up on sales offers.
  3. No batch names. A wrong upload then has to be found unit by unit.
  4. Repricing in place. Keep the revision history; finance will need it.
  5. Allocation by spreadsheet. If the system does not enforce groups, a broker will book a VIP unit.

How Nogbase handles inventory

Nogbase's Developer App imports inventory from Excel through its Data Wizard and per-project import sessions. Units follow a hold, release, reserve and sold lifecycle, and a background worker releases holds when they expire. Developers can share inventory with specific brokers or all active brokers, and brokers see availability in the free Broker App. Nogbase does not replace the finance approval chain, repricing workflow or ERP master data described above.

Next in the series: configuring payment plans and construction milestones.

Frequently asked questions

What unit statuses does an off-plan developer need?

A full lifecycle usually has Draft, Unreleased, Management Block, Available, Block Pending, Blocked, Reservation Pending, Reserved, SPA In Progress, Sold, Termination in Progress, To Be Released and Void. Reservation Cancelled is often tracked as an opportunity outcome that sends the unit to To Be Released.

What is a management block?

A unit that finance and sales operations have approved but deliberately held back from sale, for example to release a floor later at a higher price. Only administrators can move it to Available or back.

Who should approve an inventory upload?

Typically the project team uploads, a sales operations executive reviews, finance approves the data and prices, and the sales operations manager approves before release. Each step can reject the batch back for correction.

What are allocation groups in real estate inventory?

Allocation groups decide which users can see and book which units, such as a VIP group, a broker inventory group or a regional team. Units are assigned to groups or to individual users, and only members can view and book them.

Can sold units go back on sale?

Yes, through termination or cancellation. The unit moves to To Be Released, a repricing decision is made, and only then is it released to stock as Available. It should never jump straight from Sold to Available.

Ahmed Khaire
Written By

Founder at Nogbasehttps://ahmedkhaire.com
unit inventory managementdeveloper CRM requirementsoff-plan salessales operationsUAE

Keep Reading