Store maintenance: what to do monthly
The monthly routine that keeps a store fast, secure, accurate and profitable, in an hour or two.
The short answer
A store on a managed platform does not need server maintenance, and it still drifts every month in ways that cost money quietly: an app added for a campaign and never removed, a former agency still logged in, stock that no longer matches the back office, structured data broken by a theme update, a payment method that stopped working in one market, emails and reviews gone stale, a search that returns nothing for the new product line. A monthly routine in six groups catches all of it in an hour or two. Most items take minutes when done monthly and become projects when discovered after a year. Record the results; the record shows the trends and proves the store is looked after.
The monthly routine
| Group | Checks |
|---|---|
| Speed | Real-user mobile numbers for homepage, top collection and top product against last month; lab check of any regression; new scripts on the page identified |
| Apps and access | Apps list reviewed: purpose, use, permissions, storefront injection; unused removed. Staff and collaborator accounts reviewed; two-factor confirmed; leavers removed |
| Catalogue and stock | Stock for top sellers compared with the back office; products missing images, weights or descriptions; out-of-stock behaviour; new products in the right collections with structured data valid |
| Checkout and payments | A real order per main market and method, refunded; discount rules behaving; fraud holds reviewed; payment failure and abandonment by method and market read |
| Search and tracking | Search console: indexing, errors, structured data, security issues; zero-result site searches reviewed; analytics purchase event verified; sitemap and canonicals spot-checked |
| Customers and content | Email flows sending with current content; reviews collected and answered; policies current; campaign pages retired; top articles current |
Running it
- Put it in the calendar on the same day each month with a named owner per group.
- Use one checklist shared between the store team and the partner.
- Start with the real order; it finds the most.
- Record pass, fail or fixed per item, with the numbers where there are numbers.
- Fix small things immediately; schedule anything larger.
- Compare with last month and note trends: speed, app count, zero-result searches, failures by market.
- Re-run the launch checklist before peak season on top of the monthly routine.
What the record shows
Over months, the record is the store’s health trend: speed holding or slipping, the app count stable or creeping, zero-result searches falling as products are named better, payment failures by market resolved, access reviews clean. It is what a new team member, a partner or a buyer reads to understand how the store is run, and it is what turns maintenance from a promise into evidence.
What this means for you
Run the six groups monthly on a fixed day with named owners, start with a real order, record the results and watch the trends. An hour or two a month keeps the store fast, secure, accurate and profitable, and it is the routine that makes peak season an ordinary month with more orders.
Frequently asked questions
Does a store on a managed platform really need monthly maintenance?
The platform maintains itself; the store does not. Apps accumulate and slow pages, staff and agencies keep access, stock drifts from the back office, structured data breaks with theme and app updates, a payment method fails quietly in one market, emails and reviews go stale. None of that is the platform's job. An hour or two a month keeps it from becoming a quarter's clean-up.
Who should do it?
Whoever runs the store's operations, with the partner for the technical checks such as speed, structured data and integrations. A shared checklist with owners per item, run on the same day each month, recorded. The routine belongs to a person, not to a good intention.
Which item gets skipped?
Placing a real order and following it through: checkout per main market, confirmation emails, fulfilment, tracking page, and a refund. It takes fifteen minutes and finds the failures that reports do not show: an email template broken by an app update, a payment method silently off, a tracking page pointing nowhere.