Back to all articles
Digital Estate Planning

WooCommerce Store After Owner Death: A Continuity Checklist

Preserve a WooCommerce store after its owner dies: organize access, orders, backups, hosting, extension renewals, and payment-provider requests.

Stefan-Iulian Tesoi · Digital Legacy Planning Author
Published: 2026-09-11
Updated: 2026-09-11
7 min read
WooCommerce Store After Owner Death: A Continuity Checklist

A WooCommerce store after owner death needs someone to coordinate customers, technical access, and business decisions. Orders may still arrive while the family is locating records. Begin with a short operating plan: who can respond to customers, which services must stay available, and who can approve the next steps.

There is no single account handover that resolves every dependency. Treat the WordPress website, hosting, domain, extension purchases, and payment services as separate items. The checklist below is a practical coordination plan. Confirm authority to act with the business or estate representative, and ask each provider about its own requirements before requesting changes.

1. Make a map of the store

Record the website address, business name, hosting company, domain registrar, administrator contacts, and billing email addresses. Add the developer or agency, warehouse, shipping service, customer support mailbox, and accounting contact. Use records you are authorized to inspect, and mark missing information clearly.

For every service, write down the account identifier, next renewal date, person with authorized access, and immediate consequence of losing it. Keep passwords and recovery codes in a separate protected arrangement. An inventory should help a coordinator find the right person without exposing the whole business to everyone reading the document.

Choose one coordinator and a backup contact. Give each urgent task an owner and a review date. A shared list of unresolved questions prevents relatives, employees, and contractors from sending conflicting instructions to the same provider.

2. Decide whether new orders can continue

Ask the operator to count paid but unfulfilled orders, pending refunds, open disputes, preorders, and recurring customer commitments. Confirm that someone can access stock, packing materials, shipping accounts, and customer messages. A working checkout alone does not show that the business can deliver.

If fulfillment cannot continue reliably, have an authorized administrator arrange a controlled pause in new purchases and publish a clear service notice. Test the customer experience after the change. Keep an appropriate contact route available for existing buyers, and explain when they can expect another update without disclosing private family details.

Review automated charges and external sales channels separately. Pausing new checkout activity may leave other workflows running. Keep an order log showing the next action, responsible person, and supporting records for each unresolved case. Coordinate refunds through the approved payment process, and record confirmation rather than relying on a changed order label.

3. Separate daily operations from administration

WooCommerce's role documentation distinguishes Shop Manager access from full Administrator access. A Shop Manager can manage products and orders, including refunds, without receiving every WordPress administrative capability. Check the site's actual permissions before assigning work, especially where plugins customize roles.

Use named accounts for people continuing operations. Review access with the existing authorized administrator or agency, and give each person the permissions needed for their task. Avoid making every family member an administrator simply because several people are helping.

If nobody has authorized administrative access, contact the hosting provider and relevant account providers through their official support channels. Explain the death and ask which documents and verification steps they require. Keep case numbers and replies. Do not assume that possession of the owner's phone, mailbox, or password establishes permission to act on every connected service.

4. Preserve a usable backup before major changes

The WordPress backup guide explains that a complete site recovery needs both the database and site files. Ask the technical operator to preserve a dated backup set, including the store database, uploads, themes, plugins, and configuration. A product spreadsheet can support an inventory, but it should not be treated as a complete store backup.

Have a qualified operator test recovery in an isolated environment. Disable live payments, outgoing customer messages, and automated integrations in that test copy before running it. Check recent orders, product images, downloadable files, and the settings needed to understand how the store operates.

Store the backup securely and limit access because customer records may be included. Record where it is kept, when it was created, and who verified it. Avoid overwriting the live store with an older copy during a handover; doing so can lose activity that occurred after the backup.

5. Keep hosting, the domain, and email accounted for

Review hosting, domain, DNS, business email, backups, and essential service renewals as individual dependencies. Identify which charges use a personal payment method and ask the responsible representative how approved business expenses should be handled. Keep invoices and decisions together.

Contact the host and registrar separately about continuity or transfer. Ask what happens at the next renewal and how to keep a support contact reachable while ownership is reviewed. Record the current configuration before a technician changes anything.

An agency may maintain the website while another person owns the hosting account. Ask the agency to describe that boundary in writing. Agree on who will maintain the site during the transition, which work is authorized, and when the arrangement will be reviewed. Avoid canceling an apparently duplicate service until its purpose is understood.

6. Review extension purchases separately

WooCommerce.com supports subscription transfers between accounts, with ownership and future billing moving when the recipient accepts. That ordinary process does not itself change the site's WooCommerce.com connection. If the deceased owner's participation or account access is unavailable, ask support how to proceed instead of assuming the routine transfer steps apply.

List paid extensions and themes, their purchaser, renewal dates, and the features they support. Distinguish subscriptions for store software from subscriptions sold to customers. Mark whether an agency purchased a license and whether other websites depend on the same arrangement.

Confirm the recipient, billing responsibility, and continued update access for each approved handover. Keep written confirmation. Avoid removing a plugin merely because its purchase record is difficult to find; first ask the operator what customer or administrative workflows depend on it.

7. Ask the payment provider about succession

WooPayments' ordinary ownership-transfer guide involves site administration, a WordPress.com connection, and Stripe Express ownership. It includes verification by the previous owner and warns of a payment interruption during a connection change. Those steps cannot simply be assumed to work after the owner's death.

Contact WooPayments support with the store details and explain that the owner cannot participate. Ask what documentation, account review, and business-representative changes are required. Follow each other payment provider's own process too; a WordPress administrator account does not resolve those separate requests.

Record outstanding payouts, refunds, disputes, and the next response deadline. Coordinate any proposed bank-detail changes with the authorized representative and provider. Keep financial decisions separate from routine website edits so that a technician is not left deciding where business funds should go.

8. Leave a tested handover for the future

Owners planning ahead can nominate an operational backup, document approved access, and keep a service inventory with their wider business records. Explain how to pause new orders, where fulfillment instructions live, and whom to contact for payment or hosting problems.

Run a small rehearsal using the backup operator's own account. Can they find an outstanding order, locate the latest backup, identify an upcoming renewal, and reach the support mailbox? Record gaps and fix them while the owner can still approve changes. Review the plan after changing providers or key staff.

Your next step

Start with the oldest unresolved order and the nearest service renewal. Assign a responsible person to each, then complete the access and backup inventory before deciding whether the store will continue, transfer, or close. Keep the final decisions with your digital legacy checklist so the next person can find both the instructions and their limits.

Related Topic Cluster

Related Articles

Adobe Creative Cloud Account After Death: A File and Subscription Plan
Handle an Adobe Creative Cloud account after death: preserve creative files, distinguish personal and business access, and request subscription cancellation.
Canva Account After Death: Preserve Designs and Brand Assets
Plan what happens to a Canva account after death: identify shared designs, preserve brand assets, contact support, and arrange a practical handover.
Nonprofit Digital Continuity After A Leader Dies
Build a nonprofit digital continuity plan that protects accounts, records, donations, communications, and administrator access after a leader dies.

Stay Updated

Subscribe for practical digital legacy planning strategies and updates.