Artisanly - Consignment Billing for Small Food Producers
Built a consignment ledger for small food producers that bills each stockist on what actually sold rather than what was dropped off, with delivery rounds and commissions agreed on the road.
Project Goals
Replace notebook-and-memory consignment tracking with a single shared ledger, make the arithmetic visible so producer and shop agree before the driver leaves, support counting stock one-handed while standing in a shop, and keep the product usable for a producer with a handful of stockists as well as one with dozens.
The Problem
Consignment is a bookkeeping problem disguised as a delivery problem.
A small producer drops off twelve jars at a shop. Three weeks later they come back. Some sold. Some are still on the shelf. One broke. The shop remembers it one way, the producer remembers it another, and the invoice gets written from whoever sounds more certain.
Multiply that by thirty stockists and the producer is no longer running a food business. They are running a reconciliation business badly, from a notebook.
What We Built
One ledger per stockist, settled on what actually sold.
The delivery screen is the whole product. You arrive, you count what is still on the shelf, and the app works out the rest: what sold since last time, what needs replacing, what the shop owes. The arithmetic is shown line by line rather than collapsed into a total, so both sides can agree on it before anyone gets back in the van.
It is built to be used standing up, one-handed, in a shop, with a crate under the other arm.
Technical Implementation
Astro for the marketing site and product shell, TypeScript throughout, and a canvas-driven hero that renders the actual product screens rather than mockups. Commission and consignment rules are modelled per stockist, so a producer can run different terms with different shops without keeping the difference in their head.
WhatsApp is the support channel, which matches how the producers in this trade already work.
Note
The results above are delivered capabilities, verifiable from the running product. If you have real adoption or time-saved numbers from the client, they belong here instead — I have not invented any.