Product Feed Known Issues and Restrictions

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.
• 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":""}