You are here:
Support Serialized Products for Sales & Returns
Point of Sale provide features to support the sale and return of serialized products. When a serialized product has been added to a cart or returned, users is prompted to scan or manually enter the product's serial number.
- Modern POS App Build: 9.8.1 or greater
- Platform Support: iPhone & iPad
- Offline Support: Yes
For information on managing serialized products in inventory, consult the Manage Inventory section.
Configure Product Feed
Serialized products are configured through the Product Feed.
- In the Product Feed, for each serialized product, create a dedicated boolean column indicating whether serialization is required. Products marked True are serialized and vice versa. You can label this column as needed, as it will later be mapped to the "SerialNumberRequired" field in Field Mappings. See the sample feed for reference.
- Once configured, upload the feed using the processes to Run Feeds Manually or Schedule Feed Runs.
Configure Product Field Mappings
Validate serialized products on the POS app by configuring Map Data Feed Fields.
- After successfully uploading the feed, configure Field Mappings in the CMS by going to .
-
Locate the serialized column under Source Field and map it to "SerialNumberRequired" under
Target Fields.
- Save your changes.
POS Behavior
Sales Flow
When a serialized product is added to the cart, a modal will appear, prompting you to scan or manually enter the product's serial number.

Returns Flow
During the Returns & Exchanges process, after selecting a serialized product, the same modal will appear, prompting you to scan or manually enter the product's serial number.

If an incorrect number is entered, an error message will be displayed. Upon successful entry, you can proceed with the return/exchange process.

Reporting
Serialized products will have their information logged in the TLogs, with their serial numbers recorded under the attribute "serialNumber." See this example:

Changes to Cart Action Validation During Transactions
Starting in app build 11.6, the POS adds more checks to validate the current cart state before certain cart actions can proceed. These checks serialize valid cart actions and help prevent mismatches between the app and backend. If the POS prevents you from completing one of these actions, void the cart or reset tenders as needed, and then try again. The POS now blocks these actions in specific scenarios:
- Changing the customer associated with the cart after tendering has started.
- Updating product form information for an item in the cart after tendering has started.
- Continuing to modify the order flow when the server returns an empty cart.
- Continuing the punchout flow when the server returns an empty cart.
- Starting a multi-tender workflow after tendering has started on the cart page, but unable to continue because of a payment terminal connection issue.
