What sets an ornamental horticulture app apart from an ordinary B2B app?
The ornamental horticulture chain has its own rhythm and its own language. EAB codes, plant passport fields, MPS registrations, daily prices on the clock, batch listings on 100procentveilen: these are not features bolted on afterwards, but starting points from which the design begins. The chain also works in tight time windows, because fresh product doesn't wait. An ornamental horticulture app has to be robust offline, fast to use and reliable in syncing with the source systems.
Do you work with existing ornamental horticulture software (Floricode, Florpartner, Priva, Hortimax)?
Yes. We integrate with Floricode's official APIs for EAB and batch codes, with Florpartner for transaction and invoicing data, and with climate computer suppliers such as Priva, Hoogendoorn and Hortimax. For crop administration (Letsgrow, AgriCura, Plantsoft) we connect via standard APIs or an ETL process. We are not a FloraHolland vendor, but we do build ornamental horticulture software that connects carefully to their official interfaces.
Do you build native or cross-platform?
Both. For performance-critical apps or hardware access (NFC scanning of plant passport labels, biometric unlocking, AI camera for disease detection) we often choose
native: Swift for iOS, Kotlin for Android. For B2B order books, customer portals and internal tools, Flutter is usually the more efficient choice: one codebase, two stores, one design system. We advise on what fits the use case, not on what the team prefers.
Can you integrate IoT sensors in the greenhouse or the cold chain?
Yes. For climate rooms and greenhouses we work with LoRa gateways for temperature, relative humidity, CO₂ and light sum, often linked to existing climate computer data. For cold chain towards export, we use NB-IoT loggers per pallet or roll container. For local connections to handhelds or phones, Bluetooth Low Energy. We buffer the edge component offline if the Wi-Fi in the greenhouse drops out and synchronise later.
What about certification: MPS, GLOBALG.A.P., FFP, plant passport?
We build audit export flows that deliver exactly the format that MPS-ABC, MPS-GAP, GLOBALG.A.P. or the Floriculture Sustainability Initiative requires. For the plant passport, the app generates labels compliant with EU Regulation 2031/2016 from your batch registration, with automatic archiving of the PDF for audits. We use GS1 standards for product identification and can deliver exports in EDI formats for customers who require them.
Does the app work offline, in the greenhouse or on the road?
By default, yes. For ornamental horticulture apps, offline-first is a requirement, not a luxury. A greenhouse regularly loses Wi-Fi, and a driver on the A4 sometimes has no signal. We build every app so that data is stored locally and syncs automatically as soon as connectivity returns, with conflict resolution so nothing is lost if two team members edit the same batch at the same time.
Who owns the code, and is there lock-in with Appfront?
The code is yours. We work in your own Git repository, the backend infrastructure runs under your own cloud account (AWS, Azure or Google Cloud, EU regions), and the apps live in your own App Store Connect and Google Play Console accounts. You can take it over, bring in another party or continue in-house whenever you want. No hidden contracts, no exclusive service layer.
Do you also work for agro-tech outside ornamental horticulture?
Yes. Many building blocks, such as IoT, cold chain, batch tracking and MPS-style audit flows, are reusable across ornamental horticulture and the wider agri-food sector. For our broader positioning, see our
agri-food software page.
Do you come on site to the nursery or to FloraHolland?
Yes. For serious projects, on-site work is often necessary: observing how stocking works on the shop floor, how a trader works at the clock, how a driver handles cold-chain loggers. We actively schedule those sessions during the discovery and build phases. We arrange vendor onboarding for FloraHolland access through your HR or security department.
How does a project with Appfront begin?
With an introductory meeting where we go through the problem you want to solve, which systems are already in place, which supply-chain partners are involved and what a suitable first step would be. After that comes a paid discovery phase of a few days with a concrete plan, or straight into a first build sprint if the use case is clear. Location of your choice: at the nursery, at FloraHolland, at our office on the Westerdoksdijk in Amsterdam, or online.