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.

Review: Pricebook_Id__c on Outlet__c

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.

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

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

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

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.