On WordPress Multisite, a subsite administrator is not the same as a network super administrator. WooCommerce 11.2 requires super-admin rights for Blueprint imports on multisite, so a previously available import can now be blocked for an ordinary subsite admin.
The Blueprint import permission change applies to multisite. Single-site stores are not affected by this particular restriction. Establish which installation you are using before trying to repair an apparently missing capability.
Identify the intended target
Record the network, destination subsite URL, current user and source of the Blueprint file. A permission error and an invalid import file are separate problems. Moving to a more privileged account will not correct malformed configuration, and fixing configuration should not require unrestricted user access.
Ask the network owner to confirm whether the requested settings belong on this store. Review the Blueprint contents for environment-specific URLs and integrations before importing. Use only a trusted source. Keep secrets out of screenshots or support tickets.
Use a delegated import, not a permanent promotion
- Have the subsite owner describe the desired result and supply the reviewed configuration through the team's approved channel.
- Have an authorized super admin confirm the destination and the affected settings.
- Back up the destination site's relevant configuration and test the import on a representative non-production subsite.
- Compare the actual changes with the approved list. Investigate settings outside that list before proceeding.
- Schedule the production import with the network owner and verify the store afterward.
Do not add a support account to the super-admin list just to bypass the error. That role can affect more than the one storefront named in the ticket.
Target: Exact subsite confirmed. Scope: Configuration reviewed. Changes: Only approved settings changed. Access: No permanent role promotion. Explanatory checklist, not a customer test result.
A minimal acceptance worksheet
| Item |
Record before the import |
Verify afterward |
| Destination |
Exact subsite URL and store identity |
Same store received the changes |
| Configuration |
Approved setting names and current values |
Only intended values changed |
| Customer path |
Product, cart and checkout behavior |
Storefront remains usable |
| External systems |
Approved mail and payment environment |
No staging endpoint was copied live |
| Access boundary |
Who owns network administration |
Subsite staff were not promoted |
The mail and payment rows are review prompts, not a claim that every Blueprint includes those settings. Inspect the actual file and installed importer to determine its scope.
If the import still fails
Capture the error after confirming authorization. Note whether it occurs before file processing or while applying a particular step. Preserve the import version and a redacted configuration sample. Avoid repeatedly importing the same file without checking whether an earlier attempt partially changed the store.
For another common scope confusion, see why the plugin Delete button can be missing. That guide distinguishes ordinary plugins, network activation and host-managed components.
HandL WP can coordinate a controlled multisite change with your network administrator. The goal is an approved configuration on the right store, not broader access for everyone who encounters an import error.
References reviewed October 8, 2026. Examples are explanatory, not customer test results.