Skip limits

Skip limits cap how much of their own billing a subscriber can defer by skipping deliveries. They're off by default — skipping is unlimited until you turn them on — and live on the Settings → Skip limits card.

#The two caps

• Maximum skips per subscription — the total number of times a single subscription may be skipped. Leave it blank to keep skips unlimited, or set a number (1–100) to cap them. A cap of 3 grants exactly three skips.
• Furthest a skip may move the next order — a limit, in days, on how far a skip may push the next billing date past today. Leave it blank for no limit, or set 1–365 days.

Each cap works on its own; a blank cap stays unlimited.

#How it's enforced

The caps are enforced on the server, on the shopper's self-serve skip — never decided by the model or the portal alone. When a skip would exceed a cap, it's refused cleanly before anything changes: the next billing date and the skip count stay exactly as they were. In the portal the shopper sees a plain reason — for example, "You've used all 3 skips for this subscription," or "You can't move your next order more than 60 days out."

One deliberate exception: when WallaB offers a skip to save a cancellation, that cancel-save skip is exempt from these caps — at the moment a subscriber is about to cancel, keeping them outranks one extra skip, so the offer applies even if they've reached the limit. The caps still fully bind the everyday self-serve skip button; only WallaB's cancel-save offer is exempt.

#Why cap skips

Unlimited skipping lets a subscriber defer a charge indefinitely. A sensible cap protects predictable revenue without getting in the way of the occasional skip a shopper genuinely needs — many stores can leave the caps generous, or off entirely.