Eight concepts, one ledger
The expansion research produced eight merchant-facing ideas. The blueprint collapsed them — because they were never eight apps; they were one merchant ledger wearing six hats and bridging six ways.
A ledger, not a tab collection
The one truth
Sales, stock, credit and expenses live in exactly one place — the AnBuku ledger. Every other surface reads and posts to it; none keeps a competing copy.
Merchant-owned
Export, encryption and deletion belong to the owner. The ledger leaves the vault only as k-anonymized cohort numbers, on the merchant's opt-in.
Records, never custody
Money moves through licensed DuitNow/acquirer rails. AnKedai's job is the audit trail the notebook never gave the owner — and LHDN now asks for.
Where AnKedai plugs into the portfolio
The merchant superapp only exists because these bridges do: acceptance, demand, supply, index, markets and protection — each one already designed on its home ledger.
Masrif — every kedai an acceptance point
The QR on AnKedai's counter is the same DuitNow-grade rail as the flagship wallet. Merchant adoption puts Masrif where the big terminals never priced in — the kedai runcit — and every top-up has somewhere to be spent.
Pilot B of the blueprint: the ledger seeds the wallet network.
i-Saves — the supply side of savings
Segment discounts need merchants willing to fund them for a verified crowd. AnKedai is where a kedai opts into a staff week or a students' hour — campaign setup in the same console as the bookkeeping, billed on conversion.
Discount supply without a field-sales army.
AnKantin — canteens as first tenants
The school canteen auntie runs her stall, queue and parent top-ups through AnKedai. Pilot A's deployment recruits the surrounding kedai cluster at zero marketing cost — one school, one merchant cluster, three bridges proven.
Blueprint Pilot B, adjacent to Pilot A.
AnHarga — price reports, aggregated
AnKedai receipts feed KPDN's price index as floored, consented cohort numbers — the densest price ground-truth network in the country, built as a by-product of merchants keeping their own books. Nothing individual ever crosses.
The supply side of a ministry data product.
AnPerisai — protection that attaches, not competes
Gig and staff coverage rides the ledger's real income history, syndicated through PERKESO's existing gig schemes rather than a parallel insurance product. The payroll record is the underwriting.
Partner posture, per the ministry doctrine.
AnKampung & Warga — the community roster
Trusted-neighbour hiring and resident service directories were never separate apps: they are AnKedai's staff module meeting AnKampung's resident graph.
Concepts 34 → 0 standalone, this is where many landed.
AnPasar — the council's market desk
Pasar awam and pasar malam lots are public land with private chaos: waiting lists run on paper, lot transfers happen in car parks, rent collection is an envelope. AnPasar gives the council a ledger — registered operators (the same AnKedai books), ballot rounds anyone can audit, and a vendor app that is simply AnKedai in mobile mode. The dashboards the PB gets for free are the same floored cohort numbers the merchants opted into.
One vendor ledger, N councils, zero new apps for the peniaga.
Built on the Antrex spine
One ledger engine
AnKedai runs on the same event-sourced ledger spine as Masrif's dana wallet and AnTeraju's mastery record — an Antrex primitive, not a bespoke rebuild.
Offline state engine
Inherited from AnKampung's gatehouse: post offline, resolve on reconnect, states only along legal transitions. A pasar malam under a shed is the reference environment.
Aggregate by exception
Anything that looks like data monetisation must pass the floor test: cohorts of thousands, differential noise, merchant opt-in — or it does not ship.
The free ledger is the wedge; the bridges are the network. See where the demand side lives.
Ready to build something intelligent?
Let's engineer your next product — from idea to launch.