{"title":"Upgrade guide — v20 to v21 — POS","slug":"upgrade-guide-v20-to-v21-pos","url":"https://support.storeconnect.com/articles/upgrade-guide-v20-to-v21-pos","url_markdown":"https://support.storeconnect.com/articles/upgrade-guide-v20-to-v21-pos.md","subtitle":null,"summary":"Upgrade steps for POS users moving from v20 to v21, covering register shift tracking, new Liquid drops, sync changes, and the ZippayAu migration.","type":"Release_Notes","video_url":"","keywords":null,"last_modified":"2026-08-21T07:12:35+0000","body_markdown":"Skip this section if you do not use the StoreConnect POS.\n\n\n## Salesforce package changes\n\n### Review: Register_Shift_Id__c on Payment__c\n\nv21 adds `Register_Shift_Id__c`, a lookup field, to `Payment__c`. This field links each POS payment to the register shift during which it was processed, enabling end-of-shift reconciliation and reporting.\n\nPermissions for the new field are included in the standard StoreConnect permission sets.\n\n1. If you use only the standard StoreConnect permission sets, no action is needed.\n2. If you have custom permission sets that include `Payment__c`, navigate to **Setup \u003e Permission Sets** and verify those sets include appropriate access to `Register_Shift_Id__c`.\n3. Review whether `Register_Shift_Id__c` should be added to your `Payment__c` page layouts.\n\nSee [Payment Object Reference](payment-object-reference) for full field documentation.\n\n\n### Review: Pricebook_Id__c on Outlet__c\n\n`Pricebook_Id__c` is a new lookup to `Pricebook2` on `Outlet__c`. This field assigns a specific pricebook to an outlet, allowing outlet-level pricing that is separate from the store default.\n\nPermissions for the new field are included in the standard StoreConnect permission sets.\n\nReview whether any of your outlets should use a dedicated pricebook and update `Pricebook_Id__c` accordingly. If you do not need outlet-level pricebook assignment, no action is required.\n\n\n## Liquid template changes\n\n### Review: New outlet and register Liquid drops\n\nPOS Liquid templates now have access to `outlet` and `register` drops, which expose properties of the current outlet and register to template logic and custom views.\n\nNo changes to existing templates are required. Review this if you maintain custom POS Liquid templates and want to use outlet or register data in your views.\n\n\n## Behavior changes\n\n### Review: POS sync overhaul\n\nThe POS sync system now syncs the most recent records first, then fills in older records in the background. Previously, sync ran oldest-first, meaning a fresh device or resync would not surface recent orders until all historical data had been pulled through.\n\nNo configuration changes are required. After upgrading, monitor your first full sync to confirm it completes without errors.\n\n\n### Action required: ZippayAu replaces Zippay v1\n\nThe legacy Zippay v1 API integration has been removed and replaced with ZippayAu. If your POS uses Zippay as a payment method, the existing v1 configuration will not work after upgrading to v21.\n\n1. Contact your ZippayAu account manager to confirm your credentials are compatible with the ZippayAu API.\n2. In the StoreConnect Config app, update your Zippay payment provider configuration to use the ZippayAu integration.\n3. Test a Zippay transaction at the POS to confirm the new integration is working before going live.\n\nIf you do not use Zippay, no action is needed. See [Zip Pay Payment Provider](zip-pay-payment-provider) for configuration documentation."}