Cancel immediately when service or access must stop now and the store has a clear refund, fulfillment, and data policy. Cancel at period end when the customer should retain what they already paid for while preventing the next renewal. In either case, show the exact access end date, next-charge result, refund result, and undo availability.
Key takeaways
- Stopping renewals, ending access, and refunding payment are separate decisions.
- ArraySubs Free supports immediate and scheduled period-end cancellation.
- Scheduled cancellation can be undone before execution in current behavior.
- No valid future date means the scheduled path fails safely.
- Legal and refund requirements vary by offer and jurisdiction.
Compare the two timelines
| Question | Immediate | Period end |
|---|---|---|
| Subscription status | Cancelled now | Current status plus waiting-cancellation marker |
| Future renewal | Removed now | Removed/replaced so boundary does not renew |
| Access | Can end now | Continues until effective date |
| Refund | Separate decision | Separate decision |
| Undo | Usually restoration/new subscription | Supported before execution in current ArraySubs |
Current ArraySubs customer cancellation applies to active, trial, or pending subscriptions; the same current eligibility list does not include on-hold. Admin controls can differ from the customer-facing global timing setting.
Immediate cancellation
Current helpers set the cancelled/end time to now, change status, clear waiting cancellation, retry state, and pending plan switch, and unschedule related actions. Entitlement integrations that rely on active/trial status can therefore remove access immediately.
That may fit fraud, security, abuse, a requested immediate refund, or a usage service that must stop now. It can be unfair or operationally disruptive when the customer already paid for a digital term or a physical box is committed.
Cancel at period end
ArraySubs selects the earlier valid future end date or next-payment date, records the request and reason, prevents the conflicting renewal, and keeps the existing status until execution. The customer can undo the pending cancellation before it runs.
If no valid future date exists, current code fails rather than silently cancelling now. Lifetime or malformed schedules need an explicit admin policy.
Cancellation is not a refund
Assume $30 paid July 1, cancellation requested July 10, and a July 31 boundary. A simple day-based illustration gives 21 unused days:
illustrative unused value = $30 × (21 ÷ 30) = $21
Arithmetic only—not a refund entitlement or legal conclusion.
Immediate cancellation can end access without proving $21 was refunded. Period-end cancellation can preserve the paid term without requiring an unused-time calculation in this simplified digital example. Physical goods, usage, taxes, installments, and law can require another result.
ArraySubs refund behavior has its own setting and workflow. A refund can trigger immediate cancellation, scheduled cancellation, or no cancellation. Show both state and money results.
Choose by product model
- Prepaid digital access: period end is often the clearer start.
- SaaS/license: period end for billing opt-out, with separate security suspension and data-export rules.
- Physical box: stop future cycles at a defined warehouse cutoff; resolve already-funded fulfillment separately.
- Usage/postpaid service: immediate stop of new usage can fit, while accrued amounts remain due.
- Trial: explicitly state whether cancellation ends trial access now or only prevents the first charge.
- Fixed payment obligation: contract-specific; do not present owed installments as cancel-anytime service.
Customer confirmation fields
- request time and timezone;
- effective cancellation date;
- next charge: prevented, pending, or already due;
- access/service end;
- shipment or fulfillment result;
- refund amount and status, separately;
- data export/deletion timeline;
- undo or reactivation option;
- support route and confirmation identifier.
Current U.S. negative-option context is evolving. The FTC’s 2024 amended rule was vacated and a new rulemaking process began in 2026. ROSCA remains relevant for covered online offers, while state and international rules vary (FTC Negative Option Rule page, ROSCA). Use qualified legal review.
Final recommendation
Make cancellation a three-part result: future billing, entitlement, and refund. Period-end is often clear for prepaid access; immediate is appropriate only when the product and policy justify ending now. Compare ArraySubs plans.
Frequently asked questions
Does immediate cancellation automatically refund payment?
No. In ArraySubs, cancellation state and refund behavior are separate. The customer should see the cancellation outcome and refund outcome independently.
What does cancel at period end mean?
It records the opt-out now, prevents the next renewal, preserves the current agreement until its valid future boundary, and cancels on that date.
Can a customer undo a period-end cancellation?
Current ArraySubs supports undoing a waiting cancellation before execution. The system should log who restored it and rebuild the correct future schedule.
What if a subscription has no next payment date?
Current scheduled cancellation needs a valid future end or next-payment date and fails safely without one. Use an explicit admin policy for lifetime or malformed schedules.
Is period-end cancellation always best?
No. Security, abuse, usage shutoff, immediate refunds, physical fulfillment, regulated services, and contract terms can require a different result.
Disclosure, verification, and update log
- July 2026: Verified against current ArraySubs cancellation and refund-state behavior plus current FTC/ROSCA sources. This is not legal advice.
Continue from strategy to setup
Use a recipe when the model is settled
These articles own the decision and operating model. The ArraySubs feature map and recipes cover the exact product, billing, and customer-workflow configuration.
Written by
Emran // ArrayHash
Research and practical guidance for WooCommerce subscription operators and implementation teams.
Technical review
ArraySubs Engineering Team
Reviewed against current ArraySubs code, product documentation, and the linked primary platform sources.
