VioVia
Inventory, production and purchasing that hold up under an audit.
Products and bills of material, purchase orders from draft to paid, production runs with lot traceability, and the batch records a regulated product needs. Built for operations where getting the count wrong costs real money.
Scheduled
Running
Done
Catalog
Products and bills of material, with their history intact.
A catalog that remembers. Every product keeps a revision trail of who changed what and why, so the question "when did this formula change" has an answer rather than a theory.
Versioned bills of material
A reformulation is a new version with a written reason, not an edit that quietly rewrites the past. Runs stay attached to the version they were made under.
Supplier items
The same material from more than one supplier, each with its own codes, costs and lead times.
Identity is protected
Ordinary fields are editable. Changing a SKU code or a base unit of measure is a different and more guarded operation, because everything already recorded is shaped by it.
A real revision trail
Who, when, and the reason they gave. Available for any product, not just the ones somebody remembered to document.
Purchasing
From a draft order to a paid invoice.
The whole arc of buying something, in one place, with the states kept distinct because they mean different things to your accountant.
Draft and issue are separate
Putting an order together and sending it to a supplier are two decisions, and the system treats them that way.
Partial receipts
Stock arrives in pieces. An order knows what has landed, what is outstanding and what has gone quiet.
Invoices and payments
Record the supplier invoice when it arrives and the payment when it goes out, including a deposit paid before any invoice exists.
Demand you can see
What is on order against what is actually needed, so a reorder is a decision rather than a guess.
Production
Runs, lots and knowing exactly what went into what.
A production run has a life: scheduled, approved, released, started, submitted, completed. Each step is a real state with real consequences, and the lots that came out can be traced to the lots that went in.
Lot traceability in both directions
Which lots went into this batch, and which batches a given incoming lot ended up in. The question a recall asks.
Progress from the floor
Record what has actually been made against what was planned, as it happens rather than at the end.
Photo readings
Capture a reading from the floor as a photograph, attached to the run it belongs to.
Cycle counts and discrepancies
When a count does not reconcile, that is a reported discrepancy with a trail, not a number somebody quietly overwrote.
Compliance
Batch records built for the auditor, not for the demo.
GMP and GDP documentation that comes out of the work rather than being reconstructed afterwards from memory and a spreadsheet.
The record is the process
The batch record is generated from what was actually recorded during the run, which is the only version worth showing anyone.
Nothing is deleted
Corrections are recorded as corrections. Production data does not get removed.
Permissions that bite
Who can approve a run, amend a bill of material or commit a stock change are separate permissions, because they are separate kinds of trust.
Guided changes
Every stock change is proposed, checked, then committed.
This is the part that is unusual, and it is deliberate. A change to stock is not written straight to the database. It is submitted as a request, validated, and only then committed, with the trail kept.
Submitted is not committed
A request has a status you can poll. Nothing pretends to be done before it is done.
Validation before the write
The checks run against the proposed change, so a bad adjustment is refused rather than reversed later.
It works for people and for programs
The same path whether a person is counting a shelf or another system is reporting a receipt.
Connected
It fits what you already run.
An operations system that cannot talk to anything is a second place to type.
Cin7 Core
VioVia grew up alongside Cin7 Core and speaks its API, so an existing deployment is a starting point rather than a migration cliff.
EDI when a retailer needs it
Purchase order acknowledgements, advance ship notices and invoices, for the buyers who require them.
It posts into Via Chat
A count that will not reconcile becomes a message in the right channel tagging the right people, and a decision that needs making becomes a task with an owner.
Questions people actually ask
Can I sign up for VioVia today?
No, and we would rather say so. VioVia is fitted to how an operation already works: your products, your bills of material, your suppliers and your process. That starts with a conversation, not a credit card.
Is this for us?
It was built for small manufacturers and consumer-products companies that make a physical thing, hold inventory, run production and answer to somebody about it. If you have a spreadsheet doing the job of an ERP, probably yes.
We already use Cin7 Core.
Good. VioVia came out of a Cin7 Core operation and speaks its API, so the things you have already set up are a head start rather than something to redo.
What about the AI parts?
Changes are proposed and validated before they are committed, and a person decides what gets approved. The assistant does not get a quiet back door to your stock levels.
Tell us how your operation runs.
Email with roughly what you make and what is currently holding the process together. A person reads it.