Architecture for location based application

We are a startup, which provides on demand lunch to cooperate companies in UAE. We have models like companies, restaurants, Menus, Meals, Users. Now we're launching in UK and Singapore where restaurants, companies, Menus, Meals are different than what we have here in UAE. Means DB data is related to location only, and it will be different in each country. For example, Companies, Restaurants, Menus etc all this data will be different in London and same goes for Singapore and all other locations around the globe. Should we use the same deployment and add location column in each data models or we should do different deployment and DB for each location.