May Build Summary (10.0.1)

Overview of all Features

Core POS

Price Levels Page in CMS

What it does: New page in CMS that allows you to see all levels of pricing by Product ID.

How to access: CMS Link

You can view detailed pricing for each product by selecting Price Details. This opens a new window displaying both the product information and the available prices at the product and store levels.

Learn More: Price Lookup Report

PunchOut: Use External Service from POS

What it does: provides the ability to use an external service to pass things like customer information or products into a POS.

The flow works as follows: If a command starts on the PunchOut web page, it sends data back to the POS app. For example, this can involve logging in as a customer or adding products to the cart. The POS app recognizes the data via the payload sent if the command starts. Other actions, such as navigating to the cart within the POS app, can also be managed this way.

Reach out to your CSM for more details if this is something you're interested in.

Learn More: Supporting PunchOut Webpages on POS App

Copy Special Order Product in Cart

What it does: easily make many special product orders for custom products with similar features instead of having to start from scratch for each one.

Learn More: Copying Special Forms on POS App

SPI

Delivery Date Picker

What it does: With Salesforce's SPI, merchants can integrate to support retrieving delivery or pickup dates on the POS app. The POS app calls the SPI, asking for a list of available dates. It also includes details like cart products, how they are shipped, shipping addresses (if turned on), and addresses for each item that needs to be shipped. The response provides an array of dates or an error message to be shown in the POS. Delivery and pick-up dates can be set at the order level or for individual items in the cart.

How to configure SPI: CMS Link

1. In CMS, go to Integrations > Custom Connectors.
2. Create an integration by selecting Create.
3. Under Connector Type, select "SPI".
4. Under Endpoint Name, select "DATE_PICKER".
5. Under API Endpoint, enter the URL endpoint.
6. Under Integration Type, select "HTTP_POST".
7. Under JSON Headers, enter headers to be passed.
8. Save your changes.

Learn More: Retrieving Delivery & Pickup Dates via SPI

Payments

Verifone Remote and In-Store Pay by Link

What it does: Verifone now offers Remote and In-Store Pay by Link. Work with customers from anywhere and meet them where they are.

How to configure: CMS Link

1. In CMS, go to Integrations > Payment Gateways.
2. Edit the VerifonePSDK Payment Gateway.
3. Go to Pay By Link Configuration and configure the fields:
   • Organization ID: Enter the merchant organization ID, which is unique for each store. This value can be found in your Verifone portal by going to "Administration > Organization Company and Sites". Select the company or organization's site from a table list and copy the "Organization ID".
   • Pay By Link Base URL: Enter the base URL used to construct the Pay by Link URL for making Verifone API requests. Details can be found at this link.
   • Pay By Link Expiration in Hour: Enter the expiration time for created checkout links. The minimum is one hour and the maximum is 1680 hours.
   • Token Scope ID: Enter the token scope ID to be used to tokenize card details. This value can be found in your Verifone portal by going to "Administration > Organization Company and Sites". Select the company or organization's site from a table list and copy the "Token Scope". Note, this value can only be found if an admin user is logged in.
   • Credit Card Payment Contract ID: Enter the credit card payment contract ID to be sent in API request for card configuration. This value can be found in your Verifone portal by going to "Administration > Payment Provider Contracts". Edit a contract and go to "Payment Provider Contract ID value".
   • Gift Card Payment Contract ID: Enter the gift card payment contract ID to be sent in API request for card configuration. This value can be found in your Verifone portal by going to "Administration > Payment Provider Contracts". Edit a contract and go to "Payment Provider Contract ID value".
   • 3-D Secure Contract ID: Enter the 3-D Secure Contract ID, which is needed to secure payments in European countries where it is mandated. This field is optional for all other regions. This value can be found in your Verifone portal by going to "Administration > 3DS Contracts". Select the company or organization's site from a table list and copy the "3-D Secure Contract ID".
   • Google Pay: If enabled, Google Pay can be used ‌for PBL.
   • Apple Pay: If enabled, Apple Pay can be used ‌for PBL.
4. Go to Connectivity and Authentication and configure the fields:
   • User ID: Enter user ID to be used in API request for authentication. This user ID is the admin of the merchant site organization for which pay-by links are created. This value can be found in your Verifone portal, select API Keys under Profile, and select ‌the first four letters of the API Key from the list. Copy the User ID.
   • API Key: Used in API request for authentication and created from the user ID in Verifone portal. This value can be found if creating a new API key. Copy and save the key as closing the dialogue after creating the key doesn't fully show the key again.

Learn More: Pay by Link (PBL) Overview

Other Feature Enhancements