Architecture of a Web-app, is there any better choice?

consider a scenario:

For 1000 store branches that need web-based solution (receive data at first use from server and put it locally and after that use minor central update and save sold product list locally and then push these list to different central database)

I propose the following Architecture:

each store have 2 or more users (2 or more PC's) and one Local DB Server in each store plus to one Central DB SQL, we need sync from Central SQL Server DB to local DB at first time of each day (each update sync is at most 10 MB), sold product list is stored on local DB and from here send to Central SQL Server DB. at first running of this web app all data (2 GB) from Central SQL is download on local SQL Server. PC's in each store works with local DB Server.

1) IS this a good pattern for architect of web app?

2) Is it good that local and central DB have a same architecture (SQL Server) or is it better to use low light version locally (such as Pouch DB)?