LIQUIDIQ is the operating system for drinks distributors. Stock, tasting panels, batch traceability and customer claims in one record, so a fault found on the bench points at the delivery that caused it and the money it puts at risk.
An ERP extract tells you how many cases are available. It does not tell you which of them is oxidising, which lot a customer keeps returning, what the stock is really worth, or when the panel last opened a bottle. That knowledge sits in a workbook, an inbox and somebody's memory.
Most systems value the cases marked available, not the cases on the floor. The difference is usually six figures.
Without a lot number, a confirmed fault means pulling the whole item number rather than the delivery that caused it.
Three customers reporting the same bottle in one month is a pattern nobody sees when claims live in an inbox.
Wine and spirits share a platform but not a rulebook. A vodka is never rated against a rosรฉ's sampling interval.
Stock across all warehouses, with expiry banding, bin allocation and storage temperature against the target for each style.
Unit cost derived from the ERP figure and applied to every case on hand. Value at risk by expiry band, location, style and brand.
Sampling intervals per style, the five stage tasting sequence for wine, and a permanent history that survives every refresh.
Bottle, closure, fill line, liquid, palate, storage and packaging. Adverse findings are counted, not just noted.
Lot numbers with their own best-by dates, reconciled against the stock figure so the gap is never silent.
Supermarkets, hotels, bars and restaurants report against the product, with photographs, bottles affected and the value in dispute.
The purchase report loads in and reconciles against what is already there.
Everyone signs in, and every entry is stamped with their name.
Installs to a phone home screen, opens without a signal, and updates the moment the server does. No app store queue.
No dependencies, no database server to provision. The whole thing is one file and one database you can copy.
Built for a wine and spirits book of several hundred item numbers across multiple warehouses, where quality is a commercial risk and not just a preference.
Every row carries an organisation. One client cannot read or write another's records, inventory, claims or people. Enforced on the server, not in the browser.
Viewer, Taster, Manager, Administrator. A viewer's write is refused by the API even if the interface is bypassed entirely.
Every tasting, batch, claim, image and status change is stamped with who made it and when, and kept through every refresh.
Tell us how many item numbers you carry and how you taste them today. We will show you what the same book looks like in LIQUIDIQ.
