Have the owner complete agreed store tasks
Have the future Wix owner edit a test item, change its stock, find an order and recover a mistake using the intended role. Record assistance and missing permissions. A handoff demonstrates the agreed operating tasks and recovery responsibility; it is broader than giving someone a collaborator login.
Worked example — illustrative data.
| Owner task | Role or dependency to confirm | Acceptance evidence |
|---|---|---|
| Edit TEST-MUG title and image | Relevant store editing permission | Owner completes without changing another SKU |
| Change synthetic stock state | Inventory responsibility | Storefront reflects intended state |
| Review test order | Order-management access | Owner finds the correct record |
| Recover a mistaken edit | Supported recovery method | Owner restores or follows agreed help route |
Inventory accounts, subscriptions, connected services and the person responsible for each. Verify Wix’s current ownership and role rules for the actual account before changing anything. Run the editor tasks with sample data and record completed, assisted or blocked. Include payment, domain and notification dependencies without exposing credentials. Leave a concise runbook for common edits and a named support route for work outside the owner’s role.
Decision: Complete the handoff when the owner tasks and recovery responsibilities are demonstrated. Transfer or revoke access only through an authorized, reviewed action after dependencies are understood.
Editor access may exclude billing and domain control: A collaborator may be able to edit pages without controlling billing, domain recovery or another connected service. Check those responsibilities separately rather than treating one successful login as full business control.
Continue with Guides for stores, software teams and local businesses, eCommerce website design and development and Who should own your website, domain and analytics accounts?.
Before applying the specimen, verify exact feature availability, required permissions and supported field formats in the provider’s current documentation and your store.