Project
Multi-location WordPress
Multisite: one install and one database, a site per location with its own products and copy.
- Year
- Dic 2024
- Role
- WordPress
- Team
- 1
- Stack
- WordPress Multisite
01
The problem
Each location sold and published different things. One site mixed the catalog; several installs split maintenance. They needed a tenant per location without cloning WordPress.
02
Technical decisions
WordPress Multisite. One install, one database, one site per location. Content (products and information) lives on its site; operations stay one place.
WordPress Multisite
The cut was products and information per location. Multisite gives a site per tenant on one install and one database, without a custom CMS.
One database, not one WordPress per location
Cloning installs would have cloned updates, themes and backups. A Multisite network keeps that in one place and splits only the content.
03
Interface
A WordPress site per location, run on the same network. No public screenshots.
04
Result
Delivered in December 2024. No publishable location count or URL. The client runs products and information per location on a single install.
05
Learnings
Multisite fits when the tenant is a location with its own catalog. The problem was not picking another CMS: it was not cloning installs to split content.