
Offer Design
Part of Subscription software selection
Testing pause, skip and swap workflows
Test whether pause, skip and swap controls change the intended charge, order and packing instruction.
Test each control against the delivery it is meant to change. Compare the customer confirmation with the subscription, next charge, order and packing instruction. A button appearing in an account does not prove it changed the intended parcel.
Prepare the cases
Use authorised test accounts and a safe process that keeps test orders out of live dispatch. Record the starting product, price, next charge, next delivery and change cutoff. Check the installed app, portal settings and plan tier.
For each available action, test a delivery still open to change and one already being processed. Add a prepaid delivery due without a new charge if the offer uses prepayment.
Test skip
From the customer account, skip the displayed delivery. Capture the date and contents named in the confirmation.
Check whether the affected charge and order schedule change as promised, and whether the following active delivery remains visible. If several subscription items may share a shipment, test whether the action applies to one item or the whole order. Record what happens when the cutoff has passed.
Test pause and resumption
Pause the plan and capture the stated effective date, any restart date, and the status of charges and orders already processing. Inspect any already paid or released parcel separately.
Resume the plan. Compare the first new charge and delivery with the displayed restart date, product, price and frequency. If the system offers a timed pause, check that the customer can see when it ends.
Test swap
Select an eligible replacement. Before saving, record its variant, quantity, price and the first order the account says will change.
Afterwards, inspect both the recurring subscription and the order sent to packing. Also try an unavailable product and a request after cutoff. The response should make clear whether the swap was rejected, deferred or applied to a later delivery.
Decide what passed
For each case, retain the starting state, action, customer confirmation and resulting contract, charge, order and packing output. Pass the case only when those records agree with the promise. If staff must intervene, record who acts, by when and how the customer learns which parcel changed.
Key Testing Metrics
- Starting state retained
- Yes/No
- Customer confirmation accurate
- Yes/No
- Contract, charge, order, packing match promise
- Yes/No
- Staff intervention required
- Yes/No
- Customer notified of change
- Yes/No


