Ecommerce website maintenance: what to check

Maintain an ecommerce website with clear owners for product facts, policies, checkout and support. Check the customer journey after relevant changes.

Ecommerce website maintenance keeps product facts, buying tasks and customer answers correct as your store changes. Assign an owner to each part, check the affected customer journey after a change and keep a workable recovery route.

A store can load normally while customers see the wrong stock or cannot complete a payment. Build your maintenance routine around those customer tasks. Set its frequency from how often the information changes and what happens when it is wrong.

Assign each maintenance responsibility

Assign maintenance to people who can correct the underlying record or coordinate the provider responsible for it. Give each responsibility a named deputy so an absence does not leave a failed customer task unresolved.

Maintenance ownership

ResponsibilityOwner’s routine workWhen to involve a specialist
CatalogueMaintain product facts, variants and imagesImports fail or connected records disagree
PoliciesApprove delivery and returns wordingAn exception needs a business decision or legal advice
PaymentsMonitor supported payment flows and reconcile ordersA provider rejects a valid setup or payment status differs from the order
Platform and themeMaintain settings and review supported updatesCode changes or platform faults affect customer tasks
ConnectionsConfirm imports and updates reach their destinationA feed stalls or duplicate updates overwrite records
Customer supportCorrect stored answers and route exceptions to staffA fault requires another owner’s access or decision

The catalogue owner can correct an approved product description. A developer handles a template that displays the wrong field. The payment owner supplies the failed transaction context to the payment provider. Keep those boundaries in the maintenance record, including who can approve a change.

Choose review frequency by change rate and consequence. Check affected variants after a bulk import and checkout after a payment-setting change. Review delivery wording when dispatch arrangements change. Use recurring spot checks for information that changes without a deliberate site release, such as stock.

Set an acceptable delay for each type of error. A missing secondary image and an incorrect payment total need different responses. Record who notices the problem and how it reaches the correction owner. A routine has failed if an alert arrives but nobody takes responsibility.

Technical debt is upkeep made harder by earlier shortcuts or deferred maintenance. An undocumented theme modification, for example, leaves the next developer unsure which behaviour an update must preserve. Record the customer task it supports and the work needed to maintain it.

An ecommerce website redesign changes presentation and navigation. A migration moves content or operations to another system and needs its own transfer and recovery plan. A content management system (CMS) performance repair targets a measured delay. Measure the slow editing or customer task before choosing a repair. Changing the visual design does not establish that either task becomes faster.

Check product facts and customer answers

Compare a changed product with its authoritative record everywhere a customer uses its information. The authoritative record is the approved source that the catalogue owner maintains. A copied product page cannot settle a disagreement with that source.

  1. Select a changed product and record its identifier and variant. Use an additional variant when its price or availability differs.
  2. Compare dimensions, price and stock with the maintained record. Check the applicable delivery conditions, including restrictions that change the buying decision.
  3. Open the product page and inspect its images and variant controls. Follow its product references and identify any missing or retired destination.
  4. Find the product through search. Confirm the result opens the intended item and displays the right facts.
  5. Ask the store’s customer-assistance channel a product question and a policy question affected by the change. Compare the answers with the approved sources.

For a hypothetical furniture store, a supplier corrects a table’s width. Update the maintained record, then inspect the product page, search information and assistance answer. A correct page beside an outdated answer leaves the customer with conflicting buying advice. Assign the catalogue owner to correct the source and the connection owner to investigate a stale copy.

When a returns rule changes, have the policy owner approve the wording before distributing it. Check the policy page and any stored answer that repeats the rule. Record which source each answer uses so the next correction has a clear destination.

Separate publication delay from failure. If a connection refreshes on a documented interval, check again after that interval. Escalate an answer that still uses the old fact, with the product identifier and the incorrect response. Staff need the correct wording while the underlying connection is repaired.

Verify the buying and service path

Run a controlled buying and support check after a change that affects either task. Before starting, obtain authorisation for the exact test environment and workflow. Use dummy customer details and disposable test data. Isolate fulfilment and notifications so test activity cannot send goods or messages to real customers.

  1. Select a known test product and variant. Confirm the displayed price and delivery conditions match the prepared test case.
  2. Add it to the basket and change the quantity. Check that the selected variant and totals remain correct.
  3. Use a supported payment test route to complete checkout. Check that the expected confirmation appears and one correct test order exists.
  4. Inspect the confirmation sent to your test inbox. Compare its order reference and line items with the recorded order.
  5. Ask a support question about the test order or an approved policy. Confirm the answer is correct or the conversation reaches the assigned person.
  6. Exercise a supported declined-payment case. Confirm that the customer sees a usable recovery message and the system does not mark an unpaid order as paid.

Shopify maintenance example

Shopify’s test-order guidance recommends checking checkout after payment-setting changes. It lists a test payment gateway and Shopify Payments test mode as simulated-payment routes. Gateway testing requires a paid plan.

For an authorised non-production store with Shopify Payments set up, open Settings > Payments. In the Shopify Payments section, select Manage, enable Test mode and save. Follow Shopify’s Shopify Payments testing instructions for supported test-card details and success or decline cases. Confirm the order displays the test-mode banner.

Keep this procedure off the production store. Test mode changes which payment methods are available, and some methods are unsupported. Deactivate automatic fulfilment before creating test orders and never buy a shipping label for one. Turn test mode off when the authorised test session ends.

When a check fails, retain the failed step and expected result before changing another setting. A missing confirmation needs an order-record and notification check. A wrong variant needs a catalogue and basket check. Route each failure to its owner with enough context to repeat the same task.

Recover and review a failed change

Confirm what you can restore before making a material change. Name the recovery owner, required access and acceptable interruption. Keep the previous approved source or configuration alongside a record of what changed. Protect exports that contain customer information.

A stored export proves that data was saved. A successful recovery exercise in an isolated environment proves that the chosen procedure can restore the required state. Include connected records and configuration in that exercise. An export that excludes payment settings cannot restore those settings.

Shopify’s backup and duplication guidance lists CSV exports and a downloaded theme among backup material. Its duplication procedure also requires apps and store settings to be configured again. Shopify says orders cannot be imported through the admin. Treat each saved file according to its recovery limits, not as a complete store restoration.

Use this recovery sequence when an authorised change breaks a customer task.

  1. Record the failed customer task and affected records. Contain further incorrect updates through the approved fallback, with a named person handling outstanding customer work.
  2. Identify the changed source or setting. Choose a correction or rollback that preserves legitimate orders and updates received since the change.
  3. Apply the authorised repair and reconcile affected records. A restored product file must not overwrite later valid stock movements.
  4. Repeat the original failed check with the same expected result. Inspect the saved state and connected answer, not only the success message from the repair.

A hypothetical price import can succeed technically while assigning the wrong price to one variant. Restore the approved price, inspect affected baskets or orders and rerun the variant-selection check. The order owner resolves any customer commitments separately from the catalogue correction.

After recovery, add the missed case to the relevant maintenance check and confirm its owner. Keep the cause and correction short enough that the next person can repeat the check. Resume the change only when the buying task works and affected records reconcile.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup