Do we need multi-frequency subscription logic (weekly + monthly on the same product), and which app actually supports it well?
Shopify's free Subscriptions app supports multiple delivery frequencies on one product: a single plan carries several frequency-and-discount options, and one product accepts more than one plan (per Shopify's Help Center, September 2026). Frequency units run weekly, monthly and yearly. Paid platforms differ on portal depth and retention logic, not on whether one product offers two cadences (Deploi assessment, September 2026).
Set it up natively first
- Install Shopify Subscriptions from the App Store. Free, first-party, 3.7 stars across roughly 807 reviews (verified on the listing and its reviews page, September 2026).
- Create a subscription plan and set the first delivery frequency, choosing weekly, monthly or yearly.
- Click "Add option" to add the second frequency to the same plan, with its own discount. This is the step most teams miss, and the reason they conclude native cannot do it.
- Set the discount type per option: percentage off, amount off, or fixed price. Different cadences usually want different incentives; weekly at the same discount as monthly trains subscribers to over-order and then pause.
- Add the plan to the product in the admin. A product accepts more than one plan, so a second plan works when the two cadences need separate names, pricing logic or product sets.
- Confirm the theme renders the selector. Native purchase options need an Online Store 2.0 section-capable theme; older themes need the block added or a section built. This is the step that consumes real hours.
- Test both cadences end to end, including pause and skip from the customer account, and confirm recurring shipments pick the rate you expect. After the first delivery, recurring shipments default to the least expensive available shipping method (per Shopify, September 2026), a real problem for a weekly perishable program.
No plan gate here. Multi-frequency subscriptions run on every Shopify plan. Plus is not required, which is worth stating because the assumption costs evaluations.
Do you actually need it?
Two cadences on one product earn their keep when consumption genuinely varies by household or account size: coffee, pet food, supplements, cleaning refills. They cost you when the second cadence exists only because a competitor offers it: every extra option on the selector is a decision the shopper has to make before buying, and the weekly tier usually cannibalizes monthly rather than adding subscribers.
The honest test is whether you can name the segment that needs weekly. If the answer is a product category rather than a customer, one cadence with a skip function usually outperforms two.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Multi-frequency is a merchandising decision that teams keep buying as a platform feature. Native has supported it for a while; what's missing is usually a selector that makes the choice legible.
- What we’ve seen: Across five PDP subscription purchase-option builds, the cadence selector was the highest-leverage surface every time, and the most common defect was a theme section that rendered options in the order the API returned them rather than in the order a shopper reasons about.
- Times we’ve shipped this: 5 builds delivered.
- What it takes: roughly 46 hours of scoped work for native subscription purchase options on the PDP (directional Deploi estimate from a small sample of engagements, not a measured average).
- What this page adds: the exact native mechanism for two cadences on one product, and the shipping-rate default that breaks weekly programs.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-13.
Where we worked this out
Our decision records