A patient walks into one branch of a pharmacy chain. They have been a customer at another branch for years. In the pharmacy's system, they appear as a new customer. Their allergy record does not follow them. Their prescription history is elsewhere.

In retail, fragmented data is an inconvenience. In healthcare, it creates risk.

The client, a US-based pharmacy chain operating across multiple locations but had no centralized database. Customer records existed independently in each branch, managed by on-premise systems that did not talk to each other. The same patient could appear as multiple distinct records across the network. Billing was slower. Support took longer. And the data the organization depended on for its operations could not be trusted.

‍

The organization's goal was a single source of truth for every customer across every location. That meant building something new, a central data platform that the branch systems would feed into, rather than trying to reconcile the existing records after the fact.

Technogise built the platform over 12 months. At its core was a customer matching algorithm, built from scratch, that assessed each incoming record against the existing database. When a new customer event arrived from a branch, the algorithm determined whether a new Customer ID should be created or the record should be merged with an existing profile. If a duplicate was detected, APIs prevented the creation of a second profile and handled the reconciliation automatically.

The branch systems were on-premise and not cloud-native. A full migration was not on the table. Technogise used webhooks to harvest data from these systems: each time a branch created or updated a customer, the system triggered a webhook that sent the data to the central platform for processing.

Events flowed into the platform, were analyzed against existing records, and either linked to a known Customer ID or used to create a new one. The flow was event-driven throughout the central platform did not need to poll the branch systems; it responded to changes as they happened.

The result was a customer data layer the pharmacy could actually build on marketing, support, and clinical workflows that depended on accurate, deduplicated data could finally function reliably across all locations.

An internal read-only web app gave support staff the ability to look up customer data quickly when resolving complaints. Previously, addressing a support query from a customer who had visited multiple locations required checking several disconnected systems. With the central platform, the answer was in one place.

HIPAA compliance was a design constraint throughout access was controlled, and real-time data logging recorded all actions within the app.