Running multiple WooCommerce stores on a WordPress multisite network creates a specific GPSR problem: how do you keep manufacturer data consistent across 3, 10, or 50 stores without managing it separately on each one?
If each store targets a different EU country or carries a different product line, the GPSR data might vary. But the manufacturer records, EU responsible persons, and compliance workflows should not be scattered across disconnected admin panels.
The multisite GPSR challenge
WordPress multisite shares one codebase but keeps content separate per site. Install the GPSR Compliance plugin network-wide and it activates on each site independently. Each site gets its own manufacturer records, its own product GPSR data, its own settings.
That is fine for 2 stores. It falls apart at 10. You don’t want to create the same manufacturer record on every site manually. You don’t want to update your EU responsible person’s phone number in 15 places when it changes.
Approach 1: CSV export and import
The simplest approach for small networks. Set up GPSR data on your primary site, export the manufacturer and product data as CSV, then import it on each secondary site. Our plugin integrates with WooCommerce’s native CSV importer, so the 5 GPSR columns map directly.
This works well for initial setup. For ongoing changes, you repeat the export-import cycle. Manageable with 3 stores, tedious with 15.
Approach 2: REST API synchronization
For larger networks, the REST API is the right tool. The plugin exposes full CRUD endpoints for manufacturer management. You can write a simple script that reads manufacturers from your primary site and creates or updates them on all secondary sites.
A basic sync script looks like this: fetch /wp-json/gpsr/v1/manufacturers from Site A, loop through each one, PUT or POST to the same endpoint on Sites B through N. Run it on a cron schedule and your manufacturer data stays in sync across the entire network.
Authentication uses WooCommerce consumer keys, so each site needs its own API credentials. Store them in a central config file and the script handles the rest.
Per-site customization
Some things should differ between sites. If your German store and your French store carry different product lines, they need different manufacturer assignments. The bulk edit wizard on each site lets you filter by category or product type and assign the right manufacturer in one operation.
Your frontend display language adapts automatically if you use WordPress language packs. The plugin ships with 8 translations including German, French, Spanish, Italian, Dutch, and Portuguese. Each site picks up the correct language based on its WordPress locale setting.
Licensing for multisite
Each site in a multisite network counts as one site for licensing purposes. A 3-store network needs the Business plan (3 sites, 99/year). Larger networks need the Agency plan (unlimited sites, 199/year). Both include the same features, just different site limits.
If you are running a multisite network selling to the EU, GPSR compliance is not optional for any of your stores. Centralizing it saves time and prevents the kind of inconsistencies that trigger market surveillance investigations.
Related articles
- Using the GPSR REST API for integrations
- Importing GPSR data via CSV
- Selling to the EU: compliance basics
