Mall management software is bought rarely and lived with for a decade, and most of what distinguishes systems is invisible in a demo. Dashboards converge; engines do not. Here is the checklist we would use on any vendor — including ourselves.
1. Where do lease terms live?
If escalations, lock-ins, exclusivity clauses, co-tenancy terms and turnover-rent structures live in a PDF and a spreadsheet, the software is a filing cabinet. The test: change an escalation step, and see whether next month's bill changes by itself. Lease terms must be structured data the billing engine reads directly, versioned so past periods bill under past terms.
2. Can it explain a bill?
Pick a real invoice from last year and ask the vendor to derive it live: base rent, escalation applied, turnover rent against the sales base with exclusions, CAM share from the pool. If the answer involves exporting to Excel, every future dispute will too.
3. How complete is sales capture?
Turnover rent is only as good as the sales base. Ask what the system does about tenants on third-party POS, about delivery-aggregator orders, about nil-sales days, about the store whose declared sales diverge from footfall. Ask to see the audit-to-rebill workflow, not just the declaration form.
4. What happens when the internet drops?
Parking barriers, food-court tills, access doors and meters are physical infrastructure. A cloud-only system means a mall that cannot take payments or lift a barrier during an outage. Hybrid deployment — an on-site appliance that keeps the physical layer running and reconciles when the line returns — is the difference between an incident and an evening of chaos.
5. Is the finance output finance-grade?
Invoices must land in a real ledger with your jurisdiction's tax rails — GST e-invoicing in India, the local equivalent elsewhere — and support the entity structures malls actually have: SPVs, co-ownership, strata. If finance re-keys the billing system's output into the accounting system, you have bought a very expensive calculator.
6. Integrate or replace — does the vendor let you choose?
- A mall is not greenfield: parking, CCTV, BMS, meters and tenant POS estates already exist.
- The right posture is connectors for what works and replacement only where it earns it — with bespoke integration treated as part of the engagement, not a change request.
- Ask who owns each integration when it breaks. 'Their API changed' is not an answer a GM can use.
7. Commercial structure
Per-module and per-user pricing punishes adoption — the opposite of what you want from a system whose value is everyone working in it. Prefer a flat per-property subscription with hardware and setup as a transparent one-time line. And ask what an upgrade costs; the honest answer should be nothing.
CuroCentral is built to pass this checklist, and we publish it anyway: a buyer who asks these questions ends up with a better system, whoever they choose.