Single org versus multi-org strategy for multi-country operations
Key Takeaway
Start with one org for all countries. Move to separate orgs only when a hard isolation need cannot be met in one org, such as a data localization law or a contractual isolation requirement, because every added org multiplies cost and governance work.
A manufacturer that operates in many countries can run all of them in one Salesforce org or split them across separate orgs. One org can handle local needs through regional deployment, sharing, and permissions. Separate orgs give a stronger boundary between data sets, but each added org multiplies cost and governance work.
Decide during discovery
Settle the org strategy during discovery, before any org is provisioned. Data residency is an architectural decision, not a setting you toggle afterward, because an org's residency is fixed when the org is provisioned.