Operations
Part of Operating a conversion change through gates, ledgers and a release you can reverse
Who owns what in a conversion change, from merchant decision to reconciliation
Assign non-ranked ecommerce conversion responsibilities using current UK role boundaries, explicit evidence ownership and independent stop authority.
This role map covers one adult online-store change in England, with UK or Great Britain sources labelled by reach and official pages current at 6 September 2026.
These are accountabilities, not mandatory job titles. One person may hold several in a small business if competence, independence and conflicts are addressed. Employment-status and tax questions require their own qualified review.
What to take away
- Name the person assigned to each accountability, their evidence, decision, deputy and stop authority before work starts.
- The merchant decision owner accepts, revises or stops the change, but cannot waive a safety, consumer, accessibility, privacy, payment or security hold.
- Leave the launch on hold where a role is vacant or lacks qualified review.
- Handoffs belong in the role map, recording the exact state transferred, artefacts, recipient, acknowledgement and exception path.
- Qualified review means the named practitioner meets the minimum qualification listed in each role.
Before you act
- Name each accountability holder and their deputy.
- Record evidence, decision and stop authority.
- Hold the launch if a role is vacant.
- Confirm the named practitioner meets the minimum qualification listed for each specialist hold.
- Document each handoff state and acknowledgement.
- Keep retrievable evidence for incident questions.
1. Merchant decision owner
This owner defines the seller, product, customer population, proposed change and safe baseline. Evidence artefact: signed decision record with baseline version. They accept, revise or stop the decision. The government's online-selling guidance page, GOV.UK Online and distance selling for businesses, supports the transaction boundary that the owner must preserve.
2. Product evidence and safety owner
They control product facts, claims, warnings, traceability, expiry and correction. Evidence artefact: signed safety file. Where goods are involved, current OPSS guidance page, OPSS Product safety advice for businesses, provides the UK product-safety and corrective-action boundary. Missing safety evidence blocks release.
3. Consumer journey reviewer
A qualified consumer lawyer inspects product information, total price, optional choices, confirmation and remedy routes. Evidence artefact: signed total-price and remedy check. CMA, Online sales: price transparency, is authoritative for the cited pricing boundary. Commercial performance cannot override this review.
4. Accessibility reviewer
This specialist sets evidence for navigation, errors, authentication, payment and support. Evidence artefact: signed accessibility audit. The Equality and Human Rights Commission statutory code Services, public functions and associations (2014) explains the Great Britain reasonable-adjustment context. Minimum qualification: practitioner trained in WCAG 2.2 and assistive-technology testing. Automated output does not replace professional judgement or relevant user evidence.
5. Privacy and PECR reviewer
They inspect actual cookies, pixels, scripts, server events, purposes, permissions, recipients and retention. Evidence artefact: consent record and retention schedule. The ICO's final April 2026 storage and access guidance defines the current device-operation boundary. Minimum qualification: data protection practitioner able to interpret UK GDPR and PECR. This approval is separate from measurement validity.
6. Payments and reconciliation owner
This owner distinguishes order placed, payment authorised, captured, settled, refunded and disputed. Evidence artefact: reconciliation exception log. The FCA page Using payment service providers, payment-provider page, supplies register and protection context, not provider approval. Minimum qualification: finance or payments specialist who can reconcile PSP records. Reconciliation disagreement follows an owned exception route.
7. Security and incident owner
They control access, secrets, dependencies, logs, transaction monitoring, incident response and recovery. Evidence artefact: access and incident log. NCSC, Building and operating a secure online service, online-service guidance, supports that operating scope. Minimum qualification: security practitioner with incident response experience. Security approval does not decide privacy or consumer questions.
8. Measurement and evaluation owner
This person versions event definitions, eligibility, denominator, missingness and analysis. Evidence artefact: versioned event dictionary. HM Treasury, Magenta Book (2020), supports the distinction between observed outcomes and causal attribution. Minimum qualification: analyst able to document event definitions and causal limits. They must not translate a platform report into an effect claim.
9. Fulfilment and customer-remedy owner
They monitor confirmation, fulfilment, cancellation, return, refund, complaint and support states. Evidence artefact: consumer remedy log. GOV.UK, Online and distance selling, returns and refunds section, gives the relevant post-purchase context and exceptions. Minimum qualification: operations lead with consumer remedy knowledge. This owner escalates defects and verifies customer-safe recovery.
10. Release and change owner
This accountability assembles the signed packet, checks version integrity, controls exposure, pauses the change and verifies rollback. It also coordinates supplier exit and a safe operating route during recovery.
Evidence artefact: signed release packet and rollback record. NCSC, Logging and monitoring guidance, supports keeping retrievable evidence for incident questions; the release owner must still follow the privacy-approved retention schedule. Minimum qualification: release manager with rollback and evidence control.
Worked role map: small England store
Example only: a three-person England store selling homeware online.
- Merchant decision ownerowner-manager. Deputy: operations lead. Stop authority: may pause release; cannot override a specialist hold.
- Product safety ownerowner-manager. Deputy: buying lead. Stop authority: signs the safety file before release.
- Consumer journey reviewerexternal consumer lawyer. Deputy: none. Stop authority: no signature, no launch.
- Privacy and PECR reviewerexternal data protection adviser. Deputy: operations lead for records only. Stop authority: signs the consent and retention record.
- Payments and reconciliation ownerfinance lead. Deputy: owner-manager. Stop authority: owns the exception log.
- Security and incident ownerexternal security adviser. Deputy: operations lead. Stop authority: signs the access and incident log.
- Measurement and evaluation ownermarketing lead. Deputy: operations lead. Stop authority: signs event definitions.
- Fulfilment and customer-remedy owneroperations lead. Deputy: customer support. Stop authority: signs the remedy log.
- Release and change owneroperations lead. Deputy: owner-manager. Stop authority: pauses release.
Stop-authority conflict example: the release owner wants to launch on Friday. The privacy reviewer has not signed the consent record. The release owner cannot overrule the privacy hold. The merchant decision owner may set priority, but release waits until the reviewer signs or the tracking is removed.
Handoff record template: date and time; state transferred; artefacts; recipient; acknowledgement; exception path.
Example acknowledgement: 'Received 14 May 09:10. Payment authorised, not captured. Capture check pending. Exception path: finance lead.'
Common questions
What can the merchant decision owner not do?
They accept, revise or stop the change. They cannot sign a specialist hold on a reviewer's behalf. The role map names the reviewer and minimum qualification for each hold.
What must be recorded in the role map for handoffs?
Record the exact state transferred, required artefacts, recipient, acknowledgement and exception path. Use the handoff record template and example acknowledgement above.
When should the launch be left on hold?
Leave it on hold where a role is vacant or a named reviewer has not signed the required evidence. The role map names the evidence artefact for each role.
