PlantPass

The nursery outgrew the notebook

The plant volume had grown past the point where paper could keep up. Every webshop order and every market sale was written down by hand and reconciled later, which ate one to two hours every single day.

On top of that, plants traded in the EU need plant passports. Issuing and tracking those by hand for a stock this size was slow and error-prone.

The plant is the record

The core idea is simple: each plant gets a printable QR-coded label. One scan, and every piece of information and every action related to that plant is right there.

The same identity drives the compliance side. The system issues EU-format plant passports with the official registration number and a traceability code, printed straight onto the label. Variants are tracked per pot size, plant development is followed over time, and the interface is responsive, so it is comfortable to use on any device.

FastAPI, PostgreSQL and a label printer

The backend is a typed FastAPI service on PostgreSQL. Plants move through the same five states the nursery uses, sellable, reserved for market, sold, scrap and used up. Each one carries a purchase price, a planned sale price, repotting cost and a margin calculated per plant. Every change lands in an audit log, so any number can be traced back later.

Sales are part of the core too, with transactions, line items, discounts and sales channels. Returns put the stock back where it came from. The webshop is connected through the Unas API. Stock and pot-size variants sync by SKU, so the webshop always shows the same stock that is actually in the greenhouse. Passport generation, QR slugs and printable label sheets close the loop from database row to physical plant.

The MVP took 8 weeks, has been in daily use since, and development is still ongoing.

The daily paper hours became a couple of scans

The system replaced the paper and Excel work that used to take hours every day, and those hours now go into something else.