Posted on 22 November 2018
by Gerhard van der Bijl

Floriday compared to your own software

With Floriday, we are building an important foundation for the digital infrastructure of the floriculture industry. And this foundation is necessary. Many things have been well organized, yet every day we are confronted with illogical activities or message structures. Digital ordering with the order confirmation still gives rise to much confusion and there are some cracks in the VMP link here and there. And yet, this is only the beginning of a much more advanced digital cooperation between customers and growers. We are only at the beginning of a real digital marketplace. We need to do things differently, which is why we are building a new digital infrastructure with Floriday. 
But how does it compare to your software and your software provider?

Open system

We are positioning Floriday as an open system. At a later stage, your software provider will be able to access most of Floriday’s functions with the APIs. This way, you, as a grower, can directly manage the products, offer and orders on Floriday from your own software package. However, we are starting to offer these functions via Floriday’s own screens. This allows us to test the new functionalities with users before software providers link to them. It will be very easy to make adjustments to these components, since we will not have to make these adjustments to multiple software packages.

As soon as a certain function has proven itself, it is made available to external software providers via the Floriday API. The software provider can then access this function via the Floriday API and the grower can directly use the function from his/her own software.

An API is a set of agreements that software programs use to communicate with each other. These agreements form a shell around the software, giving other applications access to information and/or functionalities without developers needing to know how the other software works exactly. For example, many software packages use the Google Maps API - they are using the Google Maps’ functionality to strengthen their own software.

Focus - EAB

We want to resolve a number of pressing issues from the past with this new digital infrastructure. With Floriday, we want to harmonize and simplify the logistic operations of the different auction sites (such as the Aalsmeer or Naaldwijk auction documents, for example). This is very complex in the current situation because it requires adjustments to the grower’s systems, several of Royal FloraHolland’s systems and sometimes also third parties’ systems. We are going to solve this by replacing the EAB in Floriday, in a more or less invisible way, by a new data model at a later stage. Growers will be able to manage this ‘renewed EAB’ from their own software, via the Floriday API, submit it to Floriday but also create it directly in Floriday.

We also want to divide the function of the EAB. Today this EAB has a logistic, commercial and financial function. This makes it impossible to just exchange logistic information, because there is always a financial order for collection attached to it. It is therefore impossible to put carts in stock for sale without financial settlement taking place, for example. We will be solving this ‘invisibly’ as well in Floriday through the new data model.

Cooperation is essential to realize this digital infrastructure of the floriculture industry. That is why we are positioning Floriday as an ‘open system’ and we are actively seeking to cooperate with growers, customers, software providers and other parties. We realize that we have created together the sector that we know today. Especially the software providers have played an important role in the digitalization of the electronic delivery form (EAB) in the last 20 years. Now we are promoting the electronic delivery form to Floriday and the new data model and we want to do this together too. It is our intention to develop the Floriday API with the software providers and to realize great integrations with Floriday. By making certain components of the current software available in the form of an app within Floriday, for example.

Apps within Floriday

Another way for software providers to use Floriday is by offering their own ‘apps’. You will not find these apps in the app store on your phone, but in Floriday. The Floriday apps are seamlessly connected, which allows them to work perfectly with Floriday. Growers will soon be able to use apps that use information from his/her catalogue or apps that generate statistics based on transactions.  We are currently testing the options of the apps with two internal apps (HortiHeat and Insights); next year we want to make apps from other software providers available too, so a grower can add a growth registration app to Floriday, for example.

''We are setting up Floriday in a modular way, allowing growers to use certain functionalities in Floriday and other components from other software packages''

Modular use

The setup of Floriday and the APIs target what we call ‘modular use’. This means that growers can use certain functionalities in Floriday and other components from other software packages. You use the software package that best fits your company and are not restricted to the use of the Floriday screens or the software of a specific provider. You could manage for example your catalogue in Floriday, your stock in your ERP package and your commercial pricing yet in another package. The digital infrastructure of Floriday connects these different packages.


Involving software providers

Floriday has a large impact on the sector. This leads to questions from growers, software providers and other parties. Through the Floriday workshops and our Ideation process, we are actively trying to interact with growers. And we have organized sessions with the software providers together with Plantform. The conversations with the software providers will be intensified over the next months in order to further involve them in the shaping of the digital infrastructure for the floriculture industry.

We are convinced that adjusting the EAB, the transition from VMP to API for message exchange, a new data model, apps in Floriday, etc. are necessary. If we have our digital infrastructure in order, we will be better prepared to implement changes. And the return of your nursery will reap the benefits.

Gerhard van der Bijl
CDO

Other articles

Need help?

We’re happy to help you on your way!

Floriday uses analytical cookies to improve your experience on our website, to remember your preferences and to provide information to improve the website.


By clicking consent, you consent to the use of cookies. 

 Click here 

  for more information.

Yes, I agree