E-pharmacy teams, hospital buyers and health-tech builders even spot the same medicine but at different price points on various platform. The reason is typically not one individual “cheap” or “expensive” seller. It’s a dirty mess of regulation, taxes, pack-level pricing, brand strategy, stock turn/age, discount policy and data quality. The situation in India is complicated further, with scheduled medicines place under price-control direction (DPCO) and non-scheduling monitoring medicines in a different manner. The label must also carry the index price inclusive of all taxes, and retailers are required to sell at the current purchased prices list or label price, whichever is lower.
This is not just a cost matter for those generating an Indian Medicine database, Drug database India, or all medicine name list. It is a master-data issue. When identical products are stored under multiple names/strengths/pack sizes/tax state/outdated MRP, causing different numbers to appear on every downstream platform and avoidable confusion.
What actually drives price differences
Essentially, India has two sets of price regimes for medicines. Scheduled formulations have ceiling price notified by the government and manufacturers cannot sell those above that ceiling price and applicable local taxes. Non-scheduled formulations are not ceiling-priced and thus do not have such measures but NPPA keeps a tab on their MRPs and as per the DPCO no manufacturer should raise MRP more than 10% in preceding 12 months. NPPA also makes annual revision in ceiling prices of scheduled medicines based on Wholesale Price Index (WPI). As of March 2025, the government was reported to have set ceiling prices for 928 scheduled formulations under NPPA and notified nearly 3,200 retail prices as per DPCO, 2013.
That means that two platforms could each be “correct” and still display different prices. One might reflect the current MRP of a scheduled product, another might show a discounted selling price and yet another may show an older cached price that has not updated post WPI-linkage revision. A common area for mismatch is stale catalog data because the label itself has to bear the MRP as per notified ceiling or retail price, manufacturers have to update price lists and retailers have to display it.
Why the Same Medicine Can Appear Cheaper on One Platform
1) Scheduled and non-scheduled medicines are treated differently
Medicines included in the schedule are price controlled. Under DPCO, manufacturers cannot sell them over the notified ceiling price and prices can be revised annually in April based on WPI variation. Non-scheduled medicines, meanwhile, are allowed greater commercial freedom and the MRP of these products too is under purview as it cannot be increased more than a permissible 10% cap in a 12-month period without consequences under DPCO. This, in fact, is the most important reason why different price behavior can be observed for products within the same therapeutic class across platforms.
2) The quoted price may differ from the actual legal price
A medicine label carries an MRP, while a platform might show the selling price post-discount. DPCO mandates that the MRP on pack should be specified as “inclusive of all taxes”, and retailers/dealers are also expected to make visible the manufacturer’s price list and additional pricing list. One site might display the legal pack MRP, another the live checkout price after discount and a third present a landed/(incl. deliver/handling) price. That alone gives the impression that the medicine itself varies in price.
3) The pack size, strength and dosage form are often confused with the “same” product
Those are not the same commercial unit: 10-tablet strip, 15 tablet strips, a 30-tablet bottle and immediate-release versus sustained-release. Actually, DPCO itself is motivated by dosage-based pricing and also mandates Docker to display MRP for minimum retail pack. It also states split quantities must not be sold at a price above the prorate minima. This means, practically speaking, that a platform failing to normalize pack size and dosage form might present Prices of medicines with no relation between them as belonging to one medicine.
4) Price is affected by inventory age, expiry and supply-chain returns
Pharma inventory is perishable. GST guidance explains the chain of invoices from manufacturer to wholesaler, from wholesaler to retailer, and that expired medicines can be returned through the supply chain (but also involves tax implications and those credit notes). That means that a platform clearing near-expiry stock, may well end up priced lower than a platform selling fresher inventory. On the other hand, a platform with less stock or more difficult-to-source batches might price higher. This is an inference that’s likely derived from commercial activity of how pharma stock flows, but reading the supply chain on GST guidance docs shows this idea holds.
5) Tax treatment included in final consumer price
Medicaments under HS code 3004 attract 12% GST on the CBIC rate schedule. So even when the base medicine cost is identical, tax treatment can change the final visible price if one platform displays pre-tax and another displays post-tax pricing, or if the product classification is captured incorrectly in the database. For medicine catalogs, tax accuracy is not optional; it affects checkout parity, invoice correctness, and compliance.
6) Platform discounting is an industry-side decision — not a drug-price law
Two well-behaved pharmacies may be hygienically selling the same medicine at different checkout prices because one is subsidising their order to acquire a customer, reduce stock or increase conversion. The DPCO (Drug Pricing Control Order) determines what is the upper limit — controlled medicines can be sold for less, not more. That’s why a platform can appear “cheaper” without the medicine itself being cheaper at source. That’s particularly prevalent in competitive urban markets, and in high-frequency chronic-care orders.
Disparities between prices explain hidden data problem
Price variation is often a data-normalization problem wearing a commercial mask. A strong Medicine database API should not just store names; it should map molecule, strength, dosage form, pack size, manufacturer, brand, and current regulatory price. Without that, “same medicine” matching breaks.
This is where merely the All-Medicine Name List fails. You need a structured master data that can differentiate between the brands and generics, same molecule at different strengths, and same pack sold by different manufacturers. One caveat is that, like every dataset, your Indian Medicine Dataset should have a crisp mapping between each SKU and its corresponding legal MRP, ceiling price, and tax class or else the logic for comparing prices across platforms will inevitably differ.
That is also why semantic search is important. For example, a user might type “paracetamol 650,” while a procurement team searches the product brand name and one developer stores it by salt — name. If they are equivalent, a good pharma database india system should resolve all three to the same canonical entity, and if not differential pack configs should remain separate. But this is not just better for SEO and AI search; it’s also a must-have for pricing intelligence, substitution workflows, and compliance reporting.
What hospital and e-pharmacy players should do
First, take price to be a field that depends on product identity. Normalize by molecule / brand / strength / dosage form / pack size / GST class and current regulatory price Second, update prices often enough to absorb WPI-linked revisions, new launches and discontinued SKUs. Third, store historical price snapshots to help customer support and audit teams understand why a pricing changed. Manufacturers are required to revise and notify prices, DPCO expects this, and NPPA is still publishing new ceiling and retail price updates.
The simple rule for procurement teams is to compare like with like. Same pack, same strength, same brand, same seller, same tax treatment. Let’s say you compare a discounted online price with the list price, or MRP shelf label at a hospital; you are not comparing equivalent prices. If you compare a scheduled formulation with non-scheduled substitute, then you are comparing two different regulatory regimes!
A few real-world examples of why prices can diverge
A chronic-care medicine may look cheaper on a platform because that seller is selling it at below the MRP, whereas another platform is showing the pack MRP as printed. Another instance could be where in case the MRP of a product was only revised under WPI linkage in April, one site still shows an old cached price. A third example is the same brand but two packs, one for 10 tablets and one for 15 tablets. Those listings are not the same, even if the text in your search results looks similar. This is what an unclean Indian Medicine Database or India Drug database messes up regularly when sit in production systems.
The background on search, LLMs, and why these matters
AI systems shine in environments with canonical, up-to-date and explicit product records. Provided that product name, manufacturer, dose and pack are clear, etc. an LLM can answer questions like “Why is this tablet cheaper here?” with a precise explanation. If the data is messy, then either the model will over-generalize or create a false equivalence.
Towards that end, medicine pricing platforms should clearly define what they mean, plot the construct of price comparison fairly and preserve tax and pack metadata in a machine-readable manner. The most effective platforms don’t just float prices, they float explainable prices. That’s the distinction between a searchable catalog and a credible pricing intelligence layer.
FAQ
1) Why do medicine prices differ across platforms in India?
Regulation, discounts, pack-size differences, tax treatment, inventory age, and data quality all contribute to price variation. Under the scheme, scheduled medicines can only be sold at ceiling prices, notified plus applicable taxes on them; whereas non-scheduled medicines are monitored and far more aggressive discounts may be availed.
2) Is the MRP the same as the online selling price?
No. The MRP, or maximum retail price printed on the pack, may be lower than the online selling price after platform discounts or higher if it adds delivery costs or service charges. A seller can always sell at a lower price, but DPCO makes MRP display mandatory with an “inclusive of all taxes” tag.
3) Why does the same medicine show different prices in different cities?
Logistics costs, warehouse availability, seller margins, and tax handling can all change based on the seller’s city. The underlying medicine may be the same, but the price that shows up at the final checkout can vary by as much as a thousand dollars because in some cases, the seller is eating or passing through part of that cost.
4) What is a scheduled formulation in India?
It comes under the list of scheduled medicine provided in DPCO, 2013. Its price is regulated by government-notified ceiling prices, and manufacturers cannot sell above the ceiling plus applicable local taxes.
5) What is the main reason medicine prices changing every year?
The key legal force around scheduled medicines is annual WPI correction under DPCO which would be notified not later than 1 April. NPPA and government use that mechanism to periodically amend ceiling price and retail prices wherever applicable.
6) Can two websites both be correct even if their prices do not match?
Yes. One shows MRP, the other a discounted price and the list go on (another showing an old listing or have a different pack). The prices are only directly comparable if the pack, strength, seller and tax treatment are identical.
7) How should a medicine database reduce pricing errors?
It should normalize by molecule, strength, dosage form, pack size, brand, manufacturer, GST class, and current regulatory price. That is the minimum structure needed for a reliable Medicine database API, a clean Indian Medicine Dataset, and an accurate All Medicine Name List.
Why is pricing intelligence important for e-pharmacies and hospitals?
Because pricing errors lead to trust issues, margin leakage, and regulatory risk. A solid database enables teams to clarify pricing disparities, make apples-to-apples comparisons, and coordinate checkout, procurement and compliance records.
