What sets an ornamental horticulture app apart from a standard B2B app?
The ornamental horticulture chain has its own rhythm and its own language. EAB codes, plant passport fields, MPS registrations, daily clock prices, lot registrations on the 100% auction: these are not features added afterwards but starting points the design is built on. The chain also works in short time windows, because fresh product does not wait. An ornamental horticulture app must therefore be robust offline, quick to respond and reliable in synchronising 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 floriculture 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 unlock, AI camera for disease detection) we often choose
native development: Swift for iOS, Kotlin for Android. For B2B order books, customer portals and internal tools, Flutter is usually more efficient: one codebase, two stores, one design system. We advise on use-case fit, not on the team's preference.
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 directly the format required by MPS-ABC, MPS-GAP, GLOBALG.A.P. or the Floriculture Sustainability Initiative. For the plant passport, the app generates labels in line with EU Directive 2031/2016 from your batch registration, with the PDF automatically archived for audit. We use GS1 standards for product identification and can supply exports in EDI formats for buyers 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 all apps so that data is stored locally and synchronises automatically as soon as connectivity returns, with conflict resolution so that nothing is lost if two employees edit the same batch at once.
Who owns the code, and is there lock-in to Appfront?
The code is yours. We work in your own Git repository, backend infrastructure runs under your own cloud account (AWS, Azure or Google Cloud, EU regions), and the apps sit 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 wish. No hidden contracts, no exclusive service layer.
Do you also work for agri-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 wider agri-food. For our broader positioning, see our
agri-food software page.
Do you visit the nursery or FloraHolland on site?
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 plan these 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 conversation in which we go through which problem you want to solve, which systems are already in place, which chain partners are involved and what a suitable first step would be. This is followed by 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.