PLATFORM
Spreadsheet-style inventory software that logs every change
Vercid's inventory module is spreadsheet-style inventory software: a grid that looks and edits like Excel or Google Sheets, backed by a database that logs every change instead of overwriting it. Your team keeps the working model it already has — rows are items, columns are the fields you track. Underneath, each item is a single live record, so two people cannot book the same piece of equipment from two copies of a file, and no edit is silently lost. The module includes fulfilment and exceptions views, an append-only audit log, and full-text search, inside your branded workspace.
Spreadsheets are the right interface for inventory and the wrong storage for it. Vercid keeps the interface and replaces the storage.
The Excel feel, without the Excel failure modes
Most teams track inventory in a spreadsheet because a spreadsheet is fast, visible, and familiar. The problems start when the spreadsheet becomes the system of record: copies multiply, one save overwrites another, and nobody can say which version is true.
Vercid's inventory grid keeps what works. It edits like a spreadsheet — click a cell, type, move on. Nobody on your team has to learn new software to update a quantity or mark a unit out. But the grid is only the interface. The record behind it lives in a database, and there is exactly one of it.
Every change logged. Nothing overwritten.
When someone edits a cell in a normal spreadsheet, the old value is gone. In Vercid, every change is written to an append-only audit log: what changed, who changed it, and when. The previous state is retained, not replaced. Nothing is silently lost.
That history is searchable. Full-text search runs across your records, so answering "where did this number come from" or "who checked this unit out" is a lookup, not an investigation.
One record per item. No double bookings.
Equipment rental breaks when the same unit is promised twice — usually because two people were working from two versions of a file. Vercid removes the versions. Each item is a single live record that the inventory grid, the dispatch console, and every seat in your workspace read together.
One record. Nothing lost. When a unit is booked out, that fact is on the record everyone sees, and it cannot be quietly replaced by a competing edit.
Fulfilment and exceptions, as working views
A grid answers "what do we have." Operations also needs "what goes out today" and "what is going wrong." The module ships two views for that: a fulfilment view for the work moving through the operation, and an exceptions view for the records that are off track and need attention.
Both views are built on the same live records as the grid. There is no export, no second copy, and no end-of-day reconciliation between the sheet and the schedule.
Replacing Excel inventory tracking without retraining anyone
Moving off a spreadsheet does not mean adopting a system your team resents. The grid preserves the shape of the work; the platform adds what a file never had: members and roles with per-seat licensing so the right people can edit, Google SSO for sign-in, and Postgres row-level security keeping each workspace's data strictly its own.
The module runs inside your branded workspace at your own subdomain, alongside dispatch, billing, files, and chat — and in the iOS and Android app, so the record is the same in the warehouse as it is at the desk.
What you get
- Spreadsheet-style grid with the Excel/Sheets editing feel
- Every change logged, not overwritten — append-only audit log on each record
- Single live record per item — no competing file copies, no double bookings
- Fulfilment view for work moving through the operation
- Exceptions view for the records that need attention
- Full-text search across inventory records
- Members, roles, and invites with per-seat licensing
- Google SSO and Postgres row-level security
- Available on the web workspace and in the iOS/Android app
Common questions
Can Vercid replace our Excel inventory tracking?
Yes. That is what the module is built for. The grid keeps the spreadsheet interface your team already knows — rows are items, columns are the fields you track — so there is no retraining. What changes is the storage: instead of a file that gets copied, emailed, and overwritten, every item is one live record in a database, every edit is logged to an append-only audit log, and the same record is shared with dispatch, fulfilment, and billing in your workspace.
Does the inventory grid overwrite old values when a cell changes?
Each item exists as a single live record that everyone reads and edits. There are no duplicate copies of a file to drift apart, so two people cannot book the same piece of equipment from two different versions of the truth. The dispatch console and the inventory grid work from the same record, and because changes are logged rather than overwritten, one booking cannot silently replace another.
What are the fulfilment and exceptions views in Vercid?
They are two operational views built on the same records as the inventory grid. The fulfilment view tracks work moving through the operation. The exceptions view surfaces the records that are off track and need a person's attention. Because both read the same live records as the grid, there is nothing to reconcile between them.
Bring your current inventory spreadsheet and we will walk you through what it looks like as a single live record.
Book a walkthrough