Data about partners and their branches, previously kept in a shared Excel file, is now managed in the Partner Locator administration. Website visitors then find a partner or branch using search and a map.
Partner and branch search
A search engine on the website presents partner branches and shows them to visitors on a map.
Data management without a shared Excel file
Responsible people edit data in the administration, ending the work in a single file where they overwrote each other’s changes.
One database for the website and apps
The same partner database can be used not only on the website but also in a web or native application.
Clients needed to maintain a partner database and update data shown on a map on their website.
The previous Excel file was edited by several people, who could unintentionally overwrite each other’s changes.
After analysing the requirements, we created the Partner Locator module with backend administration and a search engine for presenting and locating branches on the frontend.
Responsible employees and individual presented entities can manage relevant data; the public part can be adapted to the use case and the database used in a web or native application.
Partner data therefore has a single place of management, which the map on the website draws from.
Partner data for the website map was kept in a single Excel file that several people edited. One person’s changes could be unintentionally overwritten by another, so there was no certainty that the data shown on the website was correct.
Responsible employees edit data in the Partner Locator administration, and individual presented entities can manage their own details. The website displays branches directly from this database, which can also feed a web or native application.
The Partner Locator replaces a shared Excel file with backend administration and a frontend search for branches. Responsible employees and listed entities manage their own data, and the public part can be adapted to a website or a native application.
Data is managed in the backend administration of the Partner Locator module rather than in a shared Excel file as before. Responsible employees add and edit details there, and the frontend draws on this database when displaying branches on the map. This removes the situation in which several people unintentionally overwrote each other’s changes in one file.
Data can be edited by the client’s responsible employees and also by the presented entities themselves, that is, the partners whose branches the locator displays. Each of them manages the data relevant to them. The client therefore does not have to collect and enter every change centrally, and the details are maintained by those who know them best.
The frontend runs a search engine that presents partner branches and locates them on a map. Visitors can therefore find a partner directly on the client’s website. The details shown come from the administration, where responsible employees and the partners themselves manage them. The public part can be adapted to the specific use case, so the search fits whatever the client deploys the locator for.
Besides a website, the partner and branch database can be used in a web or native application. The data is still managed in one place, the Partner Locator administration, so the website and the application work with the same details. The public part can be adapted for each such use.