Rosetta Stone
How it works

One forecast. Then staff, buy, and plan from it.

Rosetta Stone turns weekly fills into a customer-and-product forecast, then uses that same plan on the other screens.

The idea

What this is

It replaces the spreadsheet budget model. Pharmacy fills refresh in the background; people add judgment on top. Staffing, buying, and the money screens all read the same plan. Hover a short label for a one-line hint; click the circled i for a longer definition.

Start at Customers

Open the list, then click a name. The weekly grid is history next to the forecast — that is the number everything else is built from.

Quick start

Four steps from sign-in to a plan

Most people only need the first three. Planners take the fourth.

  1. Sign in

    Use your OptioRx Microsoft account. Your role decides what you can change. The modules granted to you decide which screens you see.

  2. Start at Customers

    When Forecasting is granted, this is the first screen: who we fill for and how recent volume looks across the four pharmacies.

  3. Open a customer

    The weekly grid shows past fills next to the forecast. That is the plan everything else reads.

  4. Adjust, if you plan

    Change specific weeks, or try a scenario first. Promote it only when you want it to become the official plan.

The portal

What each screen is for

One sentence each. Click through when you are ready to use it.

Customers

Who we fill for. Click a name to review history and plan the forecast. Planners also get Customer groups (forecast bucket + why) and Price lists tabs.

Vials by OP

Forecast vials and revenue at each bucket's price per pharmacy and product for chosen customer buckets, with coming products flagged. Export a CSV.

Products

The catalog from April's formulary workbook, landed nightly. Ops tags how each product is made so staffing and buying stay complete. Data health lists what the workbook could not settle.

Production

What each pharmacy has to make each week; the Schedule tab sets planned batches against the site's ceiling, the Daily tab shows what it made by OP by day, and Plan vs actual marks the days it missed.

Scenarios

Try a plan without changing the official one. Promote it when you are ready.

Labor

People the plan needs, compared with who is actually employed.

Purchasing

Ingredients the current plan implies, by pharmacy, and on the Cycle tab each raw item's on hand, weekly draw, par, the week it needs reordering and, with a lead time set, the week to order by, with each OP's batch kit, which Purchasing maps from the kit OPs in Pioneer.

Inventory

Raw-material lots drawn first-expiring-first-out at actual prices, each batch's measured mixing waste and unit cost, finished goods by batch within BUD, a Pioneer AL shelf compare against JP's batch-level count, cycle counts that a counter enters and Purchasing approves, transfers between pharmacies, and an audit of every change. The Expiry tab is the daily pull list: finished goods past BUD that still hold stock, lots expiring within 30 days, and expired raw lots that still have quantity. Each list downloads as a CSV, most vials or quantity first. Overview Data health counts completed transactions (Pioneer Completed Date set) with no lot on them. Per site it shows yesterday's count and share against that site's own 14-day median, and marks 2 Nov 2026, when Pioneer stopped auto-assigning the lot at data entry. The 27 Oct 99.9% figure is context in the help text. A night alerts when yesterday is more than twice that median and more than 5 points above it, on a day with at least 200 completed fills. Yesterday's no-lot transactions split by alternate id into kits, compounded, and OTC. When OTC is the largest, the row lists its five most common alternate ids. It also shows the nightly's step times against the 27 Oct total of 58 minutes and flags a figure above 1.5 times its baseline. Two more lists sit there: ingredients with no Pioneer price and their October draw quantity, and items whose lots are past on-hand with the amount past.

Inventory report

One row per site per day from the two movement ledgers: on-hand, raw material drawn into batches, vials dispensed, destroyed, wasted, and expired, and the day's net change. Download the rows, or the movements behind one cell. Nothing is posted to Sage. The journal stays on its own screen.

Leadership digest

Last week per site, then a total. A site without batch tracking says so instead of made. Tracked sites show vials dispensed with no batch, and the share of fills reaching Print with no lot. SBH raw materials on the stock line is the Overview snapshot's raw total. Finished vials and waste come from the Inventory report. Pharmacy payroll per vial excludes corporate and names the latest paid week. Ledger vials against Pioneer fills, eight Sunday weeks. Compounded is the formulary: on the book, not purchased, and not dosage form Kit. A site whose finished-goods config is off is left out. A Sunday week with no Pioneer rows is left out. A dispense gap names the Rosetta team. When Chain is more than 50% above actual, or more than 33% below, the line says so. Three Data-health lines name who fixes them. A prior figure that moved more than 2% is restated.

Revenue / Margin

