Safe launch, operations and support EN
Agree ownership and acceptance, investigate failures safely and prepare a useful support request.
This checklist recommends a working process. It is not an included support contract, response-time guarantee or certification. Agree the support channel, hours and escalation route with your provider before customers depend on the system.
Agree the launch conditions
| Topic | Evidence to have ready |
|---|---|
| Ownership | Named owners for the store, data, integrations and technical operations |
| Source systems | Which system owns products, prices, customers, inventory and invoices; who fixes discrepancies |
| Access | Correct store, roles, modules and minimum necessary permissions for people and agents |
| Side effects | Explicitly permitted test orders, payments, emails and shipping bookings, with cleanup responsibilities |
| Acceptance | Recorded normal and failure scenarios, not only a screenshot of a successful page |
| Incident handling | Contact channel, operating hours, escalation and who may stop a faulty flow |
Agree which data to reconcile before and after migration. A successful import does not establish correct prices, inventory or invoicing. Start with the integration administration guide and the B2B operator walkthrough where relevant.
When something fails
- Record store, environment, timestamp with timezone and affected workflow.
- Check selected store, role, module activation and required connections.
- Separate expected from actual behaviour. Keep the error text, safe reference and a redacted screenshot if useful.
- For payments, invoices, shipping or other external effects, inspect the destination before retrying. A browser interruption does not prove failure.
- Describe impact: one user or many, one order or all new orders, start time, and any safe workaround.
Do not grant administrator access or every API scope simply to remove an error. Use the read-only API quickstart to inspect access boundaries before attempting writes.
A useful support request
Include the affected store/environment, page or function, first observed time, short reproduction steps, expected and actual result, safe error reference, impact and checks already performed in downstream systems. Use the agreed contact channel and provide a safe way to reach you.
Exclude passwords, keys, tokens, payment-card details and complete customer lists. Remove unnecessary personal information from logs and screenshots. If you suspect unauthorised access, do not investigate by opening other customers' data. Report privately through the agreed security channel or the contact route on the security page; check its review status too.
Confirm operational commitments in your agreement
- Who operates the service, where is data processed and which providers apply?
- Which data-processing agreement governs the service and its termination?
- What is backed up, how long are copies retained and how has recovery been tested?
- What recovery-time and data-loss targets, if any, are actually agreed?
- What support, hours, escalation and SLA are included?
- Who approves production changes and how are incidents or changes communicated?
- What audit or certification evidence is available if your organisation requires it?
These questions do not imply a particular certification, round-the-clock coverage or uptime guarantee. Read the DPA, subprocessor information and terms alongside the applicable agreement. Pages marked as drafts do not replace approved contract documents.
Changes after launch
Agree testing, approval and recovery scope before major changes. A theme preview is not an isolated environment for payments, global settings or integrations. Follow the design and theme workflow. Record the exact change, who approved it and who verified the result. Do not assume reactivating an old theme reverses unrelated settings or business actions.