{"title":"Upgrade guide — v21 to v22 — Subscriptions","slug":"upgrade-guide-v21-to-v22-subscriptions","url":"https://support.storeconnect.com/articles/upgrade-guide-v21-to-v22-subscriptions","url_markdown":"https://support.storeconnect.com/articles/upgrade-guide-v21-to-v22-subscriptions.md","subtitle":null,"summary":"Upgrade steps for subscription users moving from v21 to v22, covering the corrected price for fixed-term subscriptions paid upfront, renewal order charging, guest payment of renewal orders, and card capture for subscriptions sold at the POS.","type":"Release_Notes","video_url":"","keywords":null,"last_modified":"2026-10-22T05:03:23+0000","body_markdown":"Skip this section if you do not use StoreConnect subscriptions.\n\nThe guide assumes you are on the latest v21 website release. Changes that already shipped in v21 patch releases are not repeated here.\n\n## Behavior changes\n\n### Review: Fixed-term subscriptions paid upfront are charged their term once\n\nThis applies only if you sell a product that is both a fixed-term subscription and paid upfront. Previously the line was priced as though the upfront period commitment and the fixed term compounded, so a 12-term product committing 6 periods was charged for 72 terms. A fixed-term line paid upfront is now charged its full term and nothing more, and renewal pricing divides by the same count the cart used.\n\n1. Place a test order for each fixed-term, paid-upfront product and confirm the cart total matches the price you intend.\n2. If customers were overcharged on earlier orders, review those orders and decide whether to refund the difference.\n\n### Review: Renewal order items are created before charging\n\nRenewal order items are now created before the subscription is charged, and a partially paid renewal order is charged its outstanding balance rather than the full amount. If you have Flows that populate renewal orders, confirm after upgrading that a renewal produces one subscription line.\n\n### Review: Plan-change orders complete like renewal orders\n\nWhen a customer changes plan, the plan-change order is now finalized and completed the same way a renewal order is, so order completion automation, confirmation emails, and downstream syncs run for it. If you have Flows on order completion that should not fire for plan changes, review them.\n\n### Review: Pay Later subscriptions keep their setting after a one-off payment\n\nA payment on an existing subscription's order through the payment link or a Salesforce payment no longer switches a Pay Later subscription back to automatic charging. Only a charge that saves a reusable payment token updates the subscription's payment details.\n\n### Review: Customers can pay a renewal order without signing in\n\nWhen the `subscriptions.guest_renewal_payment_enabled` store variable is `true`, a pending renewal order can be paid in full through the additional payment page without logging in, for example from a link in a renewal email. The payment advances the subscription the same way an automated charge does and never changes the stored payment token. The variable is off by default, so nothing changes until you set it.\n\n### Review: Subscriptions sold at the POS capture a card\n\nThis applies only if you sell subscription products at the POS. A cart containing a subscription or save-card product now requires an identified customer. When a Square Terminal is paired, the POS inserts a **Save card for subscription** step at checkout; otherwise a web page is offered to capture the card. The captured card is verified against the gateway, stored as a `Payment_Method__c` record, and linked to the order's subscriptions. Preauthorize-only products cannot be sold at the POS. Recurring billing is unchanged.\n\n### Review: Saved payment methods in the account area\n\nCustomers on Stripe, Stripe ACH, or Square can save a card in the account area. Saved methods are not bound to a subscription for renewal. Renewals continue to use the subscription's own stored token and provider. See [Payment methods](payment-methods)."}