A website handover should explain how the store will keep working after launch. Having access to WordPress is useful, but it does not tell the owner who restores a backup, checks an update or responds when an order email stops arriving.

I built Aprajita Toor’s WordPress and WooCommerce website from scratch and continue to handle maintenance and support. My portfolio also includes Mapcha. The checklist below describes what to agree for a maintenance arrangement; it is not a disclosure of either client’s private infrastructure or an assertion that every item is included in every support contract.

Make responsibility explicit.

List the domain registrar, hosting provider, WordPress administrators, theme and plugin licences, email delivery service and connected business tools. Identify the business owner for each account and the person responsible for renewals. Keep passwords and recovery codes in the agreed secure system, rather than in a public handover document.

Agree which requests are routine care and which are new development. A plugin update, a new payment integration and a redesigned collection page have different scopes. Define the contact route, coverage hours and how an urgent issue is escalated; do not assume a response-time guarantee that nobody has agreed.

Specify a recovery plan you can actually use.

Document what is backed up, where copies are held, their retention and who can restore them. Include both site files and the database. Record the most recent restore test and the decisions needed when recent orders exist. A backup file being present is a different fact from a successful restoration.

WooCommerce’s update guidance recommends a current backup and testing on staging where possible. Its backup documentation explains the role of content and database backups. Choose a recovery procedure suitable for the store’s order activity.

Separate a test environment from the live business.

A test copy should not send real customer emails or create unintended payments, fulfilment events or subscriptions. Before testing, identify the integrations that need sandbox settings or isolation. Restrict access and prevent a private staging copy from being indexed.

Before deployment, decide how the change will be transferred. Replacing a live database with an older test copy can remove orders and other recent activity. Code, configuration and database changes need an explicit release plan rather than a single undifferentiated “push to live” instruction.

Keep a small, store-specific regression list.

Use the actual business journeys: find an item, select a variation, add it to the cart, apply permitted promotions, choose delivery and complete an approved test checkout. Include a customer account, transaction emails and any bespoke enquiry route. The exact list depends on the store; do not run real transactions without authorization.

For a catalogue such as Aprajita Toor’s, sizing information and ready-to-ship browsing deserve attention alongside the purchase route. For Mapcha’s multi-category experience, review navigation between product categories and editorial content. Those are visible website characteristics that can inform a regression list, not a claim about either store’s current backend testing.

Leave a change record and an acceptance decision.

Record the versions changed, the backup reference, checks performed, known issues and rollback procedure. State who accepted the release. After launch, check the live journeys and relevant operational signals. If something fails, preserve useful evidence and decide whether rollback or a targeted correction is appropriate.

A maintenance agreement should explain recurring responsibilities clearly enough that the store owner can answer “who handles this?” without guessing. Read about website refresh and ongoing care or discuss your store’s requirements.

Browse all website guides