Understand what is shared.
A WordPress Multisite network runs multiple sites using shared core software and network-level administration. Individual sites retain their own content and configuration. Separate installations can follow different software and release decisions, depending on their hosting and maintenance setup.
Neither label settles every data or security question. Ask how accounts, permissions, backups and recovery work in the actual environment. Separate installations on one hosting account are not automatically isolated in every respect.
Compare the decisions you will make later.
Consider who chooses plugins, when changes are released and what happens if one shop needs a different feature. A common owner can still need different shop rules. An agency’s customers can have very different responsibilities and exit requirements.
| Area | Question to resolve |
|---|---|
| Software changes | Can every shop follow the same update and plugin policy? |
| Business data | Which products, stock or customers truly need a shared source? |
| Access | Who may manage the network and each shop? |
| Recovery | Can one store be restored without creating problems elsewhere? |
| Future separation | How would one business leave the shared setup? |
Two businesses can reasonably choose differently.
In a fictional two-brand business, the same owner uses similar product types and one maintenance team. Shared software policy may be attractive, but catalogue and stock sharing still need explicit design. A network does not make those rules disappear.
In a fictional agency, independent clients need different plugins, release dates and future handover. More autonomy may matter more than a shared installation. These scenarios explain the criteria; they are not a score that selects an architecture from the number of shops.
Agree the technical plan and the daily work separately.
Ask the developer to explain supported integrations, domain handling, access boundaries and maintenance responsibilities for the proposed setup. Use a suitable test environment before converting an existing installation.
Then describe two real tasks: switching to the correct shop to help a customer and preparing a product change for one business. An architecture can be technically sound and still need a clearer daily workspace. Evaluate each question on its own.