Deluge is the costing and publishing app I built running hotel bars, and the one every engagement runs on — it is not sold on its own. Products, preps, recipes and menus live in one database; every document the programme needs is derived from it, so nothing goes stale when a price moves.
Costing is the spine. A product is costed once, ex-tax. A prep draws on products; a recipe draws on preps and products — or on another recipe. A menu lists them at a price. Change a supplier price and every prep, batch, drink and list that depends on it is re-costed when you save.
Each list publishes as a pack: spec cards and, as chosen, a production list, prep sheets, container labels and an order sheet. The pack is a snapshot with a fingerprint. When a build, a method or a price changes, the board says the pack is out of date; one Apply sends every out-of-date pack again. Packs show guest prices, never costs.
Read: Why bar documents go stale
The publish board: one venue, two outlets, one pack out of date since a price moved — and one button to send the current version.
Outlets within a venue share one database: products, preps, recipes and tax are costed once and shared by every bar on the premises. Each outlet owns its menus, publishes its own packs, gets its own kiosk tiles and its own named team link. Several venues sit under one login, each with its own cellar.
Reports are per venue; there is no group roll-up.
Deluge works alongside whatever POS and purchasing system the venue already runs. There is no integration to install, and I don’t claim one. Supplier price lists and till reports come in as spreadsheets — pasted, CSV, TSV or XLSX, including the hotel export with its merged cells — and the columns are recognised once and remembered per source. Sales match to the menu by till code, then product code, then name and size.
Read: Why purchasing and the POS never agreeNo, and I do not claim it does. Deluge works alongside whatever you already run: supplier price lists and till reports come in as spreadsheets — pasted, CSV, TSV or XLSX — the columns are recognised once and remembered per source, and sales are matched to the menu by till code, then product code, then name and size. There is nothing to install and nothing to replace.
Your team keeps running on it. The database — products, preps, recipes, menus and every published document — belongs to the venue, not to the person who built it, and the app stays under a per-venue monthly licence that covers the app alone: hosting, the vault, the team link, updates. Further consulting is quoted separately. Pricing on enquiry.
No. The team reads published documents through one shared link guarded by a team code the manager can rotate, or on the kiosk on the bar tablet. No staff accounts exist and no data is held about staff.
Yes. Outlets within a venue share one database — products, preps, recipes and tax are costed once — and each outlet owns its menus, publishes its own packs, gets its own kiosk tiles and its own named team link. Several venues can sit under one login, each with its own cellar. Reports are per venue; there is no group roll-up.
The venue owns it. If the licence ever lapses the app goes read-only — it never locks — and exports and the team’s published documents keep working. Every venue is backed up twice: a vault copy that follows your work and a JSON file you keep, which restores the venue on an empty device.
Reports as PDF, Excel and CSV with an audience preset (the owner’s money story, the manager’s full detail, or prices only for an outside party); costed data files; printable spec cards and packs; build sheets for batches; and a full JSON backup.
It replaces the stack of spreadsheets, documents and PDFs a beverage programme usually runs on. Costs, prices, spec cards, prep sheets, order sheets and margin reports are all views of the same database, so a supplier price change moves every figure that depends on it and a document is either current or visibly flagged as out of date.
The health check puts numbers under the venue; setup puts the venue in Deluge — every drink costed, the sales mix set against it, a re-price and re-cut list — and the team keeps running on it under a per-venue licence.