Work · Concept platform / Idealink Lab
Mall OS
One mall. One member. One measurable customer network.
What it is
Mall OS is customer, loyalty and intelligence infrastructure for shopping centres: a Mall ID that exists before any app install, mall-wide loyalty and benefits, a campaign engine, verification that starts before tenant systems are integrated, and an operator command centre.
Why it needed to exist
A visitor enters, shops and leaves without becoming part of a mall-owned relationship. Offers are published, but exposure, purchase and repeat visit are rarely connected; each tenant owns its own transaction context, and waiting for every POS or ERP to integrate delays value.
What Idealink did
Idealink designed the platform and built it as a working concept: the member journey from join to reward, and the operator view where the same verified event shows up as intelligence. It is a Lab concept prepared for a pilot, 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
Shopping centres have footfall; the customer relationship is still fragmented. The gap is not another app. It is the missing layer that connects identity, engagement and verified behaviour across participating tenants — Mall OS is that layer, built as a working concept.
Six modules above tenant systems: Mall ID, loyalty, benefits, campaigns, verification and intelligence. Every verified interaction strengthens the same member profile.
02
One journey, not separate tools
The member sees a simple loop. The operator sees identity, attribution and return behaviour behind it.
01 → 02
Join
Phone and a one-time code, or a QR: a mall-owned member exists before any app install.
02 → 03
Activate
A relevant campaign, chosen by tier, recency, category behaviour or tenant affinity.
03 → 04
Shop
At a participating tenant, with nothing changed at the till.
04 → 05
Verify
Receipt, QR or API: the purchase becomes a verified member signal.
05 → 06
Earn
Points or a reward from a ledger that records every earn, burn, refund and expiry.
06 → 07
Measure
Activation → verified buyer → repeat visit, attributed to the campaign that caused it.
07 → 01
Return
The next best action for the member, the tenant and the operator.
03
Focused by design
Mall OS does not ask a shopping centre to replace its systems first. It owns the customer layer and connects to commerce infrastructure where it exists.
- Mall OS owns
- Mall ID and member identity · points, tiers, rewards and benefits · audience campaigns · receipt, QR and staff verification · customer 360 and operator intelligence
- Connects to
- Tenant POS, ERP and payment systems · ordering and commerce platforms · cinema, reservation and service systems · wayfinding and physical touchpoints · external reward providers
- Why the boundary
- A complementary layer to broader mall-commerce platforms, not a forced replacement.
04
Verification before integration
The pilot does not wait for the hardest integration, and every signal states how it was verified: by receipt, staff, merchant or POS.
Level 0 · Launch
Zero integration: receipt upload, member QR, tenant QR and staff verification.
Level 1 · Enrich
Lightweight connections: API, webhook, CSV or SFTP, or an e-commerce plugin.
Level 2 · Scale
Deep integration: POS, ERP, payment provider and real-time event feeds.
05
One network, three sides
The platform only holds if the operator, the tenants and the members all have a reason to take part.
- Operators own the customer relationship: a known member network, campaign-attributed behaviour, repeat-visit intelligence and a portfolio-ready data layer.
- Tenants turn mall traffic into measurable demand — new customers, targeted reactivation, campaign performance — without replacing their POS or receiving raw cross-mall personal data.
- Members get one mall identity, points and rewards, personalised offers and experiences worth returning for.
Discount is not the product. The product is a relationship that gives the member a reason to identify, engage and return.
07
A 90-day pilot
Designed to validate member acquisition, tenant participation, verified transactions and campaign attribution — not to rebuild the mall.
- Scope
- Member join and consent, points and simple tiers, campaigns, receipt and QR verification, tenant participation, a command centre
- Indicative shape
- 15–25 tenants · 10–25K member capacity · 20+ campaigns or offers · weekly KPI review
- Targets
- Calibrated with the operator once real footfall, tenant and campaign inputs are available.
08
The plan
Wave 1
Foundation and closed pilot
Mall ID and consent, points and rewards, receipt and QR verification, the command centre, pilot tenant onboarding.
Wave 2
Engagement and tenant expansion
Segments and campaigns, challenges and tiers, tenant self-service, CRM activation, advanced campaign reporting.
Wave 3
Deeper integration and scale
POS and API event feeds, portfolio dashboards, external benefit providers, advanced intelligence, more mall touchpoints.
Outcome
Where it stands
A working concept of the whole golden path — join, campaign, verified purchase, points, operator intelligence — ready to run as a 90-day pilot with a shopping-centre operator. It stays in the Lab until one does.
Stack and capabilities
Only what mattered
- Next.js
- Concept build