{"title":"Upgrade guide — v19 to v20","slug":"upgrade-guide-v19-to-v20","url":"https://support.storeconnect.com/articles/upgrade-guide-v19-to-v20","url_markdown":"https://support.storeconnect.com/articles/upgrade-guide-v19-to-v20.md","subtitle":null,"summary":"A plain-English overview of what changed in v20 and links to the detailed upgrade steps for e-commerce, POS, subscriptions, and payments.","type":"Release_Notes","video_url":"","keywords":null,"last_modified":"2026-08-21T07:12:35+0000","body_markdown":"v20 is a significant release with updates across e-commerce, POS, subscriptions, and payments. This guide gives you a plain-English overview of what has changed, followed by detailed upgrade steps in each subsection.\n\n## Saved carts\n\nCustomers can now save their shopping cart and return to it later. StoreConnect syncs active web carts to three new Salesforce objects: `Cart__c`, `Cart_Item__c`, and `Cart_Campaign__c`. This makes cart data available alongside your existing order and customer records for reporting, automation, and personalisation.\n\nAs part of this change, **abandoned orders are no longer created**. In v19, incomplete checkouts produced an Order record. In v20, an Order is only created after payment completes. Unfinished checkouts remain as `Cart__c` records. The automated abandoned cart job marks idle carts as abandoned by setting `Cart__c.Abandoned__c`. If you have reports, flows, or integrations built around abandoned orders, these will need updating.\n\n## Subscription renewal orders\n\nSubscription renewals can now automatically generate a Salesforce order ahead of the billing date. New fields on `Product2` control how many days before the subscription end date the renewal order should be created. New fields on `Subscription__c` track the renewal order date and the generated order. Liquid templates have new drop properties to surface renewal order data to customers.\n\n## POS enhancements\n\nv20 includes substantial updates to the StoreConnect POS:\n\n- **Quick Actions** let operators trigger common tasks from a configurable menu. Actions are defined in Salesforce using the new `Pos_Action_Group__c` and `Pos_Action_Item__c` objects.\n- **Custom Views** (`Pos_View__c`) allow you to configure what operators see on screen without a code deployment.\n- **Layout Management** (`Pos_Layout__c`, `Pos_Layout_Field__c`) is now driven by Salesforce objects, giving administrators direct control over POS terminal layouts.\n- **Returns and Refunds** have a new mechanism with improved UI, including support for initiating returns when the terminal is offline.\n- **Line item and order-level discounts** have been reworked for improved reliability.\n- **Navigation** has been updated with second-tier menus. The POS Dashboard has been renamed to Home.\n\n## Strict zone matching\n\nZones can now be individually configured as strict using the new `Zone__c.Strict__c` field. When enabled, a customer's address must exactly match the zone's criteria to qualify. Previously, strictness was a global setting.\n\n## Liquid template key renames\n\nThe internal concept of `line_item` has been renamed to `cart_item` throughout StoreConnect Liquid. This affects template snippet keys, translation keys, Liquid drop properties, and cart controller parameters. The deprecated names still work in v20 and log warnings in the Web Console. They will be removed in a future version.\n\n## New payment gateways\n\nv20 adds support for CyberSource (including express checkout), Tyro, and TouchNet. Existing gateway support has also been extended: eWay v2 now supports subscription payments, Braintree now supports Salesforce-managed payments, and both Stripe ACH and Authorize.Net ACH payments now begin as pending and poll for settlement confirmation.\n\n\n## Authentication providers\n\nv20 adds support for configuring a Generic OAuth provider and a Generic SAML provider, giving you more options for single sign-on beyond the existing named integrations.\n\n## Web console and Site Builder\n\n- Content fields and page bodies can now be edited directly from the Web Console.\n- Theme templates are searchable from the Site Builder.\n- The Web Console logs deprecation warnings in real time as your store pages are rendered, making it straightforward to identify deprecated Liquid keys that need updating.\n- A new Liquid benchmarks feature shows render times per template to help diagnose performance issues.\n\n## Upgrade steps\n\nWork through the sections that apply to your implementation:\n\n- [Upgrade guide — v19 to v20 — E-commerce](upgrade-guide-v19-to-v20-ecommerce) — applies to all stores\n- [Upgrade guide — v19 to v20 — POS](upgrade-guide-v19-to-v20-pos) — POS users only\n- [Upgrade guide — v19 to v20 — Subscriptions](upgrade-guide-v19-to-v20-subscriptions) — subscription users only\n- [Upgrade guide — v19 to v20 — Payments](upgrade-guide-v19-to-v20-payments) — if adopting a new gateway or changing payment configuration\n\n## Test your store after upgrading\n\nThis guide covers the changes StoreConnect has identified for this release. It cannot anticipate every custom Flow, integration, report, or third-party package in your org. Do not rely on this guide alone. Plan and run your own thorough testing after upgrading.\n\nAt a minimum, test every function that is critical to your business:\n\n1. Place a test order end-to-end through checkout and confirm it syncs to Salesforce correctly.\n2. Confirm payment processing works for each of your active payment providers. If you process refunds through StoreConnect, test a refund as well.\n3. If you use the StoreConnect POS, complete a test sale and confirm it syncs.\n4. If you use subscriptions, confirm renewals and payment collection work correctly.\n5. Check the Sync Error log in the StoreConnect Console for new sync errors and review your error logs.\n6. Test any custom Flows, automations, and integrations that touch StoreConnect objects.\n\nSee the post-upgrade tasks in [Managing StoreConnect upgrades](managing-storeconnect-upgrades) for the full checklist."}