Projects, phases & units

Inventory in the Hub is a hierarchy. A project contains phases (and optionally buildings and floors), and the leaves of the tree are individual units — the thing you actually sell. A unit is sometimes called a lot in some deployments; it is the same record.

The hierarchy

1. Project — a development with its own address, timeline, and team.
2. Phase / building / floor — structural grouping for scheduling, pricing, and reporting.
3. Unit type — a reusable template (layout, area, default price rules) applied to many units.
4. Unit — a single sellable item with its own number, area, orientation, price, and lifecycle state.

Spinning up a project from a template

You rarely build a project from scratch. Define unit types once, then generate floors and units in bulk — a 12-floor building with 6 units per floor is 72 units created in one step, each inheriting its type's defaults and ready to override.

Unit types

A unit type bundles the attributes units share: layout, area band, base price rule, and which documents apply. Change the type and the change is available to every unit that uses it — without overwriting per-unit overrides you have already made.

Per-unit attributes

• Number / identifier and physical attributes (area, floor, orientation, view).
• Price — inherited from the unit type's rule, overridable per unit.
• Lifecycle state — see The unit lifecycle.
• Linked records — the buyer, contract, and payment schedule once a sale begins.

Templates make new projects spin up in minutes — not weeks of consulting. Define your unit types once and the next tower is a five-minute job.

Next

With inventory in place, the next thing to understand is how a unit moves from available to sold: The unit lifecycle.