July Build Summary (9.2.1)

Overview of All Features

Analytics/Reporting

Sales Reporting Terms Defined

What it does: Check out our glossary of terms seen in CMS and App reports. There you can find definitions and calculations for metrics like GMV, Order Count, Net Sales, Taxes from Gross Sales, and so on

Learn More: Sales Reporting Glossary of Terms and Definitions

Associate Sales Attribution Report on POS and CMS

What it does: Point of Sale's Sales Attribution report allows merchants to predict commissions and measure performance. This comprehensive report is accessible on both the POS app and CMS. It presents a concise summary of sales and returns attributed to each sales associate, allowing merchants to view insights into their performance. The attributed sales ‌vary from the sales where the associate completed the transaction.

How to access in CMS: Enable Store Associate Sales Attribution

How to configure in the App:

1. In CMS, go to Layouts > Layout Templates > Hamburger Menu.
2. Edit an existing menu or create one.
3. Using the deep link picker, go to Store Associate > Associate Sales Attribution Report.
4. Set and save the changes.
5. Access the report via the deep link you set up.

Associate Login Report

What it does: The associate login report provides a reference to log in information for all registered store associates in the CMS and POS app.

Note In the CMS, the report displays the store ID while the POS app shows data only for the associate's store.

How to access in CMS: Access Associate Login Report in Point of Sale

How to configure in the App:

1. In CMS, go to Layouts > Layout Templates > Hamburger Menu.
2. Edit an existing menu or create one.
3. Using the deep link picker, go to Store Associate > Associate Login Report.
4. Set and save the changes.
5. Access the report via the deep link you set up.

Core POS

UI Enhancement to Product Cell in Return Flow

What it does: For app builds 9.1.2 and greater, the return product checkbox is replaced by a switch. Additionally, the user is prompted for the number of returns if a product's quantity is more than one.

Learn more about returns and exchanges here.

Return and Exchange Policy Approval

What it does: With POS Builds 9.2.1 or greater, you now have the ability to require manager approval for returns or exchange transactions regardless of whether they fall within the return window or not. Previous versions allow the merchant to configure manager approval only for returns outside the return window.

Learn more about store associate approval policies here.

How to configure: https://labs.predictspring.com/cms/associate-policies

1. Select Create on the top-right of the approval policies page.
2. Select All Returns, Exchanges & Edit Orders
3. Select Approving Roles that can approve this policy (for example Store Associate, Senior Associate).
4. Select Save.

Auto Suspend Cart

What it does: With builds 9.2.1 and later, you not only can manually suspend and save a cart; you can have a cart auto-suspended either after the associate logs out, if there are contents in the cart or after the app times out.

Learn more

Note Auto-Suspend won't function while in offline mode.

No Profile, No Card, No Receipt Returns Refresher + Reason Code

What it does: No Profile, No Card, No Receipt Returns feature allows a return of an item without a purchase receipt or even customer profile details.

The returns and exchanges supported as part of No-Receipt Returns are listed:

• Returning an item or multiple items (that is, pure return)
• Returning item(s) along with a purchase where a customer still gets a refund
• Returning item(s) along with a purchase where a customer makes a payment
• Exchanging (even exchange) an item or multiple items
• Exchanging (even exchange) item(s) with purchase

To create NRR Price Correction Reason Codes:

1. In CMS, go to Store Management > Reason Codes.
2. Select Return Price Correction.
3. Select Create in the upper right and fill out the required fields.
4. Save your changes.

Note The Reason Code is reported in the Electronic Journal and TLogs along with the before-and-after price corrections.

Receipts

Enhancements to Receipt Tags and How they Render in Layouts

What it does: Starting with POS version 9.2.1, if the "=IF" function returns an empty string, the receipt line is truncated, thus removing the empty row where the "=IF" function result ‌has been.

How to configure: https://labs.predictspring.com/cms/layouts (Learn more about Receipt Layouts here)

For Example: In a scenario if your customer pays with cash and you have Gift Card Remaining Balance, Cash Tendered Amount, and Cash Change Amount configured in your template, only Cash Tendered Amount and Cash Change Amount shows.

Learn More: Customize Receipts Using Functions

Clienteling SPI

Applying Customer Groups to Promotions

What it does: Create targeted promotions tailored for specific customer groups.

How to configure the layout:

1. In the merchant's external system, configure Salesforce's Clienteling SPI.
2. In CMS, configure a Customer Sign-up layout by going to Layouts > Layout Pages.
3. Add a new field for Customer Groups.
4. Configure the rest of the fields.

How to configure the customer group-specific promotion:

1. In CMS, create a promotion by going to Promotions.
2. Select the type of promotion.
3. Under Basic Promotion Information, enter the required fields.
4. Under Promotion Configuration, configure the promotion discounts.
5. Go to Customer and create a Customer Group.
6. Fill out the rest of the fields.
7. Save the changes.

How it functions:

• If signing up a new customer in the POS app, the value entered in the Customer Group field will be saved to Salesforce’s Backend.
• If a customer group-specific promotion is successfully applied to an order, and the customer completes the checkout process, the customer's group attributes are automatically logged in the TLogs and Exports.

Learn More: Apply Customer Groups to Promotions

Validate Customer Profile Address from SPI

What it does: If the CRM isn't complete or doesn't have a valid shipping address, Salesforce can check the customer's address before an order is placed.

How to configure:

1. In the merchant's CRM system, configure the Clienteling SPI.
2. Configure the endpoints of the merchant's third-party integration in CMS by going to Integrations > Custom API Connectors.
3. In CMS, go to Apps > All.
4. Edit the app configuration(s) to have address validation.
5. Go to Modules > Settings.
6. Turn on Enable Address Verification.

Learn More: Validating Customer Profile Address on Cart

Other Feature Enhancements