One inventory, one booking process, one set of numbers.
EstateFlow ERP is the sales and inventory backbone the other products read from. It holds every plot, unit and file with price, category and live status; manages dealer holds and quotas; runs the booking-to-sale workflow with discount approvals; and computes agent and dealer commissions from every deal. Finance, recovery and the map all see the same record.
- features
- 12features
- modules
- 14modules
- screens
- 5screens
- webhooks
- 11webhooks
- List price
- PKR 4,675,000 (incl. 10% corner)
- Status
- Booked · discount pending
- Dealer
- Al-Noor Estate · quota 31/40
- Commission
- 2% dealer + 0.5% override · earned
- Linked
- File GV2-0417 · Map polygon #C014
The sales sheet, the dealer’s list and the map disagree
- Availability lives in a spreadsheet that three people edit; plots get sold twice
- Holds are verbal and never expire; good plots sit blocked for weeks
- Discounts are approved on WhatsApp and remembered differently by everyone
- Commission is computed by hand at month end and disputed the same day
How each part of ERP actually works
12 features from the product documentation. Select one to read what it does, the mechanism behind it, the data it holds, the state before and after, and what it connects to.
Inventory master
Every plot or unit with size, dimensions, category, block/phase, facing, floor and price. Bulk import from spreadsheets; bulk price and status updates with history.
Every unit and plot is loaded with attributes via spreadsheet import or the master-plan link; bulk price and status updates keep a revision history.
Size, dimensions, category, block/phase, facing, floor, price, features.
CRM, Maps, QistFlow, Land Management.
Inventory in several spreadsheets.
One master record per unit.
Live availability status
Available, Reserved, Booked, Sold, On-hold, Blocked, Transferred. One status per unit, updated as sales progress, shared with CRM, Maps and QistFlow.
A single status field per unit (Available, Reserved, Booked, Sold, On-hold, Blocked, Transferred) updates as sales progress and is read by every product.
Status, timestamp, actor.
CRM, Maps, QistFlow.
Different lists disagree.
No double-selling; one truth.
Price lists & category premiums
Base price per category, corner and park-facing premiums, phase pricing, launch offers and revision history.
Base price per category, premiums for corner and park-facing, phase pricing, launch offers, revision history with effective dates.
Price list, premiums, offers, effective dates.
Booking, Maps popup, Marketing.
Prices quoted from memory.
Consistent pricing with history.
Holds & dealer allocation
Temporary holds with expiry, allocation of inventory to dealers and per-dealer quotas. Expired holds release automatically.
Temporary holds with expiry; inventory allocated to dealers with quotas; expired holds return to Available automatically.
Hold, expiry, dealer, quota, allocation.
Dealer portal, Maps, CRM.
Verbal holds that never expire.
Controlled, time-boxed holds.
Agent & dealer onboarding
Profiles, documents, role, territory or project and quota. Dealer registration with approval before access.
Onboarding form with profile, documents, role, territory or project and quota; dealer registration goes through approval before access.
Profile, documents, role, territory, quota.
CRM access, HR, Commission.
Informal onboarding.
System-ready salespeople and dealers.
Team hierarchy & territories
Head → team lead → agent, with project or area assignment. Visibility and reporting roll up the hierarchy.
Head → team lead → agent hierarchy with project or area assignment; visibility and reporting roll up the tree.
Hierarchy, territory/project map.
Lead distribution, Reporting.
Flat and unmanaged.
Clear ownership and reporting lines.
Targets & quotas
Monthly and quarterly booking or revenue targets per agent, team and dealer, with live attainment.
Monthly and quarterly targets per agent, team and dealer; attainment tracked live from bookings and revenue.
Targets, achieved, period.
Dashboards, Incentives.
Vague expectations.
Accountable performance.
Booking-to-sale workflow
Booking → confirmation → sale with multi-level discount and refund approvals routed by amount and type.
Stages booking → confirmation → sale with approvals; discounts and refunds route by amount and type to approvers and are logged.
Booking, approvals, discounts, sale.
CRM, QistFlow, Commission, Approvals.
Inconsistent process.
Controlled, auditable sales.
Commission structures
Flat, percentage, tiered by volume, split across agents, manager override, referral; per project and category with effective dates.
A rule builder attaches flat, percentage, tiered, split, override and referral structures to projects and categories with effective dates; the engine applies the matching structure on booking or sale.
Structure, rates, tiers, splits, project/category, dates.
CRM, Ledger, Payroll/AP.
Manual commission math.
Accurate, transparent commissions.
Commission ledger & payouts
Earned → due → paid per agent and dealer, statements on demand, payout scheduling through payroll or AP, clawback on cancellation.
The ledger accrues earned commission, moves it to due on the configured trigger (booking, down payment, clearance), and marks paid on payout; statements generate; cancellations claw back.
Earned, due, paid, balance, deal links.
Payout, Statements, Agent App, QistFlow.
Commission disputes every month.
Trust and clarity.
Performance & leaderboards
Leads, conversions, revenue and activity ranked per agent, team and dealer, with geo-attendance from the field app.
Leads, conversions, revenue and activity are ranked per agent, team and dealer; geo-attendance from the Agent App feeds activity.
Activity, conversions, revenue, rank, attendance.
Insights, Targets, Agent App, HR.
No visibility.
A performance culture.
Approvals & audit
Rule-based approval chains on discounts, refunds, transfers and payouts, with an immutable log of who approved what.
Multi-level approval chains by amount and type with an immutable log of requester, approver, decision and time.
Approval rules, approvers, status, thresholds.
Procurement, QistFlow, Commission, Audit.
Ad-hoc approvals.
Governance and speed.
14 modules, switched on per role. Admins configure rules; everyone else sees only what applies to them.
- Inventory Master
- Status & Availability
- Pricing & Price Lists
- Holds & Allocation
- Phases / Blocks / Projects
- Agent & Dealer Onboarding
- Hierarchy & Territories
- Targets & Quotas
- Booking-to-Sale
- Commission Structures
- Commission Ledger & Payouts
- Performance & Leaderboards
- Approvals
- Multi-Entity Consolidation
One file, start to finish.
A realistic sequence from the documentation, with the state before and after each step. Names and numbers are illustrative.
Live availability, holds and bookings from the Agent App; approvals on the phone for sales heads.
- 01
Load inventory
Phase 2’s 1,140 plots are imported with block, size, category and facing. Price list v3 sets category B at PKR 4.25M with a 10% corner premium.
- 02
Onboard dealers
Al-Noor Estate registers, uploads documents, is approved and allocated 40 plots in Block C with a quarterly quota.
- 03
Hold
A dealer holds 14-C for 48 hours from the portal. The plot shows On-hold on the map and in the CRM.
- 04
Book
The buyer commits. The booking records price, a 5% discount request and the 36-month plan; the discount routes to the sales head.
- 05
Approve and confirm
Discount approved. Status moves to Booked, QistFlow generates the schedule, the agreement generates from Documents.
- 06
Commission accrues
The dealer’s 2% structure and the agent’s 0.5% override compute on booking and post to their ledgers as earned.
- 07
Pay on collection
When the down payment clears, commission moves to due and is scheduled into the month-end payout run.
ERP, screen by screen
Click the sidebar to move between the overview, lists, records, boards and the settings that drive the rules. Sample data on real layouts.
Sales & inventory
All projects · Q3 2026 · Live| Ref | Type | Unit | Requested by | Amount | Status |
|---|---|---|---|---|---|
| AP-2291 | Discount 5% | 14-C · Ph 2 | S. Khan | 212,500 | Awaiting sales head |
| AP-2288 | Refund | 07-A · Ph 1 | Finance | 1,150,000 | Approved |
| AP-2285 | Dealer payout | Al-Noor Estate | Sales ops | 2,340,000 | Awaiting CFO |
| AP-2280 | Transfer fee waiver | 221-F · Ph 2 | H. Malik | 50,000 | Rejected |
Inventory master
All projects · 3,420 units| Unit | Project | Size | Category | List price | Status | Dealer | Updated |
|---|---|---|---|---|---|---|---|
| 14-C | Phase 2 | 10 Marla | B · corner | 4,675,000 | Booked | Al-Noor Estate | 12:04 |
| 15-C | Phase 2 | 10 Marla | B | 4,250,000 | Available | — | Yesterday |
| 44-C | Phase 2 | 1 Kanal | K · corner | 9,460,000 | On hold | Al-Noor Estate | 31 h left |
| 221-F | Phase 2 | 1 Kanal | K · park | 9,300,000 | On hold | City Marketing | 12 h left |
| 07-A | Phase 1 | 5 Marla | A | 2,450,000 | Sold | Direct | 10:15 |
| G-12 | Phase 3 | 5 Marla | A | 2,600,000 | Reserved · ballot | — | 14 Sep |
Booking BK-2026-0417
Plot 14-C · Phase 2 · Ahsan Raza · 05 Jan 2026- 04 JanHold placed by dealer · 48 h
- 05 Jan 12:04Booking created from CRM · unit locked
- 05 Jan 12:06Discount request AP-2291 → sales head
- 05 Jan 15:30Approved · agreement generated · schedule created in QistFlow
- 05 Jan 15:31Commission accrued: dealer 88,825 · override 22,206 · due on down payment
- 07 JanDown payment cleared · commission moved to Due
- Status
- Confirmed
- File
- GV2-0417
- Documents
- Agreement · Receipt
- Map
- Polygon #C014 · Booked
Commission ledger
September · 23 payees · PKR 9.8M due| Payee | Type | Deal | Structure | Earned | Due | Paid | Status |
|---|---|---|---|---|---|---|---|
| Al-Noor Estate | Dealer | BK-0417 | 2% on collection | 88,825 | 88,825 | 0 | Due · payout 30 Sep |
| S. Khan | Agent | BK-0417 | 0.5% override | 22,206 | 22,206 | 0 | Due · payroll |
| City Marketing | Dealer | BK-0402 | Tiered 2.5% | 106,250 | 0 | 106,250 | Paid 15 Sep |
| Skyline Estate | Dealer | BK-0388 | 2% on collection | 85,000 | 0 | 0 | Clawback · cancelled |
| H. Malik | Agent | BK-0410 | 1% split 60/40 | 26,000 | 26,000 | 0 | Awaiting approval |
Commission structures & approvals
Applied automatically on booking- Rate
- 2% of net price
- Accrue
- On booking
- Due
- On down payment cleared
- Clawback
- 100% if cancelled within 90 days
- 1–10 bookings / quarter
- 2.0%
- 11–25
- 2.5%
- 26+
- 3.0%
- Quota
- 40 plots · Block C
- Discount ≤ 3%
- Team lead
- Discount 3–7%
- Sales head
- Discount > 7%
- CEO
- Payout > 1M
- CFO
Scheduled to email or exported to Excel and PDF. Every report drills down to the record.
- Availability by phase, block and category
- Inventory aging and absorption rate
- Price-list history
- Hold expiry and release log
- Target vs achievement by agent, team, dealer
- Commission liability, due vs paid
- Approvals pending and turnaround
- Revenue potential of remaining stock
Who uses it, and what each role sees
Access is scoped by role, team and field. A dealer never sees another dealer’s file; an agent never exports the database.
Sales admin / inventory controller
Inventory master, price lists, holds and releases
Dealer
Allocated inventory, own holds, bookings and commission statement
Sales head
Targets, leaderboards, discount and payout approvals
Finance
Commission ledger, payout runs, clawbacks
Management
Bookings, absorption, dealer performance, approvals log
| Module | View | Create / edit | Approve | Export | Configure | Delete |
|---|---|---|---|---|---|---|
| Inventory Master | OwnOwnTeamTeamAll | OwnOwnTeamTeamAll | ———TeamAll | ———TeamAll | ————All | ————All |
| Status & Availability | OwnOwnTeamTeamAll | OwnOwnTeamTeamAll | ———TeamAll | ———TeamAll | ————All | ————All |
| Pricing & Price Lists | OwnOwnTeamTeamAll | OwnOwnTeamTeamAll | ———TeamAll | ———TeamAll | ————All | ————All |
| Holds & Allocation | OwnOwnTeamTeamAll | OwnOwnTeamTeamAll | ———TeamAll | ———TeamAll | ————All | ————All |
| Phases / Blocks / Projects | OwnOwnTeamTeamAll | OwnOwnTeamTeamAll | ———TeamAll | ———TeamAll | ————All | ————All |
| Agent & Dealer Onboarding | OwnOwnTeamTeamAll | OwnOwnTeamTeamAll | ———TeamAll | ———TeamAll | ————All | ————All |
Own = only records assigned to me · Team = my team’s records · All = the whole organisation. Field-level rules can further hide price, owner or CNIC per role.
Toggle to see how each control changes the posture score. Defaults shown are our recommended configuration.
Every action writes an entry with actor, entity, before and after value and time. Entries cannot be edited or deleted, only exported. Try it: perform an action.
- 12:04:11S. KhanBooked plot 14-C · ERP
- 12:03:48SystemLock acquired · unit 14-C
- 11:58:02A. ButtApproved discount 5% · AP-2291
- 11:41:30H. MalikExported leads (team, 84 rows)
- 11:20:15AdminChanged role: F. Noor → Field agent
- 10:15:07SystemBlocked transfer · GV2-0930 (defaulter)
What happens without anyone clicking
Rules run the routine work. Flo, the AI assistant, handles the parts that need language or judgement, and every AI action is logged.
Automations
- Expired holds return to Available
- Status changes on booking, payment and possession
- Commission accrual on booking, due on collection
- Approval routing by amount and type
- Target-progress alerts
- Low-availability alerts by block
Flo in ERP
- Demand-based pricing suggestions
- Absorption forecasting by block
- Dealer churn risk
- Commission anomaly detection
Outbound WhatsApp uses approved templates. Low-confidence cases escalate to a person.
Connects to anything, not just the list
Every connector in the catalogue, the full REST API and a webhook for every state change. If it has an API, EstateFlow talks to it.
Every connector below is available to ERP. Those most used with it are highlighted; anything not listed connects through the REST API, webhooks or Zapier / Make / n8n.
- Zameen
- Bayut
- Graana
- OLX Property
- Meta Lead Ads (Facebook, Instagram)
- Google Ads lead forms
- TikTok lead forms
- Website forms
- Landing-page builders
- Chat widget
- QR / offline import (CSV, Excel)
- WhatsApp Business API (Meta Cloud API or any BSP)
- SMS gateways (Telenor, Jazz, Zong, Ufone, Twilio)
- Email (SMTP, Gmail, Outlook, SendGrid)
- VoIP / cloud PBX (SIP, Asterisk, Twilio Voice)
- Call tracking numbers
- Push notifications (FCM, APNs)
- Payment gateways (PayFast, Safepay, JazzCash, Easypaisa, Stripe)
- Bank transfer / IBFT references
- Pay links
- Bank statement import (CSV, MT940)
- Bank feeds (Enterprise)
- POS terminals
- QGIS projects (.qgz)
- PostGIS
- GeoServer (WMS / WFS)
- Shapefile, GeoJSON, KML, DXF / CAD import
- Mapbox, Leaflet, OpenLayers clients
- ArcGIS / Esri (Enterprise)
- Satellite imagery providers
- GPS from field devices
- QuickBooks
- Xero
- Sage
- Odoo
- Tally
- SAP / Oracle / Dynamics (Enterprise)
- FBR e-invoicing
- Excel / CSV export for any ledger
- CNIC OCR
- NADRA verification partners
- DocuSign
- Adobe Sign
- PandaDoc
- Google Drive
- OneDrive / SharePoint
- Dropbox
- S3-compatible storage
- Biometric devices (ZKTeco, Hikvision)
- Bank payroll files
- Google Workspace / Microsoft 365 directories
- SSO: SAML, OIDC, Azure AD (Enterprise)
- Boom barriers & RFID
- ANPR cameras
- Smart meters (electricity, water, generator)
- IoT sensors (MQTT)
- Sales-centre kiosks & touch tables
- Digital signage
- Power BI
- Tableau
- Looker Studio
- Metabase
- Zapier
- Make
- n8n
- Google Sheets
- Slack / Teams alerts
- Everything in the UI is available through the REST API: read, create, update, and the same approvals and locks apply.
- Every state change emits a webhook within seconds, with a signed payload and automatic retries.
- Per-organisation API keys with scopes per module; OAuth 2.0 for partner apps; rate limits published per plan.
- JSON over HTTPS, cursor pagination, filtering and sorting on every list endpoint, bulk endpoints for imports.
- Sandbox organisation for testing; OpenAPI 3.1 specification and Postman collection; changelog with versioned endpoints (/v1).
- /v1/inventory
- /v1/price-lists
- /v1/holds
- /v1/bookings
- /v1/approvals
- /v1/dealers
- /v1/targets
- /v1/commission-structures
- /v1/commission-ledger
- /v1/payouts
Each resource supports list, get, create, update and (where allowed) delete, with the same permissions and approvals as the UI.
/v1/units?project=phase-2&status=available&category=BLive availability for a website or partner
/v1/holdsPlace a 48-hour hold from a dealer system
/v1/bookingsCreate a booking (locks the unit, triggers QistFlow and Documents)
/v1/commission-ledger?payee={id}&status=dueCommission due per dealer
curl https://api.estateflow.live/v1/units \
-H "Authorization: Bearer ef_live_•••" \
-H "Content-Type: application/json"- unit.status_changed
- hold.placed
- hold.expired
- booking.created
- booking.confirmed
- booking.cancelled
- approval.requested
- approval.decided
- commission.accrued
- commission.due
- payout.paid
Every state change in every product emits an event. Subscribe per event type, per project or for the whole organisation. Signed with HMAC-SHA256, retried with backoff for 24 hours, replayable from the dashboard.
POST https://your-server.example/estateflow
X-EstateFlow-Signature: sha256=3c9a…12ff
Content-Type: application/json
{
"id": "evt_01J8Z6M9QK",
"type": "booking.created",
"occurred_at": "2026-09-06T07:04:12Z",
"organisation": "green-valley",
"data": {
"booking_id": "BK-2026-0417",
"unit": { "id": "14-C", "project": "phase-2", "block": "C", "size": "10 Marla" },
"customer": { "id": "c_88112", "name": "Ahsan Raza" },
"plan": "36m-cat-b",
"net_price": 4441250,
"agent": "u_0142",
"dealer": "d_al-noor"
}
}Connected EstateFlow products
- CRMEvery lead answered in seconds, tracked to booking.
- QistFlowThe plot-file payment engine: schedules, reminders, recovery, transfers.
- MapsThe society map, alive: every plot coloured by real status.
- AccountsBooks that post themselves from bookings, receipts and purchases.
- HR & PayrollAttendance from the field, payroll with commissions, payslips on the phone.
- Documents & ContractsAgreements, deeds and receipts that generate themselves, signed with a trail.
ERP runs standalone or with the rest of the suite on the same database. Quotes are per organisation, based on users, plots and files.
- Demo on your own data
- Data migration from spreadsheets or your current system
- Onboarding and WhatsApp template approval
About ERP
01 Is the ERP the same inventory that the map and QistFlow use?
Yes. There is one inventory master. CRM bookings, Maps colours, QistFlow files and Balloting allotments all read and write the same unit record.
02 Can commissions be paid on collection instead of booking?
Yes. A structure can accrue on booking and become due on down payment, on a percentage collected or on full clearance, which is how most Pakistani dealer networks operate.
03 How are dealer quotas and holds controlled?
Inventory is allocated to dealers with a quota. Holds have an expiry (for example 48 hours) after which the unit returns to Available automatically.
See ERP on your own data.
A 45-minute demo on your own data. We load a sample of your inventory and files before the call, so you see your plots, your plans and your numbers, not a sample scheme.
- One block of your scheme digitised on the live map
- A booking → schedule → WhatsApp reminder, end to end
- A file transfer with the lock and dues check
- A rollout order and a written quote within two days