--- schema_version: "1" id: 66d55230cc8401302a769e1c86d610d615b32e98f036538d919f390fbf5618bb title: January Build Summary (10.6.1) collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/rt_releases_bfs_10_6_1.md canonical_url: https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 75803b69a3e99c983d2ee69e8795d65034b0d76b94c5112ef84152da5a86ea1d description: Build summary for Modern POS version 10.6.1, including what new features and changes it contains. Version 10.5.1 was an internal-only release for work done during code freeze, intentionally skipped number for public release 10.6.1. Access all new features and enhancements in 10.6.1. products: - Commerce release: "264" --- # January Build Summary (10.6.1) Build summary for Modern POS version 10.6.1, including what new features and changes it contains. Version 10.5.1 was an internal-only release for work done during code freeze, intentionally skipped number for public release 10.6.1. Access all new features and enhancements in 10.6.1. | Feature | Benefit | | --- | --- | | **Analytics/Reporting** |   | | [POS Sales Reports: Filter by Order Type](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) | Enables filtering by order channel (in-store, endless aisle, mixed cart, and BORIS) in POS sales reports | | [Log Manager Override IDs in Electronic Journal (EJ)](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) | Captures manager overrides in the EJ for reporting | | **Core Platform** |   | | [Audit Log Improvements](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) | Enhanced audit logs now support scheduled exports, additional filters, and more detailed event logging, including login/logout events | | [Configuration Flag for Blocking Returns](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) | New flag allows merchants to control whether returns are permitted in the POS app | | [Replace Back Button with "X" for Webviews](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) | Webview navigation improved by replacing the back button with an 'X' | | [No Receipt Returns (NRR) Search Layout](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) | Merchants can create and customize NRR Search layouts | | [New Transaction Types for EJ](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) | Introducing two new transaction types in the EJ for transaction discounts and if a till from the previous day is used | | **EJ/TLog/JSON Export** |   | | [Support EJ Exports on Hourly Schedule](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) | Merchants can now schedule EJ exports on an hourly basis | | **Integrations** |   | | [Phase 1 Synchrony: Card Present with Finance Tender](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) | Supports Synchrony cards for financing transactions in a card-present scenario | | **Payments** |   | | [Permit Clutch Gift Cards to Be Processed Without a PIN](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) | New setting allows merchants to specify whether PINs are required, optional, or not needed for Clutch gift card transactions | | [Ability to Support Remote Pay by Link in Deposit Scenarios](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) | Pay by Link is now supported for remote deposits via the multitender screen | | **Returns/Refunds/Exchanges** |   | | [Start Return from Order History](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) | Enhanced ‌support for returns directly from Order History | | **Other** |   | | [Various](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_6_1.htm&release=264.0.0&type=5) |   | ## Analytics/Reporting ## POS Sales Reports: Filter by Order Type What it does: Permits filtering by order channel (in-store, endless aisle, mixed cart, and BORIS) in POS sales reports. This helps store teams look at sales and returns by channel. This gives them better information about how customers act, how they store their items, and how well they run their businesses. ![The Filter window for order types in the POS app.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_releases_bfs_pay_filter.JPG) How to configure in CMS: 1. In CMS, edit a layout or hamburger menu. 2. Using the deep link picker, search and add these links: - **Store Associate > Reconciliation Report** - **Reporting > Detailed Sales Report** 3. Set and save your changes. Learn more: [View Payment Reconciliation Report](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_reports_payment_reconciliation_report.htm&release=264.0.0&type=5 "Confirm the accuracy of financial data and identify inconsistencies among the Retail Cloud order amount, the amount requested to the payment gateway, and the amount collected by a processor.") , [Detailed Sales Report](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_reports_detailed_sales_report.htm&release=264.0.0&type=5 "Use the Detailed Sales report to see details related to sales, refunds, registers, and safes on the POS app.") ## Log Manager Override IDs in Electronic Journal (EJ) What it does: Takes IDs of managers who override in the EJ for reporting. This helps prevent losses for returns, discounts, and other approval processes. How to configure in CMS: No configuration is needed Learn more: [View and Edit Electronic Journal Reports](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_reports_electronic_journal_overview.htm&release=264.0.0&type=5 "Customize filters for transaction research and record store transactions in Retail Cloud.") ## Core Platform ## Audit Log Improvements What it does: We've enhanced Audit Logs in CMS with scheduled exports, additional filters, and more detailed event logging, including login and logout activities. These improvements permit merchants to see and control more of the system. This makes it easier to track user actions, make sure they follow the rules, and fix problems faster. Scheduled exports can also simplify reporting, while additional filters help pinpoint specific events for improved security and operational oversight. How to access and filter Audit Logs in CMS: 1. In CMS, go to **Audit Logs** in the left-hand menu. 2. Under **Resource Type**, select the type of resource (for example feed). For a complete list and detailed descriptions of all resource types, refer to [Resource Type](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_modules_audit_logs.htm&release=264.0.0&type=5). 3. Under **Action**, select the action performed on the resource (for example created). 4. Under **User Role**, select the CMS role (for example CMS Admin) assigned to the user who performed the action for the specified record in the audit log. 5. Under **IP Address**, enter the IP address of the user who performed the action. 6. Under **User ID(s)**, enter CMS user IDs associated with the actions you want to review. You can input multiple user IDs to filter records for specific individuals or teams. 7. Configure the **Date Range** and time zone to narrow down the results to a specific time. ![Configuring Resource Types in Point of Sale CMS.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_releases_bfs_audit_logs.png) How to export Audit Logs in CMS: 1. In CMS, go to **Feeds > Export Jobs**. 2. Select **+**. 3. Select **Audit Log Data Export**. 4. Configure the fields by referring to this [article](https://help.salesforce.com/s/articleView?id=commerce.rt_adv_config_data_feeds_manage_export_jobs.htm&release=264.0.0&type=5 "Use export jobs to extract data from Point of Sale by using Secure File Transfer Protocol (SFTP). Configure and schedule these jobs in CMS to automate data extraction, and monitor their progress in the Export Logs for timely, efficient data retrieval."). ![The Audit Log Data Export settings in Point of Sale CMS.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_releases_bfs_audit_log_data_export.png) Learn more: [Track Changes in Point of Sale CMS with Audit Logs](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_modules_audit_logs.htm&release=264.0.0&type=5 "Track who modified critical configurations in Point of Sale CMS to areas such as app configurations, layouts, and server settings.") ## Configuration Flag For Block Returns What it does: A new flag permits merchants to decide if returns are allowed in the POS app. This permits them to enforce store-specific return policies, reduce fraud risk, and improve operational control. Merchants can restrict returns during certain periods or promotional events, improving policy control and reducing unauthorized returns. How to configure in CMS: Returns can be turned on in two locations within CMS: the Returns Policies configuration and store settings. These settings are linked, so turning one on automatically turns on the other. 1. Returns Policy 1. In CMS, go to **Store Management > Return Policy Configuration**. 2. Verify **Block Returns (blockReturns)** is turned off. If turned on, returns can't be initiated on the POS app, resulting in the error: "`Returns are not supported per store policy. Reach out to your system admin if needed`." ![The Return Policies setting in Point of Sale CMS](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_releases_bfs_return_policies.png) 2. Store Setting 1. In CMS, go to **Store Management > Store Settings > OMS**. 2. Expand **Advanced**. 3. Verify **Block Returns (blockReturns)** is turned off. If turned on, returns can't be initiated on the POS app, resulting in the same error: "`Returns are not supported per store policy. Reach out to your system admin if needed.`" ![The Store setting for blocking returns in Point of Sale CMS.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_releases_bfs_returns_store_settings.png) Learn more: [Returns & Exchanges in Point of Sale](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_returns_exchanges_overview.htm&release=264.0.0&type=5 "Shoppers can return and exchange products in the POS app. Exchanges are defined by any return transaction that also includes a sale.") ## Replace Back Button with 'X' for Webviews What it does: We've updated the UI of webviews by replacing the back button with an 'X.' Previously, selecting the back button caused any work done in the webview to be lost. This update establishes a smoother transition between the webview and native POS app, preserving data and enhancing the user experience. ![A mocked webpage on the POS app that shows PunchOut tiles.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_pos_settings_punchout_launch_pos_app.png) How to configure in CMS: No configuration is needed Learn more: [Supporting PunchOut Webpages on POS App](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_settings_punchout_webpages.htm&release=264.0.0&type=5 "Integrate web-based workflows, like adding custom products, directly into store transactions using the Point of Sale (POS) app. Launch preconfigured web pages from the POS app to securely pass data and trigger actions via URL parameters. The POS app receives a message upon completion, which streamlines tasks such as customer login and cart navigation, enhancing the in-store shopping experience.") ## No Receipt Return (NRR) Search Layout What it does: Provides flexibility in configuring the UI, allowing merchants to customize their NRR experience How to configure in CMS: Create a layout and assign it to an app configuration. 1. Create Custom NRR Layout 1. In CMS, go to **Layouts > Layout Pages**. 2. Select **Add From Template**. 3. Select **No Receipt Returns Search**. 4. By default, the NRR layout template includes the deep links for order filtering: - **Order Search by Credit Card** - **Order Search by Customer** - **Order Search by Order Information** - **Order Search by Product**\* 5. \* If the Order Search by Product deep link is configured on the custom layout, No Receipt Returns — Turn on **Search by Product** to process returns. ![The No Receipt Return deep link configuration in Point of Sale CMS.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_releases_bfs_nrr_layout.png) 2. Assign Custom NRR Layout 1. In CMS, go to **Apps**. 2. Edit the app configuration that supports NRR. 3. Go to **UI > Search Layouts**. 4. Under **No Receipt Return Search Layout**, select the layout you've created. 5. Save your changes. Learn more: [No Profile, No Card, No Receipt Returns (NRR) in POS](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_returns_nrr_overview.htm&release=264.0.0&type=5 "Allow returns for customers who don’t have a purchase receipt or a customer profile. No Profile, No Card, No Receipt Returns (NRR) in Point of Sale are performed at the lowest historical price and only if the returning item is still available in the system.") ## New Transaction Types for EJ What it does: Introducing two new transaction types in the EJ for transaction discounts and if a till from the previous day is used ![The Electronic Journal filters in Point of Sale CMS.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_releases_bfs_ej_filters.png) How to configure in CMS: No configuration is needed Learn more: [View and Edit Electronic Journal Reports](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_reports_electronic_journal_overview.htm&release=264.0.0&type=5 "Customize filters for transaction research and record store transactions in Retail Cloud.") ## EJ/TLog/JSON Export ## Support EJ Exports on Hourly Schedule What it does: Merchants can now schedule EJ exports on an hourly basis, reducing file size and improving efficiency via SFTP. This can help mitigate issues related to connection timeouts, network disruptions, and bandwidth limitations if transferring large EJ files. ![The Electronic Journal schedule settings in Point of Sale CMS.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_releases_bfs_ej_export_logs.png) How to configure in CMS: 1. In CMS, go to **Feeds > Export Jobs**. 2. Select **+** and select **Electronic Job**. 3. Under **Schedule**, check **Repeat** on internal. 4. Select the hourly cadence. Learn more: [Configure and Manage Export Jobs](https://help.salesforce.com/s/articleView?id=commerce.rt_adv_config_data_feeds_manage_export_jobs.htm&release=264.0.0&type=5 "Use export jobs to extract data from Point of Sale by using Secure File Transfer Protocol (SFTP). Configure and schedule these jobs in CMS to automate data extraction, and monitor their progress in the Export Logs for timely, efficient data retrieval.") ## Integrations ## Phase 1 Synchrony: Card Present with Finance Tender What it does: Point of Sale's POS app, in combination with the Adyen terminal, supports the recognition of Synchrony cards and enables financing transactions. During checkout, if a customer chooses to pay with their Synchrony PLCC and the card is present, the store associate can process the payment. If the order total is more than a certain amount, the store associate can offer financing. The customer signs an electronic disclosure and financing contract. ![A tablet displays a payment option to proceed, including selecting a payment option for deferred interest financing.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_adv_config_3p_int_finance_synchrony_pos_pay_method.png) How to configure in CMS: 1. In CMS, go to **Store Management > Store Settings > Payment**. 2. Expand **Advanced**. 3. Select the pencil icon next to **Payment Terminal Financing Configuration (cardAcquisitionSettings)**. A window opens, allowing you to define the rules for promotional financing options based on the card acquisition response. 4. Turn on "**Enable Card Acquisition**" to activate the card acquisition for each card swipe or insertion before payment. 5. Under **Financing Rules**, specify whether to use "**Synchrony via Adyen Terminal**" for cards with a PAN matching a specified BIN range (for example, the issuing bank's range for Synchrony cards). If no BIN range is specified, the POS app accepts all types of Synchrony cards. 6. Under **Set Order Rules** for Applicable Finance Code, specify the finance code to use for each order total range. This code is passed to the terminal for preauthorization of Synchrony financing and determines the APR for the applicable finance option. ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_important.png) Important Set at least one order total rule. Without it, the POS app won't present a financing option, as the finance code is required based on the order total. 7. Under **Finance Terms and Conditions**, enter the terms and conditions that the customer sees during the card acquisition process. Learn more: [Set Up Processing of Synchrony Credit Card Purchases using Adyen](https://help.salesforce.com/s/articleView?id=commerce.rt_adv_config_3p_int_finance_synchrony.htm&release=264.0.0&type=5 "The POS app, in combination with an Adyen terminal, supports the recognition of Synchrony cards and enables financing transactions. During checkout, when a customer chooses to pay with their Synchrony PLCC and the card is presented, the store associate can process the payment. If the order total meets a set threshold, the store associate can offer financing, which requires the customer to sign an electronic disclosure and financing contract. The threshold, electronic disclosure, and financing contract terms are customizable in the CMS.") ## Payments ## Permit Clutch Gift Cards to Be Processed Without a PIN What it does: Configure whether a PIN is required for checking a Clutch gift card balance or redeeming it. Point of Sale offers three options: Optional, Required, or None. How to configure in CMS: 1. In CMS, go to **Integrations > Gift Cards**. 2. Edit an existing Clutch integration. If no integration exists, refer to this article to create one. 3. Under **Advanced > Pin Settings**, select one of these options: - **Optional**: PIN isn't mandatory but can be used if available - **Required**: Enter PIN to check the balance or redeem the gift card - **None**: A PIN is required, and the system processes gift cards without PIN validation 4. Save your changes. ![A form displays advanced settings.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_adv_config_3p_int_gift_card_clutch_pin_10_6.png) Learn more: [Integrate Clutch Gift Cards](https://help.salesforce.com/s/articleView?id=commerce.rt_adv_config_3p_int_gift_card_clutch.htm&release=264.0.0&type=5 "The Point of Sale (POS) app supports gift card integration with Clutch. Learn how to configure a Clutch account with the supported functionality.") ## Ability to Support Remote Pay by Link (PBL) in Deposit Scenarios What it does: Deposits made with PBL (both in-store and remote) can be done via the multitender screen. PBL can only be applied to the full deposit amount. If an order has been paid for and is marked as completed, PBL can't be used. If the order status is changed to partial or any other status other than completed after the deposit is made, PBL can't be used. ![The Pay by Link Deposit and Amount settings in the POS app.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_releases_bfs_pbl_remote.png) How to configure in CMS: - Enable and configure [deposits](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_checkout_laway_deposit.htm&release=264.0.0&type=5 "POS app supports partial payments/deposits while creating an order. An order is eligible for partial payments if it has online items. Partial payments can be done in two ways in the POS app: creating a layaway order and adding a deposit amount to an order. Only online orders define Layaway orders, while deposits can be a mix of in-store and online orders. The deposit must be more than the total of items in-store. If the deposit is less than 25% of the total for online purchases, a warning is shown."). - Enable and configure [multi-tender](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_checkout_multitender_config.htm&release=264.0.0&type=5 "Accept payments across multiple credit cards and other tenders in a single transaction. Configure the supported tenders and customize their display order in your POS app."). - Enable and configure [PBL](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_checkout_pbl_overview.htm&release=264.0.0&type=5 "Point of Sale's POS app offers Pay by Link functionality with two distinct payment flows. The In-Store Payment flow lets customers pay right away by scanning a QR code with their phone. The Remote Payment flow lets customers get an email link to pay later. Both payment flows are supported by Adyen and Verifone payment gateway terminals."). Learn more: [Point of Sale Pay by Link (PBL) Overview](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_checkout_pbl_overview.htm&release=264.0.0&type=5 "Point of Sale's POS app offers Pay by Link functionality with two distinct payment flows. The In-Store Payment flow lets customers pay right away by scanning a QR code with their phone. The Remote Payment flow lets customers get an email link to pay later. Both payment flows are supported by Adyen and Verifone payment gateway terminals.") ## Returns/Refunds/Exchanges ## Start Returns from Order History What it does: Enhanced to permit returns to be processed directly from Order History, giving store associates greater flexibility and streamlining the return process How to configure in CMS: This isn't a configurable feature as it's an enhancement of the Order History process Learn more: [Returns & Exchanges in Point of Sale](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_returns_exchanges_overview.htm&release=264.0.0&type=5 "Shoppers can return and exchange products in the POS app. Exchanges are defined by any return transaction that also includes a sale.") ## Other Feature Enhancements | Title | Description | Help Center Link | | --- | --- | --- | | Block Returns of Unshipped Send Sale Orders | Prevents associates from returning unshipped items, establishing inventory accuracy, and eliminating the need for reconciliation | [Manage Buy Online, Fulfill In Store (BOFIS) Orders in Point of Sale](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_orders_fulfill_bofis.htm&release=264.0.0&type=5 "Process Buy Online, Fulfill In Store (BOFIS) orders in the POS app. Store associates pack, ship, and manage orders fulfilled from the store.") | | NetSuite OAuth Enablement | NetSuite’s OAuth authentication is now supported, establishing secure access and synchronization of customer data while minimizing authentication errors | N/A | | Service Level in Delivery Group SPI | SPI updated to include service levels (for example, 3-5 days), enhancing delivery flexibility and clarity | [https://help.salesforce.com/s/articleView?id=commerce.rt\_cms\_modules\_omnichannel\_delivery\_groups.htm&language=en\_US](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_modules_omnichannel_delivery_groups.htm&language=en_US) | | CMS Register Reconciliation | Enhanced CMS till reconciliation by displaying till details, prompting users to count and enter amounts, and selecting reason codes for discrepancies to help prevent fraud | [Reconcile Open Tills in Point of Sale CMS](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_settings_reconcile_open_tills_in_retail_cloud_cms.htm&release=264.0.0&type=5 "Resolve open tills and other issues caused by ghost tills directly within Point of Sale CMS.") | | Migrate Terminal Management API Calls to Management API Calls | In preparation for Adyen's deprecation of the POS Terminal Management API on April 1, 2025, Point of Sale introduces the "Adyen Merchant Management URL Prefix" setting to replace the "Adyen Terminal Management URL Prefix." | [Adyen Payment Gateway Information](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_hardware_ayden_gateway_info.htm&release=264.0.0&type=5 "You can configure different payment gateways at the store level, such as store-level settlements, reporting, and currency requirements and integrate Adyen into Point of Sale.") | | Permit Zero Quantity to Be Part of Full Cycle Count | Items with zero quantity can now be added to the cycle count, even if not originally part of it, if the cycle count type is set to Full. | [Perform Cycle Count as an Associate](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_modules_perform_cycle_count_as_associate.htm&release=264.0.0&type=5 "As an associate, you can create and use batches to perform cycle counts for store inventory in Point of Sale CMS.") | | Verifone M450 Payment Terminal | New certification | N/A | | Adyen AMS1 | New certification | N/A |