Your replies are a mixture of "This sounds false - large supermarkets would have this data" and "This is just an ML use case" and i think both miss the point.

Your replies are a mixture of "This sounds false - large supermarkets would have this data" and "This is just an ML use case" and i think both miss the point. Work backwards from the customer need. If they truly need this system, and are willing to pay for it, then it sounds like what you need to build is: * A database for product taxonimies/locations * An internal tool to make it easy and quick for staff to go through and log the locations of products to build out the data model * The actual maps UI and display tech. The thing is, this might not even be that much work. It's all a factor of how many "categories" the store expects customers to be able to search for. If the granularity level is "pasta", you can probably get away with 100 entries, and 1 days of grunt work for a staff member to log the location in the store where "pasta" and "coffee" and "condiments" etc are. This story is not a good example of a difficult customer or a difficult technical problem.