Offer Design
Subscriber self-service
Plan a subscriber account that shows the next order, explains change deadlines and makes skip, pause, edit and cancellation outcomes clear.
A subscriber account should show what happens next and let customers make the changes available to them, with a clear result. Start with the next charge or shipment, the order it covers, and the deadline for changing it. Label billing, dispatch and delivery dates separately; they describe different events.
Make sign-up and first-order status explicit
Explain when a customer enters an ongoing subscription, what action starts it and whether a first order or charge is already in progress. This matters when sign-up includes account access, payment details or meal selection. A customer should not have to infer subscription status from a later payment notification or delivery.
Keep the sign-up explanation and account status aligned. The ACCC says traders must clearly communicate when consumers are signing up for a subscription, how they can cancel and how to avoid being charged. Put that information where the customer makes the relevant choice, and show the resulting status in the account.
Show the next order in context
Show the products, quantities, expected charge, shipping address and known dispatch or delivery information. If the plan is prepaid, show scheduled shipments separately from the next renewal charge. Place the change deadline beside the order it affects, with a time zone where timing matters. Once an order is being processed, explain which changes can still affect it and which will apply later.
Explain each choice before confirmation
| Choice | What the customer needs to know |
|---|---|
| Skip | Which order is skipped and what remains scheduled. |
| Pause | When future charges and orders stop, and how the plan resumes. |
| Change a product or quantity | Which order receives the change and what it will cost. |
| Update an address or payment method | Whether the update reaches an order already being processed. |
| Cancel | What happens to future renewals and any order or prepaid shipment already scheduled. |
Describe available changes—such as skipping, pausing, editing or cancelling—only where offered, and state their effect on the next order and charge.
After an action, show the revised order or subscription state and give the customer a matching confirmation. A successful click should not leave an unchanged next charge without explanation. For prepaid plans, explain how changes affect any shipments already scheduled.
Provide a clear route when self-service ends
If an action cannot be completed in the account, explain the limit and provide a direct way to resolve the affected order. Keep cancellation findable even when pause or skip is offered.
Keep account and support answers consistent
Use the same explanation of a control and its consequences in the account, help content and assisted support. If these channels give different answers about whether a cancellation or change took effect, customers cannot reliably tell what will happen next. Keep the customer-facing wording simple, and put the action they need to take before background policy detail.
Give each help article an owner and review it regularly, with an expiry point for content that may become outdated. Feedback from customers, agents and chatbot use can also reveal where people are getting stuck or receiving inconsistent answers.
Make the handover to support clear when an account cannot complete an action. Define when self-service should stop, connect the customer with an appropriate person and pass along useful context, so they do not need to start the explanation again.
Test cancellation claims against the outcome
On 16 December 2025, the ACCC announced separate Federal Court proceedings against HelloFresh and Youfoodz over alleged subscription practices. The ACCC alleged that customers who cancelled online before the first-delivery cut-off could still be charged and receive that first order.
The ACCC alleged that many customers could only stop the first delivery by speaking with a customer service representative, despite being told they could cancel through online account settings. It also alleged that Youfoodz told some customers their first delivery was cancelled and they would not be charged when that was not the case. These allegations show why a confirmation must reflect the actual result, not just the action the customer attempted.
The ACCC alleged that 62,061 HelloFresh customers and 39,408 Youfoodz customers were charged despite cancelling before the specified first-order cut-off. The alleged conduct occurred from 1 January 2023 to 14 March 2025 for HelloFresh, and from 1 October 2022 to 22 November 2024 for Youfoodz. Treat these as allegations, not findings, and use the underlying issue as a check on whether account wording matches the customer's outcome.
Key Dates in ACCC Allegations Against HelloFresh and Youfoodz
- 1January 2023 — HelloFresh alleged subscription misconduct begins
- 16December 2025 — ACCC announces Federal Court proceedings against HelloFresh and Youfoodz
- 14March 2025 — HelloFresh alleged misconduct ends
- 1October 2022 — Youfoodz alleged subscription misconduct begins
- 22November 2024 — Youfoodz alleged misconduct ends
ACCC Allegations: Number of Customers Affected
- 62,061HelloFresh customers charged despite cancellation
- 39,408Youfoodz customers charged despite cancellation
In this guide
- Designing clear pause and skip optionsExplain which order a skip affects, what a pause stops, when changes take effect and how subscribers resume.
- Letting subscribers change products without contacting supportSet eligible product swaps, preview the actual next charge and confirm which order will receive the replacement.
- Showing the next billing and delivery datesLabel the next charge, change deadline, dispatch and estimated delivery separately, including for prepaid and skipped orders.
- Testing subscription cancellation for unnecessary frictionAudit cancellation against checkout promises, cutoffs, queued charges and prepaid shipments, then verify the actual result.
