Operations
Part of How to run subscription commerce operations that scale cleanly
How to run a subscription commerce operating workflow without weekly firefighting
A step-by-step method for operations leads: assign owners, a fixed cadence and clear triggers so subscription commerce work stops arriving as a surprise.
What to take away
- Unowned refunds, failed payments and address changes can turn routine subscription work into a daily queue.
- A subscription commerce operating workflow is a named owner, a fixed cadence and a written trigger for each recurring task.
- Sort work into daily, weekly and monthly rhythms before you buy more software.
- Score each task on failure cost, frequency and evidence, then staff the top of that list first.
- Write the workflow down so a new starter can run it by week two.
Map the recurring work
Recurring subscription tasks to map
- Payment retries
- Renewal notices
- Address changes
- Cancellations
- Stock checks
For each item, note who currently touches it and what triggers their action. Most teams find three or four tasks with no owner at all.
Then keep the list to what your team actually does, not what a larger retailer publishes.
Set owners and cadence
Every recurring task needs one named person, not a team. Shared ownership is how queues grow quietly.
Cadence by task type
Daily
- Payment failures
- Daily
- Dispatch exceptions
- Daily
- Stock
- —
- Complaints
- —
- Churn review
- —
- Data requests
- —
- Supplier checks
- —
- Margin reporting
- —
Weekly
- Payment failures
- —
- Dispatch exceptions
- —
- Stock
- Weekly
- Complaints
- Weekly
- Churn review
- Weekly
- Data requests
- —
- Supplier checks
- —
- Margin reporting
- —
Monthly
- Payment failures
- —
- Dispatch exceptions
- —
- Stock
- —
- Complaints
- —
- Churn review
- —
- Data requests
- Monthly
- Supplier checks
- Monthly
- Margin reporting
- Monthly
Publish the cadence where the team already looks, such as the operations board. If a task has no slot, it will drift.
Use the same cadence across fulfilment, billing and support. A hand-off is complete only when the next owner can see the status and evidence in the relevant system.
Build the trigger list
A trigger is the event that starts the task. "Payment fails twice" is a trigger. "Customer seems unhappy" is not.
Write each trigger so a new starter can act on it, naming the system and the first action.
For marketing consent and renewal messaging, the ICO's direct marketing guidance explains what counts as valid consent under PECR, which shapes how your workflow records opt-ins.
When reviewing UK consumer auto-renewals, check the Digital Markets, Competition and Consumers Act 2024 (DMCC Act) and Competition and Markets Authority (CMA) guidance. Verify which subscription provisions are in force before changing renewal or cancellation steps.
A runnable daily, weekly and monthly workflow
Use the systems your team already has as the evidence locations. Subscription and billing platforms include Stripe Billing, Chargebee, Recharge, Zuora and Paddle; support teams may use Zendesk or Gorgias; email platforms include Klaviyo and Mailchimp. Shopify or Linnworks can hold order and inventory records, ShipStation can hold shipping and tracking records, and Mintsoft is an option for warehouse or 3PL operations. These are examples, not a reason to switch platforms.
Daily
- Payments owner:Trigger: a failed-payment event or retry enters the billing queue. Check the subscription and payment event, follow the platform's configured retry and dunning process, and record the attempt and result in the billing record.
- Support owner:Trigger: a customer ticket asks for a refund, address change, pause, skip or cancellation. Verify the account, make or route the requested change under your policy, and record the action and customer response in the helpdesk ticket and subscription record.
- Warehouse owner:Trigger: the fulfilment cut-off report is ready. Match paid renewal orders to available stock, release the pick list, and flag any stock shortfall to support; keep the order and inventory records as evidence.
- Support or delivery owner:Trigger: a carrier reports a delivery exception. Check tracking, contact the carrier or customer as needed, and record the resolution in the tracking record and support ticket.
Weekly
- Finance owner:Trigger: the chargeback alert or weekly chargeback report arrives. Gather the order, payment and customer-service records for each case, submit the response through the payment provider, and log the outcome with the refund and chargeback records.
- Inventory owner:Trigger: the weekly stock and upcoming-renewal review. Compare expected renewal orders with stock, raise replenishment or allocation issues, and record decisions in the inventory system and 3PL records.
- Lifecycle or marketing owner:Trigger: the upcoming-renewal and expiring-card queue is due for review. Check that relevant notices are scheduled and that marketing messages respect recorded preferences; keep the notice and suppression report with the campaign record and the customer's preference history.
Monthly
- Operations lead:Trigger: the monthly workflow review. Check a sample of renewals, refunds, address changes, pauses, skips and cancellations against the billing and support records; assign any recurring error to an owner and update the runbook.
- Finance owner:Trigger: the monthly reconciliation. Compare billing, refunds, chargebacks and fulfilled orders, investigate mismatches, and save the reconciliation and follow-up actions in the finance records.
Cover warehouse risk
Subscription fulfilment involves lifting, packing and repetitive movement, so injury risk grows with volume.
The HSE's guidance on musculoskeletal disorders covers the workplace risks that apply to warehouse and fulfilment operations. Build a manual handling check into your monthly rhythm rather than waiting for a reportable incident.
If you use agency staff at peak, add their induction to the same list.
Track sign-up quality
Your workflow should feed acquisition, not just fix problems. If sign-ups from one channel churn faster, that is an operations signal worth acting on.
Google Ads publishes quality score guidance for search campaigns. It is a useful prompt to check whether your conversion tracking matches what the operations team sees in the billing system.
Score each task
Use a simple rubric so the team agrees on priorities. Score each recurring task out of five on each row.
What a low score looks like
- Failure cost
- Minor annoyance
- Frequency
- Quarterly
- Evidence
- Nobody can show it happened
- Ownership
- Unassigned
- Handover
- Lives in someone's head
What a high score looks like
- Failure cost
- Refunds, chargebacks or regulator contact
- Frequency
- Daily
- Evidence
- Logged with a timestamp
- Ownership
- One named person
- Handover
- Written and tested
Add the scores and rank the list. Anything scoring below ten on a total of twenty-five goes on a watch list, not the main workflow.
Write it down
The workflow only counts once it is written. Keep it to one page per rhythm: daily, weekly, monthly.
Name the owner, the trigger, the first action and where the evidence lands. Review the page each quarter and cut anything nobody has touched.
Use the daily, weekly and monthly workflow in this article as your pass-or-fail check: every recurring task should have an owner, a trigger, a first action and an evidence location.
Common questions
How long should the workflow take to run each day?
For a team under 2,000 subscribers, aim for thirty to forty-five minutes of queue review each morning. Longer usually means a trigger is unclear or an owner is missing.
Who should own the workflow?
One operations lead owns the document. Individual tasks sit with the person closest to the trigger, whether that is support, finance or the warehouse.
What if we have no operations lead yet?
Assign the role to whoever already handles escalations. Write the first version yourself, then hand it over with the trigger list attached.
How often should we revise the rubric?
Quarterly is enough. Score again after any change to payment providers, carriers or consent rules.
