Case
The Plantpol nursery sells plants wholesale, and its demand follows the season: what is available in April is gone by July. We built a B2B store where the catalogue and the prices adapt to the season and to the customer.
Angular SSR on the front end, Laravel on the back end, two-way sync with the warehouse — the buyer sees real stock, not yesterday's.
Agriculture for us means accounting for and selling live goods with a short shelf life, not abstract "digitalisation".
Where agricultural businesses lose data
The greenhouse has climate control, the warehouse has stock records, the shop has a catalogue — and all three live apart. How much actually shipped, what is left on the shelves, what has not moved for two seasons: answering means somebody merging spreadsheets by hand.
Second, the commercial layer. Climate is Priva and Hoogendoorn territory, and that is their job. But a catalogue of thousands of items, wholesale orders, reservations against shipment and documents — that is often the weakest point, because nobody has treated it as a system.
What we build for the sector
Plant and product catalogue
Thousands of items with attributes, seasonality, photos. Search and filters that work at real volume.
Wholesale orders
Personal pricing for regulars, reservation against shipment, purchase history.
Warehouse accounting
Stock, batches, goods movement. What is reserved against an order is not sold twice.
Documents
Invoice, delivery note and waybill generated from order data without retyping details.
Equipment telemetry
Polling controllers over Modbus where pump, ventilation or irrigation status belongs in one panel.
Accounting integration
Export to bookkeeping so nobody retypes figures.
What it runs on
Angular with server-side rendering for speed and search visibility, Laravel backend, MySQL. Where equipment exists — Modbus RTU/TCP. We do not build climate systems: our part is trade, warehouse, documents and equipment data in one picture.
Our evidence
Plantpol — nursery e-commerce for the Polish market: 6,925 orders, a 7,422-product catalogue, 68,804 order lines, 1,811 buyers. Figures from the live database.
Frequently asked
Do you build climate control systems?
Do wholesalers need a separate site?
Do you work with foreign markets?
Answers on this topic
Plain explanations without marketing — useful even if you never hire us.
Telemetry where the link drops for hours
Telemetry where the mobile link drops for hours: store-and-forward, clock drift, deduplication, staleness on the dashboard, alerts that do not cry.
Raspberry Pi on site: when it is a sound choice
When a single-board computer next to the equipment is sober engineering, and when it becomes a source of night calls. Power, SD cards, temperature, updates.
An IoT/SCADA platform for a small plant: what you need
Seven layers of an IoT/SCADA platform: Modbus RTU/TCP over RS-485, gateway, telemetry, history, alarms, phone. Offline buffering, Raspberry Pi, security, cost.
Modbus: what it is and why your business should care
Plain explanation of Modbus RTU and TCP: how equipment exposes data, the difference between RTU and TCP, and what to do if your device does not support it.