Overview
After the main location or store structure is created, users still need smaller maintenance actions such as rename or type change.
Where To Find It
Path: Stores > Maintenance actions
Use these store-maintenance screens when the store list already exists but a practical structural update is needed.
How It Works
QBM provides dedicated actions for creating a new store, renaming an existing one, or changing the store type where that change is supported.
Main Areas
| Area | What It Means | When To Use It |
|---|---|---|
| New store | Creates an additional store record in the working structure. | Use it when the business expands or adds a new operational store. |
| Rename store | Updates the visible store name without rebuilding the whole structure. | Use it when naming changes but the operational identity remains the same. |
| Change store type | Adjusts the type-based behavior of the store where permitted. | Use it when the role of the store changes in a meaningful way. |
Recommended Workflow
- Review the existing store structure before making a maintenance change.
- Choose the specific action that matches the real business need.
- Save the change and then test the affected workflows or selections that use the store.
Best Practice
- Treat store-type changes carefully because they may affect downstream behavior.
- Document rename decisions so staff recognize the new naming.
- Review store-linked reporting or permissions after major store maintenance.