Use case · Off-plan inventory
One governed source of truth — project → building → unit, the visual stacking plan, statuses and pricing. Edit a unit once; every surface, feed, listing and agent reads the same live record.
The problem
Advisors reserve the same unit for two clients. Availability drifts out of date. A manager can’t tell what’s really available, reserved or sold without opening three different files — and quotes built by hand come back with errors.
Availability and price live in scattered files. Two advisors reserve the same unit; no one can confirm what’s really free without digging through three versions.
Status and price live on one record. Edit a unit once and it’s current everywhere — no double-booking, no conflicting price, no third file.
How it works
Bring your book in via CSV/Excel or the API. Propcore builds the project → building → unit hierarchy straight from the file.
Edit a unit once. Status, price, pricing mode and promotions all live here — on one record, with a history.
Storefront, portal feeds, listings and agents all read the same core — so every surface is always current.
Proof
Reads from the core
FAQ
Import a CSV or Excel price list, or push them through the API. Propcore builds the project → building → unit hierarchy from the file, so your whole book is in one place from day one.
Yes. The model is project → building → unit, with sections in between. Every unit lives under its project, and you manage the whole portfolio — many projects, many buildings — from one core.
Yes. Each project has its own schema, so you define the fields that matter for that development — view, orientation, payment plan, finish package — without forcing every project into one rigid shape.
Yes. Status and price live on the governed record. The moment a unit is reserved, sold or repriced, every surface, feed, listing and agent reads the new value — no manual re-export, no stale number.
See it run against two of your real projects.