What the plan is worth at the price in force — including a narrower family tier when one applies — and whether it honours a typed or uploaded volume deal.

Receivables

What clinics have been billed and what has been collected.

Accuracy

Where the forecast is running high or low, so you know who to review. A weekly history keeps the company score at 4, 13, and 26 weeks, and the chart shows the last 12 weeks of bias for the horizon you select.

Admin

Data refresh and settings. Finished-goods settings for each site are stored here and are not read by the nightly yet. Most people only need to look here.

Purchasing review

The open price and count questions for John Rick, by site: cost review, suspect counts, units that differ, missing prices, and formulas on a dead record, from the 13:00 Overview snapshot. A row is answered when the corrections table holds an answer for that item or its NDC. Download it as the Monday sheet. Answers are entered on the corrections table, not here.

Users & access

Grant portal access from the MS365 directory, choose which modules they can open, and change roles. Only optiorx.com accounts can be granted; tenant guests are not listed.

Access

Who can change what

Viewer

Read the modules granted to you. You cannot change the forecast. An empty grant opens no business screen. Codex and How it Works stay available.

Planner

Change the forecast, routing splits, and scenarios. Set a bucket's weekly total on Vials by OP and it is split across the bucket's customers. Enter the batches each pharmacy plans per OP per week on the Production schedule.

Ops Admin

Keep products, headcount, labor standards, clinic name mappings, contract volumes, and each pharmacy's batch ceiling current — type them on the screen or upload a CSV. Grant Viewer or Planner, and which modules they can open. An Ops Admin has every module.

System Admin

Refresh the data, tune the model, and grant Ops Admin and Inventory admin access. A System Admin tests the Sage connection and sets whether production posting is on. A System Admin has every module. Seeded from configuration.

Inventory viewer

Read inventory in the pharmacies you are given. Inventory roles sit on top of the portal role and can be limited to named sites.

Pharmacy counter

Start and enter cycle counts, and discard a draft you started before it is submitted (nothing posts; the count id stays on record). Each line shows its cost and variance $; the count summary and monthly dollar totals stay hidden. Anyone holding this role sees no pharmacy until one is ticked, whatever other role they hold.

Receiving & approvals

Usually the Purchasing team. Record receipts and transfers, approve or reject a submitted count, discard a draft you started, override a lot's expiry, confirm a pull at BUD or the disposal of an expired lot, record test vials, and set an item's par weeks and supplier lead time and map each OP to its batch kit on the purchasing cycle. On Admin, maintain the corrections table: an item row for a per-unit cost or a substituted dollar, a unit alias when a record should join its family under another unit, an item-family join when the normalised name missed a record, and a batch row for a made count or fills printed on the wrong lot. On Admin, also keep the packaging bill (component, inventory item, quantity per vial, and a fallback unit cost). Batch close draws that bill into the vial cost; an OP with no row shows packaging not configured, not zero. This is an inventory role; the Purchasing screen is a module.

Inventory finance

See every inventory dollar and record a batch's test-vial count. Failed visual inspection stays on Bo's sheet.

Inventory admin

Everything Receiving & approvals does, plus overriding a batch's BUD, resuming a count whose approval stopped part-way, and discarding anyone's draft count. Granted only by a System Admin.

Reference

A few common questions

Where do the numbers come from?

Weekly fills from the pharmacies refresh in the background. Planners add judgment on top — a week-by-week change, or a scenario they try first.

What is a scenario?

A what-if plan that stays on its own until someone makes it official. Labor, purchasing, and the other planning screens follow the official plan unless you pick a different scenario.

Why can I not edit?

A Viewer reads the modules they were granted and cannot change the forecast. An empty grant opens no business screen. An Ops Admin or System Admin has every module, whatever is listed. Ask for Planner access to adjust weeks and scenarios, or Ops Admin to maintain products, headcount, labor standards, clinic mappings, and contract volumes. Inventory changes need an inventory role (Receiving & approvals, Pharmacy counter, Inventory finance or Inventory admin) and only reach the sites you are given. Modules and roles are granted on the Users & access page, not by signing in alone.

How do I check where a number comes from?

Open Codex, at the foot of the menu on the left, next to How It Works. For every screen and column it names the PioneerRx table and column (or who types it), where Rosetta stores it, and the calculation. Search it, or download it as a CSV to check line by line. The assistant can answer from it too.

What do the circled i icons mean?

A one-line hint appears when you hover a short label. The circled i is for longer definitions — Alternate ID, production type, back-test, routing, CompoundCost, bias. Click it; press Escape or click outside to close.