Skip to content
Start a Project

Bensan

Recipe-driven inventory accountability for a multi-branch restaurant group — every stock movement recorded, every variance explained.

Client
Bensan
Industry
Restaurants
System
Inventory Management System
Services
Custom Software
Bensan inventory dashboard — inventory value, items below minimum, approvals, open variances and stock composition by category

01Overview

Bensan runs restaurants across more than one branch. Aether Labs is building an inventory system that ties stock to recipes, so the business can see what should have been used, what actually was, and why they differ. It is being rolled out in phases.

02The challenge

In a restaurant, stock does not just sit on a shelf. It is used in recipes, wasted, given as staff meals, and moved between branches.

Without a system that connects servings to recipes, it is hard to tell whether a shortfall is normal usage, waste, or an error — or to hold anyone accountable for it.

03The solution

We designed an inventory system where every stock movement is written to an append-only ledger, and recipes are versioned.

Daily servings multiplied by the recipe give the expected usage. Physical counts are compared against it, and variances are investigated and shown in pesos. The system never labels a variance as theft — it surfaces the facts for people to review.

04The system

  • Append-only stock ledger

    Posted records cannot be edited — mistakes are fixed with approved reversals.

  • Versioned recipes

    Expected usage is calculated from servings and the recipe in effect that day.

  • Waste & staff meals

    Recorded with photos, so usage outside of sales is accounted for.

  • Maker-checker approvals

    Nobody approves their own document or recipe change.

  • Blind counts & variances

    Physical counts are compared against expected stock, with variances in pesos.

  • Tamper-evident audit

    Every audit entry is hash-chained, so any edit can be detected.

05Visuals

Bensan stock on hand — value by category and every item with on-hand quantity, average cost and last movement
Bensan variances — count differences per item, each with a status until it is explained and approved
Bensan receiving — supplier deliveries with receipt numbers, references, who recorded them and posting status
Bensan menu and recipes — every dish with its recipe status, ingredient count and cost per plate

06Technology

  • React
  • Fastify
  • PostgreSQL
  • Kysely
  • TypeScript

Running into something similar? Tell us about your workflow.

Start a Project

Have a business problem that software could solve?

Tell us what you're trying to accomplish. We'll help determine what should be built.

Start a Project

or email hello@aetherlabscreative.com