A pharmacy loses money in two places that Dynamics 365 Business Central does not watch on its own: the batch that quietly reaches its expiry date on the shelf, and the supplier scheme whose bonus quantity never reaches the cost of the goods you actually sold. Business Central ships genuine item tracking — lot numbers, expiration dates, item tracking lines, and expiration-date checks on posting — but it stops at the level of a distributor. There is no first-expiry-first-out suggestion when a counter assistant scans a strip, no near-expiry worksheet that proposes returns to the supplier while the credit window is still open, no representation of a "buy 10 get 1 free" scheme in the costing chain, and no concept of a schedule-wise sale register that a drug inspector will ask for. Counter staff also cannot work at the pace a queue demands on a standard Sales Order page, which is built for a keyboard-patient back office, not a Saturday evening rush.

Pharmacy Retail Management is an AL extension that ECOSIRE builds for your Business Central tenant to close exactly those gaps. Batch and expiry control is layered on top of native item tracking rather than replacing it: table extensions on Item, Item Ledger Entry and Tracking Specification carry the pharmacy attributes (schedule class, pack size, strip conversion, supplier batch reference), while an event subscriber on the item tracking assist-edit proposes the correct lot by earliest expiry and refuses lots already past their date or inside a configurable quarantine window. A dedicated counter page — a single-screen card with barcode entry, running total, substitution lookup and a keyboard-first layout — posts through the standard sales posting codeunits, so your general ledger, VAT and inventory valuation stay exactly where Microsoft put them. Nothing about the posting routine is forked.

On the purchase side, a scheme table extension records bonus quantity, slab discounts and free-goods lines against purchase lines, and a costing codeunit distributes that value across the received batch so the unit cost you see is the cost you actually paid. A margin-by-batch page then reports realised margin per lot, per supplier and per schedule category, drawing on posted value entries rather than a parallel set of numbers. A job queue entry runs nightly to rebuild near-expiry buckets you define (for example 90, 60 and 30 days), writes a Near-Expiry Worksheet with proposed supplier return lines, and can send the summary through Power Automate. Regulatory registers are defined as configurable register templates over posted ledger entries, exported to Excel or read externally through API pages published on REST API v2.0 and OData v4, which also makes the data available to Power BI and Dataverse without a separate integration project.

This is a build-to-order product, not an existing Microsoft AppSource download. Nothing installs until you request a quotation and we agree the scope. We start with a short scoping call to confirm your Business Central version and deployment (SaaS or on-premises), your counter workflow, your supplier scheme types, and which registers your regulator actually requires — because a register that is correct in one jurisdiction is worthless in another. We then build the extension against your version, install it to your sandbox for UAT with your own item and batch data, and only move to production once you sign off. Typical delivery is two to four weeks from confirmed scope, and you receive the full AL source in your own git repository at handover.