Costyour true COGS, signed by the floor.
Because every dispense, step, hold and yield reading is captured at the kiosk, V5 can compute true COGS per batch — material, labour and overhead — and surface variance against the standard without a separate cost roll-up project.
Your COGS isn't wrong on purpose.
It's wrong because it can't see what actually happened.
Standard cost is a theory. Period-end COGS is that theory plus a month of plugs, averages, and adjustments. The math isn't broken — the capture layer underneath it is.
Every consumption, yield, scrap, and labor minute is a signed event the moment it happens — not a journal entry next week.
Every cost line is link-resolvable back to the kiosk event, the operator, the instrument, and the SOP rev that produced it.
Period close is a hash of what already happened — not a two-week reconciliation against a binder of guesses.
Each leak has a specific capture mechanism that closes it.
Click through. Watch what the data actually looks like.
Every dollar in COGS is link-resolvable back to a signed event.
Click any GL line. V5 walks you back through the posting, the consumption, the dispense event, the operator, the instrument and its calibration certificate. Period close stops being a reconciliation — it becomes a hash.
The number on the page means something again.
We deliberately don't quote a generic "X% COGS reduction." For the first time, the COGS you report is the COGS that actually happened — and decisions made on it are right because the data underneath them is right.
Activity-based costs follow the work, not the BOM. Easy SKUs stop subsidizing hard ones in your gross margin report.
Yield, scrap, and rework variance pinpoint the step and instrument — not a month-end pool that's too big to investigate.
Inventory and consumption are already posted. Close is verification of signed events, not a two-week reconciliation.
Cost-of-goods cited to your auditor walks back to the operator, instrument, and SOP rev. No 'we'll get back to you'.
We don't publish a fixed "$ saved per batch" — your batch size, standard cost structure, scrap baseline, and QA burden are all different from the next site's. We'd rather quantify the seven leaks against your actual data than guess with ours.
- · walk the 7 leaks against your last 6 months
- · quantify each one with your actual data
- · identify the 2-3 with the highest recovery
- · you keep the analysis whether you move forward or not
You know what each lot actually cost before it ships.
Most plants discover COGS three weeks after month-close, when the controllers reconcile dispense logs against the GL. V5 streams cost into the lot as it forms — labor, materials, utilities, scrap, changeover, QC — so the variance is visible at the line, not the quarterly board meeting.
COGS forms line by line as the batch runs.
When the same SKU costs 2.1% more this week, V5 finds the line that changed.
Variance gets attributed across labor, material, scrap, utility and changeover lines automatically — and ranked. The plant manager opens the standing 9am dashboard and the answer is on the first row.
Quote with the cost you actually have, not last quarter's.
Drill down to the SKU, the line, the operator — or up to a portfolio rollup in one click.
Sub-assemblies, kits and packaging components flow into FG cost without spreadsheet glue.
Multi-currency PO costs land at the dock in your reporting currency, FX rate captured at receipt.
Quality scrap, line scrap, changeover scrap each split out — not buried in a 'manufacturing variance' bucket.
Standard-to-actual variance posts to the GL on lot release, not a month-end batch job.
Pair lot cost with customer pricing to surface gross margin per lot, per ship.
Cost is a stream, not a memo.
Curious how V5 actually builds true COGS from the floor?
One signed event — the same data proves the batch and posts the cost.
MES, eBMR, WMS, maintenance, analytics and the ERP all read the same kiosk events. There is no parallel cost extract to reconcile — and no "cost roll-up project" to fund.
Wondering how V5 costing plugs into your finance stack?
The edge cases a month-end cost roll-up quietly smears.
Four moments where V5's event-level costing stays honest — even when the period, the rates or the BOM shift under the running batch.
Material revalued mid-period
API-501 jumps from $28.40 to $31.10/kg on the 12th. Older WOs stay at the rate they posted under; new WOs pick up v08 automatically — no retroactive smear of the prior period.
Rework on a flagged batch
WO-88488 reworks 1,100 tablets. Rework labour, rework material and rework overhead post to a child cost layer that rolls into the parent COGS — and into the QMS cost of poor quality.
WO spans the period cutover
WO-88440 starts 28 Sept, closes 2 Oct. V5 splits the cost layers by the rates effective on each event's date — not the date the WO happened to close.
Co-products & by-products
One run yields a sellable co-product plus a recoverable by-product. V5 splits the joint cost using the configured method (relative sales value, weight or fixed %) — every split shown on the eBMR.
Got a costing edge case the team's worried about?
Just ask V5 — it knows the product cold.
Pick a question or type your own. V5 answers grounded in how cost, cogs & variance — true cost from the ebmr, not estimates | v5 ultimate actually behaves on the floor.
The rest of the platform this plugs into.
V5 isn't a bolt-on. Every module shares the same data, the same audit trail, the same operator. Pick where to look next.
MES
Operator-led execution: scan-gated dispense, step-by-step kiosk, equipment + scale integration, live yield. Built for regulated process & discrete manufacturing.
WMS
Receiving, putaway, transfers, cycle counts, picks, pack & ship — all lot-aware, bin-accurate, FEFO/FIFO-enforced and barcode-driven.
QMS
Built-in QMS: deviations, CAPA, supplier scorecards, in-process AQL, release-by-exception. Aligned with 21 CFR 211/820, ISO 13485 and 111.
Got questions, or want to see it on your shop floor?
Ask V5 — our code-aware assistant — or spin up a workspace. Both are free.