Work · Concept platform / Idealink Lab
Mall OS
A connected-member operating system for malls — as a working concept.
What it is
Mall OS is a concept for a connected-member platform: one member identity across a mall's tenants, a receipt and transaction layer, a points ledger, campaigns and rewards, and an operator command centre with transaction and campaign intelligence.
Why it needed to exist
Malls know footfall and rent; they rarely know the customer. Tenants run disconnected loyalty programs. A shared layer would let a mall act like one product without replacing its tenants' systems.
What Idealink did
Idealink built the concept as a working demo — landing page, member flow and operator console — to test the primitives. It is a Lab concept, not a live deployment.
- Status
- Concept
- Relationship
- Idealink venture
- Industry
- Shopping centres
- Period
- 2026 — concept
- Platform
- Web concept
- Idealink role
- Platform concept, product design, engineering of the demo
Thesis
A mall is a marketplace without a shared customer layer. Mall OS is the concept-platform story: what happens when member identity, receipts, a points ledger, campaigns, rewards and analytics become reusable primitives — shown as a working concept, not a shipped platform.
01
The primitives
Reusable pieces any mall could compose.
- Member identity shared across tenants.
- A receipt and transaction layer that turns purchases into events.
- A points ledger with campaign-driven multipliers.
- Rewards, redemptions and campaign intelligence for operators.
- Analytics over members, tenants and campaigns.
Concept platform. Nothing here is a customer deployment; it exists to test whether the primitives hold.
Outcome
Where it stands
A working concept demo with a member flow and an operator command centre, kept in the Lab until a partner wants to run it for real.
Stack and capabilities
Only what mattered
- Next.js
- Concept build