Why Do I Get a WooCommerce Admin Permission Error?

Why This Happens

WordPress's role and capability system is more granular than a simple "admin vs. not admin" distinction — WooCommerce adds its own specific capabilities (manage_woocommerce, edit_products, and others) that need to be explicitly present on a role for that role to perform the corresponding action. A custom role created without these capabilities, or a role management plugin that accidentally stripped them, will produce exactly this kind of permission error even for an account that otherwise looks fully privileged.

Common Causes

• A custom user role (created for a specific staff member or contractor) missing one or more WooCommerce-specific capabilities that weren't included when the role was originally set up.
• A user-role management plugin inadvertently modifying or resetting capabilities during an update or configuration change.
• A genuinely corrupted user meta entry in the database, in rarer cases, where the role assignment itself is intact but the capability data associated with it has become inconsistent.
• Multisite-specific permission quirks, if the store runs on WordPress Multisite, where capabilities can behave differently across the network compared to a single-site installation.

How to Diagnose and Fix It

1. Check the specific user's assigned role and confirm it's the expected one (Administrator, Shop Manager, or a custom role).
2. Use a role/capability inspection plugin to see exactly which capabilities that role currently has, comparing against what WooCommerce actually requires for the specific blocked action.
3. Reset the role to WooCommerce's default Shop Manager capabilities if a custom role has drifted from what's needed, or add the missing capability explicitly.
4. Test with a fresh Administrator account to rule out a broader, sitewide permission issue versus one specific to a single user.

Finding the missing capability

1. Note exactly what fails. Record the screen address and the wording of the message. The page named in the address hints at which area of WooCommerce is being blocked.
2. Compare the role with Shop Manager. WooCommerce gives Shop Manager its capabilities by default. A custom role created from Editor lacks them. A role-editor plugin can show the failing role's capabilities next to Shop Manager's.
3. Test an Administrator account. If an Administrator also gets the error, roles aren't the cause. Look at security plugins that restrict admin access by rule or location.
4. Check whether a role plugin changed things recently. A role plugin update or setting change can reset capabilities.

Give staff the least access they need

For day-to-day store work, the Shop Manager role is usually enough, and it avoids handing out full Administrator access. Add individual capabilities to a custom role only for the specific tasks it needs.

Need staff permissions set up properly for a specific workflow? See WooCommerce fixes.