Upgrade guide — v20 to v21 — POS

Skip this section if you do not use the StoreConnect POS.

Salesforce package changes

Review: Register_Shift_Id__c on Payment__c

v21 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.

Permissions for the new field are included in the standard StoreConnect permission sets.

1. If you use only the standard StoreConnect permission sets, no action is needed.
2. If you have custom permission sets that include Payment__c, navigate to Setup > Permission Sets and verify those sets include appropriate access to Register_Shift_Id__c.
3. Review whether Register_Shift_Id__c should be added to your Payment__c page layouts.

See Payment Object Reference for full field documentation.

Liquid template changes

Review: New outlet and register Liquid drops

POS 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.

No 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.

Behavior changes

Review: POS sync overhaul

The POS sync system has been rebuilt with cursor-based pagination, replacing the previous offset-based approach. This improves reliability and performance when syncing large data sets.

The previous 72-hour window that limited order retrieval in the POS has been removed. The POS now retrieves orders based on cursor position rather than a time window.

No configuration changes are required. After upgrading, monitor your first full sync to confirm it completes without errors.

Action required: ZippayAu replaces Zippay v1

The 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.

1. Contact your ZippayAu account manager to confirm your credentials are compatible with the ZippayAu API.
2. In the StoreConnect Config app, update your Zippay payment provider configuration to use the ZippayAu integration.
3. Test a Zippay transaction at the POS to confirm the new integration is working before going live.

If you do not use Zippay, no action is needed. See Zip Pay Payment Provider for configuration documentation.

Review: Register auto-lock

v21 adds configurable auto-lock for POS registers. A register can be set to lock automatically after a period of inactivity, when the device locks, or both. Locked registers require PIN re-entry before use.

No configuration is required for existing behaviour to continue. If you want to enable auto-lock, configure the inactivity timeout or device lock setting per register.

See Configure register auto-lock for setup instructions.

Review: Remote customer record search

The POS now supports real-time customer record lookup from Salesforce, rather than relying solely on the local IndexedDB cache. This improves search results for customers who have not yet synced to the device.

No configuration is required. If you maintain custom POS views or flows that involve customer lookup, test them after upgrading to confirm behavior is as expected.