---
schema_version: "1"
id: 62eb17eb130b5a52a25ea3fc157f5e67e67346d7180b2508d6ada33c4e185fb9
title: September Build Summary (10.4.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_4_1.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_4_1.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 08c1423e860692baa6a9903c74174cd918e4320627fe91c6efc09e3e74ed5faa
description: Build summary for Modern POS version 10.4.1, including what new features and changes it contains
products:
  - Commerce
release: "264"
---
# September Build Summary (10.4.1)

Build summary for Modern POS version 10.4.1, including what new features and changes it contains

  
| Theme | Feature | Benefit |
| --- | --- | --- |
| Inventory Management | [Corporate Transfer (CTS) Receiving Enhancements](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_4_1.htm&release=264.0.0&type=5) | Pack multiple boxes in a single transfer and effortlessly generate shipping labels using a shipping aggregator. |
| Inventory Management | [Upload Multiple Corporate Transfers in One CSV](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_4_1.htm&release=264.0.0&type=5) | Bulk upload corporate transfers via file instead of having to do 1:1. |
| Core Platform | [Activation Codes for Digital Products](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_4_1.htm&release=264.0.0&type=5) | Enables merchants to sell products through digital codes (for example, product downloads) via SPI from the merchant. |
| Adyen | [Adyen Card Alias](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_4_1.htm&release=264.0.0&type=5) | Link orders to shoppers in downstream systems for loyalty programs and fraud detection with a "card alias", nonPII identifier in the JSON. |
| Adyen | [Adyen Webhook for Handling Returns](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_4_1.htm&release=264.0.0&type=5) | Validation system implemented to block multiple fraudulent refunds tied to a specific order number. This validation uses Adyen's refund webhooks to confirm the success of refunds. |
| Other | [Various](https://help.salesforce.com/s/articleView?id=commerce.rt_releases_bfs_10_4_1.htm&release=264.0.0&type=5) |   |

## Inventory Management

## Corporate Transfer Receiving Enhancements

What it does: We've enhanced our corporate transfers feature to simplify receiving! Now, store associates can pack multiple boxes in a single transfer and effortlessly generate shipping labels by integrating with Salesforce's SPI.

![Products showing whether they're to be backed or packed 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_pos_inventory_ct_pos_packed.png)![The Shipping Options Window in the POS App, where you can generate a label or add a tracking number to the transfer.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_pos_inventory_cts_pos_tracking.png)

How to configure in CMS:

1. In CMS, go to **Store Management > Store Settings > Store Fulfillment**.
2. Expand **Shipment**.
3. Edit **Shipment Aggregation**.
4. Turn on **Corporate Transfers**.

![The Shipping Aggregator Settings for Corporate Trasnfers 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_shipping_aggregator_cts.png)

How to configure the SPI:

1. Go to **Integrations > Customer Connectors**.
2. Create a connector by selecting **Create** in the upper right.
3. Under **Connector Type**, select "**SPI**".
4. Under **Endpoint Name**, select "**SHIPPING\_LABEL**".
5. Fill in the rest of the fields.
6. Save your changes.

![The SPI connection to create shipping labels for CTS transfers 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_spi_cts.png)

Learn more: [Managing Corporate Transfers in Point of Sale CMS](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_inventory_corporate_transfers.htm&release=264.0.0&type=5 "Facilitate the movement of merchandise between stores, allowing merchants to align with regional demands and preferences.")

## Upload Multiple Corporate Transfers in One CSV

What it does: Merchants can create corporate transfers in CMS automatically by uploading a CSV file with inventory transfer information. This action initiates a store-to-store transfer. After the file is uploaded, it’s sent to the store's POS app. Store workers can then start packing the products for the store-to-store transfer.

How to configure in CMS:

1. In CMS, go to **Inventory > Store to Store CSV Upload**.
2. On the next screen, select **Add** to create a transfer.
    
    ![Store to Store CSV upload screen](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_pos_inventory_store_to_store_initiated_transfers1.png)
3. If prompted to upload a file, make sure that it isn't a duplicate and doesn't have any missing field data (for example **ProductID**) or the wrong file format. Failure to do so can result in an error after uploading (sample files in Point of Sale). The required fields for CTS uploads are **UploadNumber**, **FromStoreID**, **ToStoreID**, **ProductID**, and **Quantity**. All other fields are related to [Advanced Shipping Notices (ASNs)](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_inventory_asn_receiving.htm&release=264.0.0&type=5 "Set up accurate inventory receiving, check merchandise against prearrival notifications, and set reason codes for inventory mismatches in Point of Sale.").
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_note.png)
    
    Note **UploadNumber** refers to the transfer group.
4. The added file is shown in a list before upload. You can upload multiple files at one time. You can also remove files from the list using the delete icon.
5. After an upload completes, a message shows either the upload is successful or failed due to errors.

Learn more: [Inventory Management - Store to Store Initiated Transfers](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_inventory_store_to_store_initiated_transfers.htm&release=264.0.0&type=5 "Merchants can create Corporate Transfers (CTS) in the Point of Sale CMS automatically by uploading a CSV file with inventory transfer information. This action will initiate a store-to-store transfer. After the file is uploaded, it'll be sent to the store's POS app. Store associates can then start packing the products for the store-to-store transfer.")

## Core Platform

## Activation Codes for Digital Products

What it does: Salesforce supports retrieving activation codes via an SPI. For merchants selling products through digital codes (for example for product downloads), this SPI allows the POS to request the code from the merchant's server. The code can then be printed on the customer's receipt. For example, if a shopper needs a digital code to start a digital purchase made in-store, the SPI permits the POS to find the code and print it on the receipt. This gives the customer instant access to their digital product.

How to configure in CMS:

1. In CMS, go to **Products > Product Class**.
2. Configure a new class for activation codes. [Learn More](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_orders_custom_non_merchandise_sku.htm&release=264.0.0&type=5 "POS enables you to configure non-merchandise SKUs, such as postage stamps and gift certificates, to meet your business needs. You can also configure the checkout rules that apply to these items. Control if these items are discountable or taxable, and set other rules.")
3. Turn on **Requires Activation Code via External Source**.

![The CMS shows the requiring activation code via external source flag.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_pos_orders_special_types_activation_code_product_class.png)

How to configure the SPI:

1. In CMS, go to **Integrations > Custom Connectors**.
2. Select **Create** in the upper right.
3. Under **Connector Type**, select "**SPI**".
4. Under **Endpoint Name**, select "**GENERATE\_ACTIVATION\_CODE**."
5. Under **API Endpoint**, provide the external endpoint to get activation codes.
6. Under **Integration Type**, select "**HTTP\_POST**."
7. Under **JSON Headers**, provide headers that to be passed.
8. Configure the rest of the fields as needed.

![The CMS shows SPI settings.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_pos_orders_special_types_activation_code_spi.png)

Learn more: [https://help.salesforce.com/s/articleView?id=commerce.rt\_pos\_orders\_special\_types\_activation\_code.htm&language=en\_US](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_orders_special_types_activation_code.htm&language=en_US)

## Payments - Adyen

## Card Alias

What it does: The '**cardAlias**' provided in Adyen's payment response is included in the order JSON payload. This enhancement allows merchants to link orders to shoppers in downstream systems for loyalty programs and fraud detection. For example, merchants can automatically apply loyalty rewards based on past purchases. The '**cardAlias**' can also help detect fraudulent activity by identifying suspicious transaction patterns tied to the same card, allowing merchants to flag and prevent further fraudulent actions.

How to configure:

To get the '**cardAlias**' from Adyen, configure these settings in your Adyen portal:

For Card Payments:

1. Log in to your Adyen Customer Area.
2. Go to **Developers > Additional Data > Payment**.
3. Turn on **Include Alias Info**.

For Adyen Webhook/Notification Payloads (Pay by Link):

1. Log in to your Adyen Customer Area.
2. Go to **Open Standard Webhook > Additional Settings**.
3. Turn on **Alias Info**.

If a payment is made (via card or pay by link), the '**cardAlias**' value can be found in the order export JSON, specifically under the tenders attribute. See the example of a card payment order:

![THe JSON payload for Ayden Payments.](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_ayden_json.png)

Use cases:

**'cardAlias**' is populated in these scenarios/transaction types:

- Terminal is online for card transactions, and POS is online
- Terminal is online for card transactions, and POS is offline
- In-store Pay by Link
- Remote Pay by Link
- Tap to Pay
- Unreferenced Refund
- Apple Pay via Wallet

'**cardAlias**' won't be populated in these scenarios/transaction types:

- Terminal is offline for card transactions, and POS is online
- Terminal is offline for card transactions, and POS is offline

Learn more: [Adyen Payment Methods](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_hardware_adyen_payment_methods.htm&release=264.0.0&type=5 "Integrate supported Adyen payment methods integrate with Point of Sale (POS), allowing your customers to use a variety of payment options.")

## Webhook Handling for Returns

What it does: A validation system has been implemented to block multiple fraudulent refunds tied to a specific order number. This validation uses Adyen's refund webhooks to confirm the success of refunds, including both referenced and unreferenced ones. If many refunds aren't linked to the order, the system protects merchants by stopping more refunds after the total refunded amount is the same as the original order value. If many refunds aren't linked to the order, the system protects merchants by stopping more refunds after the total refunded amount matches the original order value. This enhancement helps prevent refund fraud, verifying merchants aren't exposed to excessive unreferenced refunds.

How to configure in CMS:

1. In CMS, go to **Store Management > Store Settings > System**.
2. Expand **Rollout**.
3. Verify **Enable Refunded Amount Validation—Adyen Only (refundedAmountValidation)** is turned on.

![The Enable Refund Amount Validation setting turned on 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_ayden_webhook_returns.png)

Learn more: [Validating Refunded Amounts via Adyen Refund Webhooks](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_returns_validate_refunds.htm&release=264.0.0&type=5 "Point of Sale implements a validation system to block multiple fraudulent refunds tied to a specific order number. This validation uses Adyen's refund webhooks to confirm the success of refunds. All refunds (referenced and unreferenced) are validated via these webhooks.")

## Other Feature Enhancements

  
| Title | Description | Help Center Link |
| --- | --- | --- |
| Personal Checks Without Validation | You can now select not to verify a customer's information if using a personal check as a tender. | [Tender Business and Personal Checks in the POS App](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_checkout_tender.htm&release=264.0.0&type=5 "The POS app supports both personal and business checks as a tender type. For business checks, only the check amount and check number are required. For personal checks, users can turn on or disable verification. If verification is enabled, all fields—routing number, check number, account number, check amount, and license details—must be entered. If disabled, only the check number, check amount, and license details are required.") |
| Vertex Offline file mapping to complete Vertex Connector | Offline functionality for Vertex tax connector | [Integrate Vertex](https://help.salesforce.com/s/articleView?id=commerce.rt_adv_config_3p_int_tax_vertex.htm&release=264.0.0&type=5 "Integrate Point of Sale with the Vertex tax engine to facilitate tax calculations during sale transactions. Confirm that the Vertex engine handles all necessary tax computations.") |
| Zebra Scanner Reset Barcodes in Device Manager | We recently changed the Zebra scanner reset instructions in Device Manager. Instead, we added a link to a ZD article with the steps for each supported model for merchants using an Epson-connected scanner. | [Zebra Scanner Support](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_hardware_zebra_scanner_support.htm&release=264.0.0&type=5 "Configure your wired or wireless Zebra scanners in the Point of Sale (POS) to make sure of accurate and efficient barcode scanning.") |