---
schema_version: "1"
id: 8b9547714333aef1d864997a77bf59f90d83c0ad53e5e8635fe62d4fd92beb84
title: Product Feed Known Issues and Restrictions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/rt_adv_data_feeds_spec_prod_feed_issues.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.rt_adv_data_feeds_spec_prod_feed_issues.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7cde6dc2bc70fd5d7ac07322f2d315c943dd829fb53984d4bb95af106b58b9a3
description: Understand product feeds limitations within Point of Sale CMS and how to work around them.
products:
  - Commerce
release: "264"
---
# Product Feed Known Issues and Restrictions

Understand product feeds limitations within Point of Sale CMS and how to work around them.

## Known Issues and Restrictions

- For columns that do not conform to the following feed spec names and values, we can apply field mappings and, optionally, field transformations so that the product data gets indexed correctly.
- Several fields are common with Google Shopping feed spec, but we need additional fields to build a fully functional app. See [Product data specification](https://support.google.com/merchants/answer/7052112?hl=en).
- When uploading your file, make sure to map the required Target Fields marked with an asterisk. Map the fields as columns that contain a value, don't leave them empty. For example, if certain products don't have a list price, enter '0' instead of leaving the field blank. Failing to map these required fields correctly can result in errors during the upload process.
- When trying to upload a CSV to have additional images added to products, you might encounter an error if the URLs have commas. A workaround might include quotes around each URL or upload a TSV file instead.
- You can sort product sizes in the POS app alphabetically. However, you can also sort sizes based on the customer’s preference. For example, you can sort S, M, L, XL into L, M, S, XL. To have this functionality, upload a size file for sorting through the Point of Sale backend. The file needs to include all the sizes for _all_ the products.
- When scanning a UPC-A barcode offline, if you see an error that the product was not found, it could be because the barcode number begins with "0". If it does, in the CMS go to **Store Management** | **Store Settings** | **Feed** | **Product**. Under Barcode Scan Replacement JSON, add the following regex:
    
    `{"regex":"^0+(?!$)","replace":""}`