Product Content (Product Feeds)
Logicbroker has the ability to collect product content from all of your suppliers, validate formats and integrate with your PIM*, CMS**, DAM***, or eCommerce systems. This allows you to collect product data from 100s of channels, allowing your suppliers to upload content in your format and verify that their content is always compliant with your requirements. Below is a step by step process for getting your product content integrated.
*Product Information Management, **Content Management System, ***Digital Asset Management
✨Tip:
To learn more about uploading product content see this article.
Setting Up Format
First we need to determine the data required to receive from your suppliers. This can include fields like image URLs, product SKUs, descriptions, ingredients, etc. The format templates created for your suppliers will always use a CSV format. All header columns can be customized to contain the following field types:
| Field Type | Description |
|---|---|
|
String |
Standard collection of characters. |
|
Integer |
Whole number field. |
|
Decimal |
e.g. 3.14 |
|
Image URL |
Used to transmit images for the product using URL. Setting this type for the field will show the product in the portal Product Search page with the image of the provided URL. |
|
Name |
The Name type will show the product name in the portal's Product Search page. |
|
Category |
Indicates if the field is a category which would be used to create separate templates for each option. |
By default you will be able to receive all of your feeds in this format as well using an SFTP/FTP connection. All field column names cannot contain any special characters, such as forward slash (/), backslash (\), number sign (#), question mark (?), control characters, dashes (-) and spaces.
🗒️Note:
If you are integrating using a custom API, Logicbroker can connect your content to your system converting the custom CSV template into the required format needed to integrate.
Required Rules and Validation
Once your CSV format is created with all columns, the next step would be setting up the rules for different templates per product category and validation for all your fields. When a feed is submitted, we will not only check the format of the field, but can also validate specific data setup.
Below is a list of rules we can setup on your feed; a rule is a parameter setup to check against the field value that is being submitted. The rules can also include conditions, where they will only run validation against if they meet that condition. The condition can relate to another field in the feed or refer to the same field. Each field can have an unlimited number of rules and conditions.
| Rule Type | Description |
|---|---|
|
Required |
A rule that will make the field required. Usually used with a condition looking up Category. For example, you can add a condition to always include "Size" when the Category is "Shoe" In addition, by setting this condition the supplier will have the ability to download templates for each category including only the required fields. |
|
Equals |
Used to check the value submitted in the field equals the parameter set. If the field does not match the product will fail validation and show as non-compliant. |
|
Not Equals |
Used to check the value does not equal the parameter set. If the field matches the parameter the product will fail validation and show as non-compliant. |
|
In List |
Will check the value submitted against an array of values. The array can contain an unlimited number of values to check against. If the value is not in the list the product will be marked as non-compliant. |
|
Matches Expression |
A regular expression can be written to check against the value submitted. This can be an exression to verify a valid UPC is being sent or only alpha numeric characters provided. |
|
Length Equals |
Check the number of characters are provided in the field and compares against the parameter set. For example if 10 is set the value provided must contain 10 characters. |
|
Length Less Than |
Checks the number of characters provided in the field and if the length is not less than the parameter setup, the product willl be marked as non-compliant. |
Integrating Product Feeds
Once you have your format and validation rules setup you can setup an integration to receive your content feeds. Out-of-the-Box SFTP/FTP integration is offered as an integration option.
Using your Logicbroker credentials and logging into your SFTP/FTP site, you will see the /Product directory. Go there and into the /Product/<PartnerAccount>/Inbound directory, this is where all files are sent to, from your suppliers. All files here will have passed validation setup and have been verified to process successfully; suppliers cannot send their feeds until all products have passed validation. To learn more about the SFTP/FTP directories, see this article. To learn more about the process for managing compliant and non-compliant products in the portal, see this article.
🗒️Note:
We also have the ability to connect your product content to any API or system. For more information on available system connectors and creating a custom connection contact us.
Product feed shows Failed or "Feed is not compliant"
This applies to suppliers who upload product feeds in the portal and to retailers who receive them. You may see this message on the feed:
Feed '<Feed ID>' is not compliant. <number> items must be fixed to meet requirements. To fix the errors download the failed feed, view the "error" column, correct the <number> items that must be fixed to meet requirements and re-upload your file.
What it means: one or more items broke the retailer's field rules, such as a required field, a value that is not in the list, or a wrong date format. Logicbroker sends a feed to the retailer only when every item in it is compliant.
What to check:
- Go to Products › Feeds and select the retailer under Partner.
- In the Feeds table, compare the Items and Compliant columns for your file. If Compliant is lower, some items have errors.
- Click Download on that row. The downloaded file has an "error" column that names the problem on each failing item.
- Check the Events table at the bottom of the page. If the whole file could not be read, the event shows the error with the row and column.
- Click View feed specification to see every field the retailer accepts.
The fix:
- Item errors: correct the items named in the "error" column and upload the corrected file again. Use the exact format the error asks for. For example,
Last modified needs to be in "MM/DD/YYYY HH:MM:SS " format.means every date in that column must follow that pattern. - Old failed feeds: click Delete on a failed feed after you upload the corrected file, so only the current file stays in the list.
- Error shown in the retailer's own system: if the message appears on the retailer's website or onboarding form and not in Logicbroker, contact the retailer. Logicbroker Support cannot change the retailer's own checks.
How to check it worked: the new feed shows the same number under Items and Compliant. Its status changes to Complete once it is sent. If the retailer approves feeds first, the status shows Pending until the retailer clicks Approve. A compliant feed that is not sent yet shows a Send button.
When to contact Support: contact Support if a compliant feed shows Failed, or if you cannot tell what the error means. Include your company name, the retailer, the Feed ID, the file name, the exact error text and what you already tried.
Product images do not upload or update
This applies to suppliers who send image links in a product feed, and to retailers who review them. Some retailers copy each image from your link into Logicbroker. For those retailers, an item can fail with an error that starts with Failed to load images:, for example:
Failed to load images: The remote server returned an error: (503) Server Unavailable.Failed to load images: Parameter is not valid.
What it means: Logicbroker could not download a real image file from the link. Either the image host refused the request, or the link opened a web page instead of the image itself.
What to check:
- Open each image link in a private browser window where you are not signed in to anything. The image alone should load, with no sign-in or preview page around it.
- Make sure the link points to an image file, such as a JPG or PNG, and not to a folder, gallery or product page.
- Make sure each image is 10 MB or smaller.
The fix:
- Link opens a page, not the image: replace it with the direct link to the image file. Many file-sharing services give a share-page link by default. Use their direct-download link instead.
- Link needs a sign-in or is restricted: host the images where anyone can open them. Google Drive links often fail, because Google Drive can block direct access to the files.
- Image is too large: resize or compress it to 10 MB or less.
Replacing an image that will not change: Logicbroker remembers images by their link. If you replace the picture but keep the same link, the image host may report that nothing changed, and Logicbroker keeps the old picture. Give the new image a new file name or link, put that link in the image column and upload the feed again.
How to check it worked: the item no longer shows a Failed to load images: error, and the new image appears on the product.
When to contact Support: include your company name, the retailer, the SKU, one image link that fails, the exact error and what you already tried.
Cost or MSRP did not update for a retailer
This applies to suppliers who update prices in the portal. You can update prices yourself. Agree any price change with the retailer before you send it.
What it means: the price in a product feed and the cost in your inventory feed are separate. A product feed can complete without errors while the Cost on the Inventory page stays the same. Support resolves these cases by updating the cost in the inventory feed as well.
What to check and the fix:
- Go to Products › Feeds and select the retailer under Partner.
- Click Download on your latest feed with status Complete. Change the price columns, then upload the file on the same page. If the retailer's template has no price column, you only need the inventory step.
- Go to Inventory and click Import.
- Select the retailer under Partner. Choose Inventory Feed, upload a file with the Cost column, and MSRP if you use it, then click Import.
For inventory columns and templates, see Inventory setup.
How to check it worked: on the Inventory page, the Cost column shows the new value for that retailer.
When to contact Support: contact Support if the cost changes back to an old value after you import it. Include your company name, the retailer, two or three SKUs with the expected cost, the file names and dates of both uploads, and what you already tried.
Updating a product through the API returns "SKU is missing."
This applies to retailers and suppliers who update products in the Product Onboarding Center through the API. It does not apply to file uploads on Products › Feeds.
What it means: the update request replaces the whole stored product with the request body. Attribute names are case-sensitive, so "SKU" is not read as "sku".
What to check:
- Send a
PUTto/api/v2/ProductOnboardingCenter/Products/{id}to update your own catalog product as a retailer. To update a product for a specific supplier partner, send it to/api/v2/ProductOnboardingCenter/{partnerId}/SupplierProducts/{id}. The same paths work under/api/v3/Product/. For keys and tokens, see API Authentication. - Put the attributes inside
"Attributes"with lowercase names, such as"sku"and"attribute_set". - Make sure
{id}in the path is the same as"sku". - Send every attribute the product needs, not only the ones you changed. The request replaces the stored product, so attributes you leave out can be removed.
- Send a reason or error text in the top-level
"ErrorMessage"field, not as an attribute.
Example body:
{
"Id": "ABC123",
"Attributes": {
"sku": "ABC123",
"attribute_set": "electronics",
"name": "Wireless mouse",
"brand": "Example",
"msrp": "19"
},
"ErrorMessage": "Image does not match product"
}
The API returns one of these errors when the body is wrong:
SKU is missing.means there is no lowercase"sku"attribute.Attribute set name is missing.orAttribute set name <name> is invalid.means"attribute_set"is empty or does not exist for the retailer.SKU cannot be changed. Please delete this item and create a new one with the updated SKU instead.means the{id}in the path and"sku"differ.
How to check it worked: the API returns the updated product, and the changed values show on the product.
When to contact Support: include your company name, the retailer, the full request path, the request body, the full response and what you already tried.
We're updating this article. Some steps and screenshots may not match the portal yet. If anything is unclear, contact support@logicbroker.com.