LoudCrowd Creator Storefronts require your product data in order to enable:
creators to add their product picks to collections on their storefront
creators to tag their social posts and UGC with the products featured in their media
buyers to shop creator Storefronts and view product details and options, such as color, size, etc.
you to recommend products for your creators to add to their Storefronts.
If your eCommerce system is Salesforce or Shopify, LoudCrowd can pull product data automatically via API connection directly to those systems. Other eCommerce systems will need to send LoudCrowd a regularly updated product data file. Pricing data can be included in this file, or sent as a separate file.
Pre-requisite: create an SFTP integration
Your product feed file can be sent to LoudCrowd via Secure File Transfer Protocol (SFTP). Your team will drop the file to a LoudCrowd-hosted SFTP server.
In order to set this up for your account, please contact your LoudCrowd Client Strategist via email. Your email should include:
File purpose (ex., Product Feed)
Your server host's public SSH key (in the form RSA, ECDSA, or ED25519) OR request a password from LoudCrowd.
Note: If you are sending multiple different data files to LoudCrowd, you can use the same key, or generate a different key for each.
Sample file with the required fields (listed below), including 5 sample rows of parent products and their variants.
LoudCrowd will create your SFTP server, and your Client Strategist will email you the following information to access your server:
username
SFTP server address
Drop a product file to LoudCrowd SFTP
In order to drop files to our SFTP server, the connection has the following requirements:
Your server host's public SSH key (in the form RSA, ECDSA, or ED25519) OR the password you received from LoudCrowd
The file must be dropped into a directory named
~/productsFile must be a .csv or .tsv file
Setup product feed
We recommend a daily file since products can change often.
This file should include both standalone products and product variants.
For translations of title, selling regions and PDP urls, images, add multiple rows for the same variant.
Product feed update behavior
The product feed considers the sent .csv file as a full set of your product catalog. This means that any product that might have been sent included in a prior file that is not included in a newer one will be marked as inactive and its data will be made unavailable.
You cannot use the product feed incrementally (ie: send a file with just new products), you must always send the full catalog.
Selling Regions
If the ecomm store is under one domain, but sells products to multiple regions, the feed will need to include what regions a given product is available in. A selling region is a unique text identifier defined by your system to identity a region a product is available in. Example: "US", "EU", "canada", "Fulfillment Center 1" etc. They are not inheritable so a product marked available in "EU" will not automatically be available in "France" unless specified for both. If selling region is specified, you may also have pricing be customized per region and per currency. The URL also may be customized per region in case the region is in the url. All other fields are not region specific. (See pricing example for more details) If the main product feed includes 1 million or more variants, we recommend sending selling region data exclusively in a separate pricing feed file.
Product field guide
We recommend a .csv file with the following data fields:
productId - this is the id or sku of the product in your system
parentId - the ID or SKU of the parent product if this row is a product variant. LoudCrowd will use this field to group variants under a product. If a product is a parent or standalone product this field should match the productId field.
position - For variants, this field determines the display order.
brand - the brand of this product
title - the title that will be used to display the product
active - (Y, N) whether or not the product is currently being sold
URL - the link to the product detail page of this product, this will be used to send buyers to the products from the creator storefronts
imageSrc - URL of a product or variant image. If a product or variant has multiple images, repeat the row with the same product details, changing only the URL for each image. These images will be used for both picking and displaying of products and variants in creator storefronts
language - locale language the title, product urls, and options are in. ISO 639-1 (alpha2) two letter format. Required only for translations.
country - locale region to further refine language for title and product url. ISO 3166-1 (alpha-2) two letter format. Optional for translations.
listPrice - the regular price of the product, this will display as a struck through price in favor of the sale price
salePrice - the currently discounted price of the product, if same as the list price only one will be displayed
currencyCode - this is the currency of the prices for this product
availability - (in stock, out of stock) used to hide products that are currently out of stock
allowedRegion - Selling region the variant is available in, blank or null means allowed everywhere.
option1Name - The name/title of the 1st variant option, like "Size" or "Color"
option1Value - The value of the 1st variant option, like "XL", or "Blue"
option1SwatchSrc - URL for the value of the 1st variant option's swatch image, optional.
option2Name - The name/title of the 2nd variant option, like "Size" or "Color"
option2Value - The value of the 2nd variant option, like "XL", or "Blue"
option2SwatchSrc - URL for the value of the 2st variant option's swatch image, optional.
option3Name - The name/title of the 3rd variant option, like "Size" or "Color"
option3Value - The value of the 3rd variant option, like "XL", or "Blue"
Note: if there are more options for the product. See below
option3SwatchSrc - URL for the value of the 3st variant option's swatch image, optional.
Example:
productId,title,active,imageSrc,brand,listPrice,salePrice,currencyCode,URL,availability,parentId,position
37637613,Photo Paper 2.3x3.4” (50 Pack)...,Y,https://media.example.com/is/image/product/7011637?wid=800,HP,47.99,50.99,USD,https://www.example.com/product/prd-7011637,in stock,7011637,0
47627781,"Portable Projector, 480p LED",Y,https://media.example.com/is/image/product/47627781?wid=800&hei=800,HP,387.99,387.99,USD,https://www.example.com/product/47627781/hp-mobile-portable-projector-480p-led-projector-for-home-office.jsp,in stock,47627781,0
58975778,"Portable Projector, 480p LED, Grey",Y,https://media.example.com/is/image/product/58975778?wid=800&hei=800,HP,387.99,387.99,USD,https://www.example.com/product/47627781/hp-mobile-portable-projector-480p-led-projector-for-home-office.jsp?color=grey,in stock,47627781,1
158975780,"Portable Projector, 480p LED, White",N,https://media.example.com/is/image/product/158975780?wid=800&hei=800,HP,387.99,349.99,USD,https://www.example.com/product/47627781/hp-mobile-portable-projector-480p-led-projector-for-home-office.jsp?color=white,out of stock,47627781,2
Product feeds with more than 3 variant options
In order to send more options for products, they will need to be in a separate file. The file should have:
productId - The id of the variant
optionXName - name of the option, where X is any number < 10
optionXValue - name of the value, where X is any number < 10
optionXSwatchSrc - URL for the value of the X variant option's swatch image, optional.
Setup product pricing feed
Since pricing can change even faster than the product details themselves. Some clients elect to sent LoudCrowd a separate product price file. This is optional depending on your price structure and frequency.
Product pricing feed update behavior
Unlike the main product feed, the product pricing feed does incremental updates.
This means you don't need to send the full product catalog each time.
You can send smaller files with only the products that changed their prices or are now on sale (or for which their sale period ended so their salePrice needs to be cleared).
This ensures you can send these smaller files as soon as you need to, and they are processed quickly so that our system reflects the new prices.
If a price applies to more than one selling region, that price should be repeated in the file for each allowed selling region.
Product pricing field guide
We recommend a .csv file with the following data fields:
productID - this is the id of the parent product or product variant in your system
listPrice - the regular price of the product, this will display as a struck through price in favor of the sale price
salePrice - the currently discounted price of the product, if same as the list price only one will be displayed
currencyCode - this is the currency of the prices for this product
allowedRegion - Selling region the price/currency is available in
Example:
productId,salePrice,listPrice,currencyCode,allowedRegion
123ABC,100.00,150.00,USD,US
123ABC,100.00,150.00,CA,CA
123ABC,100.00,150.00,MXN,MX
456DEF,103.00,110.00,USD,US
456DEF,103.00,110.00,GBP,GB
789HIJ,10.00,11.27,USD,,
In the example above:
Product 123ABC has a sale price of $100.00 and is available in the US, Canada, and Mexico.
Product 456DEF has a sale price of $103.00 and is available in the US and Great Britain.
Product 789HIJ has no specified regions, meaning the price applies globally.
Drop a product pricing file to LoudCrowd SFTP
In order to drop files to our SFTP server, the connection has the following requirements:
Your server host's public SSH key (in the form RSA, ECDSA, or ED25519) OR the password you received from LoudCrowd
The file will need to be dropped into a directory named
/pricesFile should be a .csv or .tsv file