1WorldSync Customer Community

CommunityJedi22 · ‎09-04-2025

This article discusses how to implement a PowerReviews-specific product Feed. To learn more about leveraging a Google Merchant Product Feed instead, click here. To learn more about Product Feeds and their features and considerations, click here. To learn more about troubleshooting your Product Feed, click here.

Required Fields

The fields listed in the table below are required for every PowerReviews Product Feed import. Match the exact spelling and formatting to ensure your code is accurate.

Field	Example	Description	Length	Additional Notes
page_id	439178561578	The unique product identifier, typically the product ID, SKU, style number, or item number. This field is case-sensitive and should not include spaces. PowerReviews uses API calls to gather data. As a best practice, you should only use alphanumeric characters in your page_id. However, PowerReviews still supports the use of hyphens and underscores.	up to 50 characters	This unique identifier is the primary key for all reviews in the PowerReviews system. It is used across all aspects of the PowerReviews solution, including the PDP, Write a Review, Analytics, Follow-Up Email, Order Data, etc.
product_url	http://www.example.com/ 1234.html	The URL of the product detail page on your website. If you participate in Google PLAs, provide canonical URLs, or consider sending PowerReviews your Google Merchant Product Feed.	up to 650 characters	This field shouldn't contain spaces. The product URL will be used on the Write a Review page, in Moderation, and in Analytics.
name	Widget1	The name of the product.	up to 500 characters	Encode all special characters. The product name is displayed on the Write a Review form, as well as in the Follow-Up Email, Moderation, and Analytics.
image_url	http://www.example.com/ 1234.jpg	The URL of the product image. Ensure you use a high-quality image. It's best practice not to use special characters in your image URL and name without URL encoding the name.	up to 650 characters	The image should be at least 350 pixels in one dimension. This field shouldn't contain spaces. The product image will display on the Write a Review form, as well as in the Follow-Up Email and Moderation.
category	Shoes > Sandals	The product's inventory classification. To indicate a hierarchy, use the greater than (>) symbol as a delimiter between categories, similar to the example. Depending on your website's navigation model, the inventory classification may correspond to navigation categories.	up to 300 characters	The category is utilized in Analytics, as well as for assignment of Write a Review templates.
brand	Samsung	The product brand. This value must accurately match the brand name given on your website.	Up to 50 characters.	This field is required if you participate in Syndication, as it is one of multiple pieces of data that can be helpful if manual matching is required. It is also necessary if you wish to use our Brand Score feature.
upc	872760558488 (UPC) or 0872760558488 (ean) or 00872760558488 (gtin)	The 12-digit Universal Product Code or the 13-digit European Article Number, or the 14-digit Global Trade Item Number.	Must be 12 or 13 numeric characters.	This field is required if you participate in Syndication since it is used for our automated matching process. Only one UPC is supported per product. If you have multiple UPCs, you will need to include a line for each variant. To learn more about variants, please see Page IDs and Page ID Variants.

Optional Fields

The fields listed in the table below are optional for every PowerReviews Product Feed import. If you elect to use them, match the exact spelling and formatting to ensure your code is accurate.

Field	Example	Description	Length	Additional Notes
page_id_variant	1234_blue	The variant of the product. This field is used primarily when the page_id has multiple item-level variants, such as color or quantities. For more information on how to include variants in your Product Feed, see Page IDs & Page ID Variants.	Up to 50 characters	If you do not have any other system-generated variant identifier, UPC can be used for this. The page ID variant is used when multiple variations of a product exist. All reviews collected for a variant will display at the parent page ID level. The variant can be used to filter reviews on a PDP. For more information, see Page IDs and Page ID Variants.
add_to_cart_url	https://www.example.com/ store/cart-AddProduct?pid=1234&Quantity=1	The hyperlink to add the product to the customer's cart.	Up to 650 characters	If this value is provided, and you are using Questions and Answers, the URL will be included in the emails sent to a user once their question is answered, allowing them to purchase the product with a click.
in_stock	1	The indication of the in-stock status of the product. A value of 0 indicates no, and a value of 1 indicates yes.	1 character	This information will allow filtering by In Stock vs. Out of Stock products in some PowerReviews Analytics reports.
price	1099.99	The current selling price of the item. International currency formatting isn't supported. Include the decimal point in the price, but don't include any dollar signs or commas.	Up to 650 characters
asin	B00005N5PF	Amazon Standard Identification Numbers (ASINs) are unique blocks of 10 letters and/or numbers that identify items - used for the Share to Amazon feature.	Must be 10 characters
description	A superior widget for every requirement. An essential part of any widget collection.	The long product description. HTML markup shouldn't be included in the description.	Up to 10,000 characters.	You must escape all double quotes. If your data contains special characters, ensure you enclose the entire value in quotes. Do not include HTML or line breaks. While not required, if you choose to include a description, it will only be visible to you in Moderation. It will not be seen by your customers.
manufacturer_id	xlslmpprod-1790001-a	The manufacturer's model number.	No limit.	In the absence of UPC values, this field can be helpful if manual matching is required for syndication.

Note: You must escape all double quotes in the 'description' field. If your data contains special characters, ensure you enclose the entire value in quotes.

Creating Your Product Feed

1. Prepare your file to send to PowerReviews, noting the requirements above. You should format the file with UTF-8 encoding and with no byte order mark (BOM).

Click to download a Product Feed sample CSV file.

2. Edit the sample file you downloaded with your own product catalog information, keeping the PowerReviews' field names as column headers.
3. Upload your file to your own SFTP, the PowerReviews-provided SFTP, or provide a public URL. If you choose to use your own SFTP, provide PowerReviews with he necessary location and credentials required to access the file. If you wish to use the PowerReviews-provided SFTP (best practice) and do not have your credentials, please reach out to your Implementation Team or PowerReviews Technical Support to request them.

Ensure that the filename and location are static. When we configure the Product Feed import on our backend, it relies on looking for the same file each time. If you need to rename your file or move it to another location, you will need to contact us when this occurs so that we can update your configuration.

5. Once you've completed these steps, please reach out to your Implementation Team or PowerReviews Technical Support to request that we configure your Product Feed for import into our system.

We highly recommend that you automate this process on your end to ensure that whenever your product information changes, we receive that data in an updated Product Feed file automatically. Otherwise, it will be important to make sure that the file is updated manually and placed in the location where we are looking for it on a recurring basis.

Processing Your Product Feed

Product Feeds are typically processed every 48 hours. If you upload a new Product Feed, please allow this time for any changes to be imported into our system. If, after that time, you do not see your updates to your data, please contact your Implementation Team or PowerReviews Technical Support so that we can ensure that this process was triggered.