Overview
While trying to recreate a deleted category or creating a new one, you may encounter an error message “custom page route already exists” in the webstore. This happens even if the category was previously deleted from both B2B and B2C sides.
Root Cause
The error occurs because the system does not allow two entities (e.g., a Custom Page and a Category) to share the same name or URL path.
-
In this case, a Custom Page already existed with the permalink
/team-commercebuild
, which blocked the creation of a new category with the same name.
Example:
-
Custom Page URL:
https://www.placeholder.com/team-commercebuild
-
Attempted Category Name:
Team commercebuild
Resolution Steps
Option 1: Rename the Custom Page Permalink
-
Go to the custom page settings:
https://www.placeholder.com/admin/mcontents/pages/
-
Update the permalink to a new name (e.g.,
/team-commercebuild-page
).
-
Save the changes.
-
Retry creating the category with the original name (
Team commercebuild
).
Option 2: Redirect Category to Existing Page
-
Create the category with a different name (e.g.,
Team commercebuild Category
). -
Set the category to redirect to the existing custom page.
-
Verify the redirect works correctly on the storefront.
Verification
-
After applying either option, attempt to create or access the category again.
-
Ensure that no duplicate permalink exists in the system.
-
Test the category display and navigation on both B2B and B2C sides.
Helpful tip
-
Always confirm whether a custom page with the same permalink exists before creating a new category.
-
If duplicate naming is unavoidable, redirects are the cleanest solution.