Monthly comparison across the three brands, sales channels, bricks, and top customers — built from the July, August and September 2026 sales files. Use the selector above to switch between July, August, September (full month, with targets), or the combined Jul–Sep total. October 1–18 (month-to-date, Distributors only, no targets) is available as its own period.
Target Achievement
—
Total Sales
—
Target
—
Weakest Brand
—
TREND ALERT — JUL → AUG
ZINOL sales collapsed from EGP 311K in July to EGP 124K in August, despite beating its target in July (106.6%). This single drop drives most of the overall gap to target, and it fully flows through to the Distributors channel, where this brand sells exclusively. September update: the same Al-Araby Medical Center 5,000-unit order repeated — ZINOL 1G shows 7,013 whole units for the month, but only 2,013 without it (vs 1,577 in August). ZINOL value in September: EGP 312K, 95.0% of its target.
-60%
Month-over-month
-64.8%
Zinol 1G at distributors
October (1–18) — month-to-date, read before comparing: the 18-Oct file is a distributor-to-customer transactions file: it has no targets (so no achievement %) and no Stores channel. Value = units × distributor list price: EGP 516,408 vs EGP 794,709 for the whole of September (Distributors only). The pace shown is Oct 1–18 scaled to 31 days vs September Distributors (+12% overall). ZINOL includes a 7,500-unit order from Al-Araby Medical Center (EGP 254,306) — without it ZINOL would be far lower, so read ZINOL pace with care.
September 2026 — complete month (1–30), with targets. Achievement = value ÷ target, both on the file's moving-price basis: EGP 1,867,404 vs EGP 2,023,140 = 92.3%. Stores delivered EGP 1,072,695 (116% of its target) while Distributors reached EGP 794,709 (72%). ZINOL includes the one-off 5,000-unit Al-Araby hospital order (EGP 169,538); without it ZINOL would be about EGP 142,510 (43% of target).
Performance by Brand
Actual vs. target value, and achievement rate
Channel & Brick
Jul→Aug: Stores stayed relatively stable while Distributors and BRICK2 were hit by the ZINOL slowdown. September: Stores rose to EGP 1.07M (+35% vs Aug) and Distributors recovered to EGP 795K (+22%) helped by the repeated Al-Araby ZINOL order; BRICK2 is up +39%.
By Sales Type
By Brick
SKU Trend — Units, Value & Achievement %, Jul · Aug · Sep · Oct* (all 7 SKUs)
Line trend per SKU (each panel has its own scale, so small packs stay readable; every point carries its number). Switch between whole-unit sales (all channels) and EGP value (Distributors channel). CLAVIMOX 1G is included; Jul/Aug values now come straight from the July–August file (Distributors channel). Sep is the complete month (Jul, Aug and Sep are all full months, so the % changes are like-for-like). Jul/Aug/Sep values come straight from the company files (Distributors channel). Oct* = 1–18 October from the 18-Oct export (Distributors only; value = units × list price) — by default scaled to a 31-day pace, and the 7,500-unit Al-Araby order is kept as is, not scaled (untick the box to see the raw 1–18 numbers). Click 🎯 Achievement % to see actual ÷ target per brand across Jul–Sep, with September split by SKU (October has no target).
Action Plan by Product
Reads from the merged chart above: Jul→Aug change, the Aug→Sep change (September is a complete month) and the Oct* pace (1–18 October scaled to 31 days vs September). CLAVIMOX 1G has its own action plan below.
CLAVIMOX deep-dive — 1G & 625
Choose the product, the period and any set of pharmacies; every table below recalculates. The pharmacy selection is shared with the Customers section. Click any row, any survival cell, or a month header marked ▸ to open the pharmacies behind it (then click a pharmacy for its full history). Each block ends with a decision, and each table has a CSV button. 625 and the cross-sell tables use Jul–Oct 2026 data, so they are already 2026-only.
Product
Period
Pharmacies
Customers Explorer — pharmacies & hospitals, one table, five lenses
One row per customer (same-name branches are combined, all their addresses are listed). The filters below apply to every lens: search (name or address), type, brick and sub-brick. Switch lens to see the same customers by product, by month, year-over-year, retention or Pareto — nothing is repeated in a second table.
Units by SKU and month for pharmacies and hospitals together (use the Type filter to split them). Oct* = 1–18 October (partial). Click a column to sort; choose which SKUs to show.
CLAVIMOX 1G, Distributors channel, whole-unit transactions — every month Jan25–Oct26*. Pick months below (one month = the old "customers by month" list). Oct26* = 1–18 October only.
Pharmacy-level comparison
Methodology note: July 2025 is missing from the source file entirely, so July is excluded from both years. All charts and the table below use the same 8 months in both years (Jan–Jun + Aug + Sep). September 2026 is now the complete month, like-for-like with the full Sep 2025: the total is -37.7% (41,322 → 25,764 units). Pharmacies with the same name are combined into one row (as in the monthly series). September adds 13 pharmacies that were not in the earlier list, and some pharmacies that were "New" or "Lost" are now "Retained" because of the extra September days. October (1–18) is not part of this pharmacy-level section — partial-month units against a full Oct 2025 would distort the Retained / Lost / New split — but it appears in the monthly chart above and in the Retention & Pareto tools. The three charts below are live: they recompute from whatever subset the search box, status chips, and brick/locality filters currently select underneath.
Pharmacy movement
By brick
By locality (sub-brick) — all 55 localities, grouped by brick
Pharmacy-level detail — every pharmacy, with address
1 · Retention — compare two periods (who is lost, who declines, who stays)
Click a month to cycle: A (base period) → B (comparison period) → off.
2 · Pareto — who drives the volume by Brick, Sub-brick and pharmacy
Territory Map — Villages & Pharmacies
Every village / area of MENOFIA III with its pharmacies. Switch between Google Maps (needs your API key) and the free Street map (street names; layer switcher at the top-right of the map). Big circles = villages (size = number of customers); small dots = pharmacies (size = units in the chosen period). Click a village to list its pharmacies, or a dot for its details.
Street map (free)Google Maps (API key)
Paste your Google Maps API key to use Google Maps. It is saved only in this browser.
The key needs Maps JavaScript API and Geocoding API enabled in Google Cloud, with billing on. A key restricted to a website will not work from a local file.
Dot colour: green = bought in the last two months of data · red = bought before but not in the last two months · grey = no purchase in the selected period. The source data has village and street text but no GPS, so pharmacy dots are grouped by address text inside their village (pharmacies with the same street / hamlet in the address sit together). Press Locate pharmacy addresses to place them from the address by geocoding where it is specific enough — positions are best-effort, not surveyed. To correct a pharmacy yourself, click its dot → Set / move this pharmacy → click its real place on the map (marked with a white ring). Manual positions always win over automatic ones. They are saved in this browser, but Safari can erase saved data after a few days without use — so press Export my locations to keep a backup file (and Import locations to restore it), or paste its contents into PHARMACY_COORDS in the script to make them part of the file for good. Village centres are found automatically and saved in this browser; faint village circles = not found, shown at the area centre. To fix one, edit VILLAGE_COORDS in the script below. To open Google Maps directly with no key box, put your key in GOOGLE_MAPS_KEY.
Tablets Market — Units & Market Share Dynamics
CLAVIMOX 1GM MKT only (tablets, IMS territory data) — MENOFIA III, Aug 2024–Aug 2026 (IQVIA, Territorial Dynamics file; “Other” includes CURAM and the rest of the market)
Competitive alert: MEGAMOX 1GM held a stable 7–17% share for 22 months, then jumped to 44.1% in Jun-2026 (+31.2 pts in a single month) and 48.5% in Jul-2026 — directly coinciding with CLAVIMOX's share falling to its lowest point (6.5%). In Aug-2026 MEGAMOX eased to 43.0% (-5.5 pts) and CLAVIMOX recovered to 9.1% (+2.6 pts, 3,570 units) — a first step back, but MEGAMOX is still far above its earlier 7–17% range. Toggle to "MS Gain" to see the swing clearly.
Injectables Market — Cefotaxime: Units & Market Share Dynamics
CEFORAN MKT (cefotaxime vials, IQVIA territory data) — MENOFIA III, Sep 2024–Aug 2026 (Territorial Dynamics file). “Others” = all other cefotaxime brands. Use the brand icons to switch brands on and off.
Customer & Sales Trend — Full History
CLAVIMOX 1G units and unique customer count, MENOFEYA III, Jan 2025 – Sep 2026 (Jul 2025 missing from source, omitted below). Sep26 is complete; Oct26* (1–18 October) is a partial month — it is shown faded, and kept out of the trend fit and anomaly flags.
Jul26 & Aug26 customer-level data comes directly from the Q3 company file and Sep26 from the complete September file (same CLAVIMOX 1G item, Distributors channel, whole-unit transactions), and Oct26* (1–18) from the 18-Oct export — these are used throughout the tables below.
Action plan for CLAVIMOX 1G: +36.5% Jul→Aug, then 3,273 units in September (−5.8% vs August, +28% vs July; CLAVIMOX brand at 91.5% of its September target). Keep distributor stock coverage ahead of demand and consider extending trade incentives to widen the customer base further — the 20-month view above shows this needs sustained reach, not just a one-month push; September reached 301 active customers vs 313 in August.
CLAVIMOX 1GM Allocation Trend
Source: company-wide Clavimox Allocation file, filtered to MENOFEYA III's three bricks — quantity only, no target in this source
Cross-check passed: this independent district-level file gives Jul = 2,546 units and Aug = 3,476 units for CLAVIMOX 1G across MENOFEYA III's three bricks combined — matching our own bottoms-up distributor calculation (2,546 / 3,475) to within rounding. Our internal numbers check out. September (complete month: 3,273 units — BRICK1 980, BRICK2 1,651, BRICK3 642) comes from our own whole-unit calculation on the full September file, because the district file does not cover September yet.
October (1–18, partial, shown faded with *): 1,035 units so far (BRICK1 490, BRICK2 491, BRICK3 54) — about 2,917 at a 31-day pace vs 3,273 in September (−10.9%). Like September, it comes from our own whole-unit calculation (the 18-Oct export), not from the district file, and it is not part of the trend lines below.
Fitting a linear trend line across all 9 months (Jan–Sep, same method as before — slope ÷ average level) gives BRICK1 -5.17%/mo, BRICK2 -3.88%/mo, BRICK3 -2.71%/mo and MENOFEYA III combined -4.11%/mo. On the earlier Jan–Aug window the rates were -5.16 / -5.56 / -3.71 and -5.08%/mo: September (3,273 units, above the Jan–Aug trend line) softened the picture, most of all in BRICK2. The office-wide (district) benchmark is -4.68%/mo, but it still covers Jan–Aug only (there is no office-level September file), so for a like-for-like read compare it with the Jan–Aug rates: on that basis BRICK3 declined slower than the office while BRICK2 was the fastest-declining piece. On the Jan–Sep window BRICK1 is now the fastest-declining brick. See "Growth Trend vs Office" for the side-by-side comparison, and "Share of Office %" for the office total and your exact share, month by month (September shows N/A — no office total yet).
YoY Analysis — Jan–Sep, 2025 vs 2026
Monthly view first, then the pharmacy-level comparison (hospitals excluded) — CLAVIMOX 1G, Distributors channel, 2025 vs 2026.
How the totals below reconcile: with no filter applied, the same 8 months give -32.1% for all customers (43,077 → 29,262), -37.7% excluding hospitals (41,322 → 25,764; hospitals went 1,755 → 3,498), and the pharmacy-level comparison in the Customers Explorer (Year over year lens) now shows the same -37.7% (41,322 → 25,764). The pharmacy-level dataset was rebuilt from the monthly series for this update: the previous stored version had a 2026 total about 3,100 units too low because it did not include August 2026, which is why it could not be reconciled before.
Anomaly Detection — Statistical Deviations
CLAVIMOX 1G units, 20 complete months (Jan25–Sep26); Oct26* is 1–18 October only, so it is shown faded and kept out of the fit. Method: fit a linear trend, compute the residual (actual − trend) for every month, flag months where |residual| exceeds 1.5× the standard deviation of all residuals.
Step 1 — Trend: linear fit gives slope -139.5 units/month (intercept 5,833.2). This is the same regression approach used for the brick-level trend earlier in this dashboard, chosen because it uses every data point rather than picking two arbitrary windows.
Step 2 — Dispersion: residual standard deviation across all 20 months = 1,678 units. Threshold set at 1.5σ (≈ 2,517 units) — a common, moderately strict cut that flags genuinely unusual months without over-flagging normal noise.
Step 3 — Flag: 3 of the 20 months exceed the threshold (shown in red/gold below). Every other month, including the widely-discussed Jun26 MEGAMOX competitive surge (z = -0.05) and now the complete Sep26 (3,273 units, z = +0.05), falls inside normal statistical variation for our own unit volume — see the note underneath the chart for what that means. With September complete, all 20 complete months are used in the trend fit and the flagging; Oct26* (1–18) is displayed but excluded.
Why the MEGAMOX shift doesn't show up here: the IQVIA/market-share data (Tablets Market section above) shows MEGAMOX jumping from ~10% to 44–49% share in Jun–Aug26 (44.1%, 48.5%, 43.0%) — a huge move. But our own CLAVIMOX unit series that month (3,516 units, z = -0.05) sat almost exactly on its existing downward trend line. That means the competitive loss didn't arrive as a sudden drop we'd notice by watching our own numbers — it was absorbed into a decline that was already happening anyway, from a shrinking base. This is exactly the kind of erosion internal anomaly detection alone will miss; it only becomes visible by cross-checking against the external competitor (IQVIA) data.
Forecast — CLAVIMOX 1G units
Method, training window and range are chosen by backtesting on this series (details at the bottom). Change the horizon, method or start; then use the what-if panel to see how pharmacy and order levers move the plan.
What-if scenario
Win back lapsed pharmacies
Active pharmacies
Change in the number of pharmacies buying in a month.
Units per pharmacy
Order size, e.g. from a bonus or a promotion.
One-off order
Hospital or tender order in
How reliable is this forecast? (backtest and assumptions)
🔮 What-If Scenario Planner & Decision Support
Built with React + Recharts, isolated from the rest of this dashboard. Projects CLAVIMOX 1G units 6 months forward from Sep26.
Assumptions, stated up front: 1. Starting point is the last actual month (Sep26 = 3,273 units) — not a smoothed average, so it inherits whatever noise that single month had.
2. The "Base" line extends the same linear-regression trend used earlier in this dashboard (−4.11%/month, fitted on Jan–Sep) forward unchanged — it assumes nothing new happens, good or bad.
3. "Pessimistic" and "Optimistic" apply a symmetric shock (5–15%, your choice on the slider) to that monthly rate itself, not to the unit total directly — a 15% shock on a -4.11%/mo base gives roughly -4.73%/mo (pessimistic) or -3.49%/mo (optimistic), compounded month over month.
4. This is a straight-line extrapolation of one brand's own historical pattern. It does not model the MEGAMOX competitive dynamic, seasonal effects (e.g. the Sep25 back-to-school bump), or any planned commercial action — those would shift these lines independently of the slider below, in either direction.
Decision-support framing: the gap between the Pessimistic and Optimistic lines at any future month is a rough envelope of "how wrong the base trend could reasonably be" if nothing changes — not a confidence interval in the statistical sense. Use it to size the risk of inaction, not as a precise forecast.
Loading interactive scenario tool… (requires internet access to load React/Recharts from CDN)