A product catalog is a data file that provides detailed information about the products on your site. Product feeds are useful for a variety of applications such as building out comparison shopping engines or product storefronts.
In the left navigation bar, select Content → Products → Product Catalogs.
In the top-right corner, select Create Product Catalog.
Provide the fields as defined in the following table:
Product Catalog Name
The name of the catalog. This will be shown to Partners as a way to identify the catalog. If you have multiple catalogs, they should have unique names.
Labels can be used to make the product catalog searchable for Partners.
You have the option to include a PDF file with instructions when using a custom format. This gives Partners additional details about the catalog (recommended).
You can upload a credit card catalog using various methods which include Direct Upload, Impact FTP server, or Pull From URL.
Larger catalogs can be uploaded to the impact.com FTP server using an FTP utility. Login, password and instructions are sent via email upon creation of your first catalog using FTP upload.
The FTP credentials can be used for uploading all product catalogs.
FTP credentials are emailed to all account users with technical permissions. Verify permissions by navigating to [Menu] → Settings → Account Users → Edit Access Rights.
Specify the location where impact.com can retrieve the product data.
Specify an HTTP or FTP URL. For FTP, the URL should be of the FTP directory and the configured filename needs to match the name of the file on the FTP server.
The catalog is pulled periodically depending on the configured fetch frequency, which is daily by default.
The following file format is supported:
Credit Card (TXT/CSV format)
Access Product Catalog via API
API Access gives you the option to maintain your product catalogs via API which includes querying, creating, updating and deleting catalog items.
See the API documentation for more info.
In the UI:
Get API access (separate screen with API credentials)
Learn more (API documentation)
Upload File Name
This is the name of the file to be uploaded.
This should exactly match the name of the file created and include a valid extension according to the format of your catalog:
CSV (comma-separated) requires .csv extension
Tab-delimited requires .txt extension
If using a compressed file, it must have a .gz or .zip extension depending on whether gzip or zip compression is used, respectively.
For gzip, the filename must include the format extension and the .gz extension, e.g. testFile.xml.gz, testFile.txt.gz, testFile.psv.gz.
Restrict Partner Access (optional)
Allow access to only specific Partners.
If using the TXT format, always save the file in UTF-16 encoding.
If using the CSV format, always save the file in UTF-8 encoding.
For APR fields, if you prefer to use your own text instead of impact.com specified format, please use Description fields.
When opening downloaded files in Microsoft Excel, it may default to Windows character encoding and not UTF-8/UTF-16, in which case special characters won't be recognized correctly. To prevent this, instead of opening the file directly, first open Microsoft Excel, open a new blank workbook, go to File → Import → CSV → get data → Delimited → File Origin: Unicode UTF-8 → Comma Separated → Open File. You can view an example file of the Product Feed Credit Card Template here.
If after processing, more than 10% of the records in the catalog have errors, or there was another overall file error such as a mismatched filename or empty file, the overall catalog processing is considered a failure. The failed catalog file will not be available to Partners.
If after processing, less than 10% of the records in the catalog have errors, the file will replace the previously active catalog file, but records with errors will be excluded.
If items with duplicate IDs are found to those already processed, an error occurs for these items and they are not indexed for search but do not count towards the overall error count either. These items are still present in the Partner downloaded file (unless your (the brand's) REST API is in use).
If there is a minor issue with a catalog record, a warning will be created. Records with warnings will be treated the same as successful records and uploaded as usual, but warning messages will be available for viewing from the UI so that the issue can be addressed if desired.
Error Message Meaning
No catalog found for the request. Check if the file name of uploaded file is the same as the one registered with the catalog
The configured upload file name must match the name of the uploaded file.
No attributes present in the catalog file
The catalog file is empty.
Catalog item with ID occurs more than once in the catalog, and those after the first will be ignored
Each product item ID in the catalog must be unique.
Record '1' has an error: (line 1) invalid char between encapsulated token and delimiter
A delimited file contains invalid use of double quotes. These need escaped properly by enclosing the field in double quotes and replacing all other double quotes with 2 double quotes. E.g. 3 " floppy becomes "3"" floppy".
(startline 1) EOF reached before encapsulated token finished
A delimited file contains an opening double quote, but a new line prior to closing of the quotes.
Error parsing (catalog type) field: with value: (field)
The product field is invalid and cannot be accepted.
Record (recordNumber) has an error: The number of delimited values (FieldsLength) does not match the expected (ColumnNamesLength)
When the number of product record fields does not match the number of column names in a delimited catalog.
No valid records were found in the catalog file
The catalog has no records.
More than 10% of the records in the file had errors
More than 10% of fields in the catalog records have errors, as a result the file cannot be processed.
To receive email notifications regarding product catalog upload failures, navigate to [Notification Settings] → [Gear Icon] → Technical → Catalog Uploads.