Partner Pharmacy Platform.

The team built the procurement, inventory, retail and digital-commerce foundation for an undisclosed venture-backed pharmacy network. The platform connected central supply operations with partner-store execution and an online-to-offline care and fulfillment journey.

The network expanded to 3,600 partner pharmacy sites, more than 10,000 SKUs and over 100 pharmaceutical brands across 45 provinces. Reported GMV grew at 140% CAGR over three years, while reported inventory days fell to 12. These are company-level operating results supported by the platform.

The mandate was to coordinate a growing pharmacy network without treating purchasing, store operations, customer demand and fulfillment as separate businesses. The platform needed to support a broad catalog, distributed retail execution and a consistent connection between suppliers, pharmacies and consumers.

The work connected the following capabilities:

• Central procurement and inventory. Procurement, ERP and inventory functions supported the network supply model, linking central operations to partner-pharmacy purchasing and a catalog exceeding 10,000 SKUs.
• Tools for the pharmacy counter. Partner pharmacies used connected POS, ERP and procurement capabilities, bringing store-level activity into the broader operating model.
• Connected enterprise and custom applications. Odoo formed part of the enterprise platform alongside custom applications built with React, Kotlin, .NET and Java on AWS.
• Brand education inside the partner experience. A learning management system enabled pharmaceutical brands to deliver education to pharmacists, adding professional learning to the partner platform.
• Digital care linked to distributed fulfillment. Consumers could shop online and move from virtual consultation to prescription and local fulfillment. Pharmaceutical relationships included Sanofi, AstraZeneca, Bayer, Boehringer Ingelheim, Merck/MSD and Johnson & Johnson, with Zuellig Pharma and DKSH as anchor distributors.
• Governance and control. The care-to-dispensing journey coordinated licensed medical practitioners and pharmacists, with partner education complementing retail and procurement tools.

The reported technology and integration scope was:

• Web application framework: React
• Mobile application language: Kotlin
• Application services: .NET, Java
• ERP platform: Odoo
• Cloud infrastructure: AWS

Odoo uses Python and PostgreSQL internally. These platform dependencies are distinct from the separately supplied custom application technologies.

They are reported project figures and describe selected experience of the team behind AIGard.

The case study separates delivered scope and reported scale from measured outcomes. Technology and company references describe the work; they do not imply endorsement or a direct AIGard client relationship.

Relevant to franchise and distributed-retail businesses that need central coordination without losing local execution. The experience combines enterprise software, custom commerce, partner enablement and fulfillment across a large operating footprint.

Yes. The same disciplines are available through staff augmentation, dedicated teams or software outsourcing.

Tell us what you are building, and on a 30-minute call we will recommend an engagement model, a team shape and first milestones.

NDAs are signed before any access is given, and engineers work inside your environment under least-privilege access, with permissions limited to their responsibilities.

Access is reviewed as roles change and removed when work ends. Our practices align with ISO 27001, SOC 2, GDPR and HIPAA, with PII masking, encryption and audit logging built into data work. We review your access policies, data-handling needs and vendor requirements during scoping.

Engineers typically start within two to four weeks of the scoping call. The exact date depends on the roles, seniority and number of people required.

We confirm a realistic start date in writing before you commit, and you meet the proposed engineers before work begins.