Social commerce operating workflow in England: six stages from request to pause and handover

Capture a decision-ready work request

Start only when a request contains enough detail to route and govern the work. Record product identifier, seller, social destination, checkout, audience, offer, stock source, delivery promise, creative version and intended live period. Name the person authorised to refuse release and the person empowered to pause sales.

A route record should connect the approved product record to the public asset, listing, checkout, order, fulfilment, cancellation and refund. Build each release from one planning template and use the quality checklist after approval. Do not proceed until all ten fields and both authorities are recorded.

Confirm item identity before approval

Approve the exact item and variant, rather than relying on a similar title. The product owner checks identity, category, specifications, evidence, labelling and the safety record, confirming that the material applies to the chosen variant and the use described to buyers.

OPSS business guidance sets out duties across supply-chain roles and distinguishes Great Britain from Northern Ireland. For an English sale, follow the applicable Great Britain route and refer product-specific questions for review instead of treating a supplier message as proof. Place each objective claim beside its evidence and review date, then stop where coverage is missing.

Reconcile the public promise with its evidence

Review the entire buyer-facing offer, not just the words in isolation. Seller identity, total price, availability, delivery terms and material conditions should agree between the social item and the checkout a buyer reaches.

The CMA's unfair commercial practices guidance describes business conduct prohibited by unfair business-to-consumer trading law. A prepared script is not the final asset because production can alter it; keep the approved version and compare it with the published social item and checkout before release.

Record whether content is marketing, affiliate work or independent material in the disclosure policy. Keep the relationship and marketing label visible in every supported format. Treat the electronic commerce route as another review path, comparing the social item and checkout against the approved asset before release.

Inspect a contained release as a buyer

Run a restricted product group before widening publication. Inspect the listing from a fresh customer view and compare product, variant, stock, price and destination with the source record. A platform status alone cannot show what a buyer actually encounters there.

Record rejected items and partially applied changes, then assign an owner to the listing-error queue before expansion. Do not treat successful status as proof that all changes reached the public page accurately. The gate closes only after the customer view has been checked against the source record.

Keep remedies moving when exposure stops

Keep remedy work active after stopping new exposure. A pause can prevent further views, but it does not complete existing fulfilment, cancellations, refunds or safety reports. Name owners for open orders and customer problems, so outstanding commitments remain visible throughout.

Use the team's risk scenarios to rehearse access revocation, safe catalogue restoration and live-order protection. NCSC's response and recovery resource supports incident preparation. If personal data may have been exposed, check data protection duties before closing the incident record.

Track received, accepted, dispatched, delivered, cancelled, returned, refunded and disputed states across platform, shop, payment and fulfilment records. Reconcile differences using a stable identifier and give customer service one accurate status plus an owner for the hand-off. Keep cancellation, return, refund and dispute states visible beside delivery so exceptions remain traceable.

GOV.UK distance-selling guidance describes information, confirmation and delivery duties for covered transactions. Have a qualified reviewer apply those duties to the relevant goods, consumer contracts and consumer rights, rather than infer obligations from a generic platform status. Keep the review decision with the route record.

Pass unresolved work into the next shift

Pass unresolved work through the controlled workflow record, not a private chat or personal notebook. At each shift transfer, give the incoming owner the current state, missing evidence, next action, access and escalation route. Require acknowledgement before treating the handover as complete.

At shift change, use the team roles to pass on the live-release list, oldest order exception, unresolved listing errors, paused products, customer promises and approvals nearing expiry. For each open item, record a deputy, escalation contact and time; have the incoming person confirm system access rather than relying on an unverified message.

Keep public items scheduled to expire and credentials due for removal in the same record. At the following shift, check completion rather than assuming the task left the queue. During launch, review open errors and order exceptions each day, then analyse repeat causes weekly.

Renew approval whenever platform, checkout, category, fulfilment or measurement configuration changes. Record the changed setup and its review in the controlled workflow record; earlier approval does not cover a changed route. Resume only after the revised route has passed review, keeping operational work and release approval visible as separate decisions.