COCKPIT PANEL
The Admin page includes a Storefront Management area for partner storefront connections. You can add named storefronts, edit saved endpoints, delete old ones, and globally enable or disable storefront visibility without removing saved data.
When to Use This
- You want to add a new storefront integration.
- You need to correct or replace a storefront API root.
- You want to hide storefront integrations temporarily without deleting them.
- You want to clean out an old storefront entry.
What the Admin Section Includes
- Add Storefront form
- saved storefront table with edit and delete actions
- a global status switch to enable or disable storefronts
- a status pill showing whether storefronts are enabled or disabled
Steps
- Open Admin.
- Scroll to Storefront Management.
- Use Add Storefront to create a named endpoint entry.
- Use the table actions to edit or delete an existing storefront.
- Use the global storefront toggle if you need to disable or enable all storefront visibility.
- Return to the Store page and confirm the visible result matches the new configuration.
Expected Result
After saving, the storefront list in Admin should reflect the current endpoints and the Store page should respond to the global storefront status correctly.
Common Mistakes
- Deleting when you only meant to hide: Use the global enable or disable control if the endpoints should remain saved.
- Using unclear storefront names: Operators should be able to identify the endpoint without guessing.
- Changing Admin but not checking Store: Always verify the storefront effect from the browsing side too.
Example Use Cases
- Partner switch: The owner updates a storefront API root after a partner changes infrastructure.
- Temporary maintenance: Storefronts are disabled globally without deleting the saved endpoints.
- Catalog cleanup: An outdated storefront is removed from the panel after it is no longer used.
Related Articles
- How to Use Store Editor Mode
- Store Page Tour
- How to Review System Health Checks