Pharmacy and Dealer Loyalty Programs Built for Oman's Pharma Trade

Yes. Each audience runs as its own programme with separate KYC, earning rules, validation, payout method, and message templates. The admin portal keeps a pharmacy volume scheme, a dealer rebate scheme, a chain trade contribution, and an OTC consumer QR scheme fully isolated, so no policy or budget crosses between them.

Monthly purchase data from distributors and sub-distributors feeds into the loyalty engine straight from the DMS or ERP. The engine applies volume bands by brand and category, so a pharmacy in Muscat or a dealer covering the Batinah coast earns on genuine sell-in, not a manual claim. Tier upgrades apply automatically and the outlet sees the credit in the app the same day, with full history.

Chain pharmacies typically run on contractual trade contributions rather than volume bands, with triggers such as listing, shelf compliance, and joint-business-plan targets. The engine calculates the agreed amount and posts a credit note or accrual to the chain ledger in Omani rials for finance reconciliation, kept separate from the pharmacy and dealer volume flows.

OTC packs carry a unique QR code mapped to the manufacturer's batch and expiry record. Consumers scan through the consumer app to earn; pharmacy staff and dealers scan separately for their own trade entitlement. AI duplicate-scan and geo-validation checks block repeat or copied codes, and redemption routes to Maal, a card, or bank transfer, with separate KYC per entry type.

Outlets register with their trade licence and pharmacy registration details, an authorised contact, and a bank account or Maal card for payout. Once verified, approved rebates settle by bank transfer, Maal, or card in seconds. Higher payout thresholds route through an extra approval step before funds leave the programme float.

Every transaction logs a timestamp, source, audience, approver, payout method, and reference. Chain contributions carry the joint-business-plan reference, pharmacy and dealer points carry the DMS run ID, and OTC entries carry the QR code, batch reference, location, and validation status. Trails export on demand for finance review, and record-keeping is designed to align with Oman's Personal Data Protection Law (PDPL).

Brand sees active pharmacy and dealer counts, earning trends by governorate, and catalogue performance across Muscat, the Batinah coast, and Dhofar. Trade sees chain accruals, listing compliance, and OTC conversion. Finance follows payout liability and redemption ratio in OMR against budget. The 1Voice assistant answers plain-language questions on top of all of it.

Messages sequence by lifecycle: enrolment, first earning, approaching the next tier, and dormancy. Pharmacies and dealers see balance, batch-recall, and tier alerts; chain finance contacts see programme recaps; OTC consumers receive SMS and push updates. Opt-in, timing, and language (English or Arabic) are set per campaign to match Oman's business and official languages.

Yes, though it rarely needs to. Coverage across the Muscat-Sohar-Salalah corridor is reliable, and the scan and outlet apps still queue entries offline and sync automatically for the rare stretch of interior or desert route where signal thins out, so a rep working Nizwa, Duqm, or another remote wilayat never loses a scan.

A few weeks once volume bands, KYC, the catalogue, and the DMS feed are finalised. Configuration runs in the admin portal, bulk onboarding of outlets loads by spreadsheet, and Maal, card, and bank-transfer payout set-up adds a short window before the first payout cycle. No custom coding is needed to go live.