Best approach – Multi Backend (cloning) with single frontend or single backend (More effort) with single frontend? [closed]

My application is separate backend and frontend, this app is about managing stok, manage product, transaction purchase or sales, reporting and etc

At first, client have 1 store we called “STORE A”

Client open 3 store in different place, like store branch that have main branch, and in current condition my app is used by main branch which is “STORE A” and client request to cloning my app to 3 in last year, so ya currently in one server running 4 backend app, STORE A, STORE B, STORE C, STORE D with 1 frontend

this is my current structure

FRONTEND 1 (login page choose the branch with contain url backend that user want)
 -> BACKEND A -> DATABASE A
 -> BACKEND B -> DATABASE B
 -> BACKEND C -> DATABASE C
 -> BACKEND D -> DATABASE D

This is the challenge: client request want to have reporting all of their store, which is stock and transaction report like profit loss, the problem is the app is separate by different database, should I create new project with multiple database connection to connecting all of store to get the data reporting ? I know this isn’t best practice, but client want to request fast in 1-2 month from now

Actually this is same condition when I cloning the store A to D, they want me to work fast so yeah I aggre to cloning rather than enhance backend to making just 1 backend 1 database, of course so much effort to do that

And right now client want me to create reporting that connecting all of data, so how I do that ? Should I merge all of database then just use select ? It’s bad practice, maybe in future the app will slow and I’ m sure that client will complain, why the app is slow etc.

In additional, client also want to add new feature that each store can transfer in another store, ie:

STORE A -> STORE B
product
- product A, 
- product B,

Either STORE A or STORE B have historical data that can increasing or decreasing stock each product, and not all of product in STORE B available in STORE A, so can be different product

how ? should I making 4 app backend to 1 again ? then enchance the database structure ? maybe create new column in each table like warehouse_id or branch_id or store_id, but I’m not sure will complete in 1 month, its to many effort.

I create new app how about the relation in main app?