Are you thinking of switching your current search solution but the thought of integrating a new technology provider feels overwhelming? It doesn’t have to be – learn how.

Whether it’s an in-house development or a ready-made standard solution, FACT-Finder can be integrated into any shop. With an API-based approach, any development language has the possibility to make queries to FACT-Finder, returning all the results you need to display to your customers. The logic behind which results are shown and how, can be easily managed from our simple and intuitive management user interface. From consulting and implementation to after-sales support, our FACT-Finder team is at your side every step of our collaboration.

Compatible with any shop system

FACT-Finder project overview

This overview will give you an indication of the project process and the support our FACT-Finder team offers you.

Data export

FACT-Finder is a powerful search, navigation and merchandising tool, for which data on your products and content needs to be provided. This can originate from an eCommerce store database, PIM tool, or other data source. This is the start of all journeys with FACT-Finder, importing your data into the tool, to begin the first steps of optimization and merchandising through the management UI. Ideally, this data is provided in CSV format at least daily, although the time and frequency can be set by you.


Direct integration via the REST API offers you the greatest possible flexibility. Whether you have a PWA, a traditional or headless eCommerce store, or a mobile app; No matter the environment, each development language can send queries or data to FACT-Finder.

When communicating with FACT-Finder, the steps are as follows:

1) Search query is sent to FACT-Finder. The search parameters entered in the search box by the user (query) must be sent to the FACT-Finder search server by means of an authenticated HTTPS request (request).

2) Search results are received (response). The FACT-Finder search server delivers the search results in JSON format.

3) Search results are processed. The returned JSON must be interpreted (parsed) by the shopping system.

4) Search results page is rendered (displayed). The structure of the HTML rendered on the search results page must be based on the search results information that is delivered by FACT-Finder.

Using REST API allows the design of the search results page to be created by the shop and FACT-Finder does not stipulate any of the look and feel of the results returned. In this way, the design is centrally managed within the eCommerce store and does not need to be monitored or corrected at multiple locations.

What customers say about FACT-Finder integration

Hear directly from our customers about why they switched, their integration experience and impressive results.

“The technical implementation also played a decisive role for me. I spend a long time dealing with the topic of site search and comparing different providers. A great advantage of FACT-Finder is that it interacts with our store without interfering with the architecture of our website. With FACT-Finder we remain completely independent. The store communicates with the search but the design of the pages remains with us.”

“The integration went smoothly even though we use a shop solution that is based on open source and therefore does not come with standard APIs. We were able to adopt many components from the previous FACT-Finder version. For example, the data feed, which we only had to extend by a few fields.”

Ulla Popken
“It couldn’t have gone better. The go-live process was absolutely seamless, which was fantastic. The day after going live, I got to the office really early to enjoy the calm before the storm that I was anticipating. Even my colleague from the technical department arrived an hour earlier because he wanted to be prepared for the worst-case scenario – and nothing happened. FACT-Finder ran like clockwork right from the start.”