Hi @digitalbrick !
No worries! I try my best to answer all questions, it’s just that unless it’s a bug report or technical issue directly related to WPRUS, I keep it at giving pointers toward a solution, without going too deep in specific use cases.
Talking about use cases, yours seems to be achievable, at least from the given info: each of the 4 satellite sites would be synced with the storefront (settings-wise: 1 storefront remote site on the satellites, 5 remote sites on the storefront ; incoming/outgoing details depend on your specific scenario). You can sync any operation (I imagine at least login, update and create in your case).
The main question is about the data the storefront needs to get from the satellites; that would be synced upon update + metadata operations, with allowed meta configured.
Now, if you wish to send data that can be used by WooCommerce (user meta – say, a phone, with meta key billing_phone), they need to either exist for the user on the sending site (meta key billing_phone in this example), or be mapped in the receiving site (with a custom plugin and core WordPress filter hook, on update meta with key example_phone, also update meta with key billing_phone).
There are some ways to do that more painlessly than others. For example, if your satellite sites use Ultimate Member, it is possible to assign a meta key to the profile fields (say, a phone field with billing_phone meta key, even if WooCommerce isn’t installed).
In that case, there is no need to code since the meta keys on the satellite and the storefront would match.
I hope that helps!