Introduction
This document covers the Standardized PartnerAccess Feed intended to automate the submission of original manufacturers’ product content to 1WorldSync Content Solutions. The document provides details on two available feeds, files structure and format of all the fields.
Benefits of direct feeds from manufacturers to 1WorldSync
When 1WorldSync Content Solutions gathers product data from manufacturers’ websites, there is always a risk of a human-induced error, slight inconsistency, or, more importantly, latency between the moment product information is requested from resellers and is made available by 1WorldSync. This translates into lost sales, which is especially damaging in the early stages of the product lifecycle. Often times the product information captured is not necessarily in-depth, since manufacturers do not always make all data available on their websites for public use.
Format & Transfer
Feed Transfer Method
The feeds are delivered to 1WorldSync via FTP. We support two main transfer methods:
- 1WorldSync FTP Server: 1WorldSync provides an FTP link and FTP account credentials to participating manufacturers, and manufacturers use them to upload their feeds to the 1WorldSync FTP server.
- Manufacturer’s FTP Server: Downloading from the manufacturer's FTP or HTTP server. Downloading from password-protected URLs is supported.
Supported Feed Formats
1WorldSync is capable to process Standard PartnerAccess Feed in either of the two following formats:
- XML Feed
- Excel Feed
The detailed explanation of the feeds fields and structure is available in the following sections of this document.
Feed Update Mode
Standard XML Feed is expected to be non-incremental (full).
The delta (new products and modifications) will be detected automatically.
Feed Synchronization Frequency
Feed synchronization frequency depends on the number of product updates on the manufacturer's side. We recommend weekly feed synchronization schedule along with intermediate updates once or twice a week when a new set of products is added by a manufacturer or when a mass product update is needed.
Standard Feed Content Types
Standard Feed has two main sections: predefined content types that can be processed automatically and generic attributes. Some content types are mandatory such as part number, product description, hero image, and product features (for Inline Content).
Our Standard Feed is made to power 2 different services, DataSource (or PartnerAccess) and Inline Content (or ContentCast). Most content types are used in both services, but not all of them. Some are exclusively used in one or the others.
Please see details below of which content type is used for each service:
| Content type | ContentCast |
| Manufacturer Part Number | Yes |
| Product Description | Yes |
| UPC / EAN codes | Yes |
| Launch Date | Yes |
| End of Life Date | Yes |
| Marketing Text | Yes |
| Product Specifications | Yes |
| Key Selling Points | Yes |
| Product Features - Media | Yes |
| Product Features - Orientation | Yes |
| Product Features - Header | Yes |
| Product Features - Text | Yes |
| What’s In the Box | Yes |
| Primary Product Image | Yes |
| Additional Images | Yes |
| Additional Images - order | Yes |
| Videos | Yes |
| Product Data Sheet | Yes |
| User Manual | Yes |
| Quick Start Guide | Yes |
| Material Safety Data Sheet | Yes |
| Warranty Card | Yes |
| Installation Guide | Yes |
| Product Brochure | Yes |
| Footnotes | Yes |
| Legal Copy | Yes |
| Accessories | No |
| Main Products Part Numbers | No |
Predefined Content Types
- Manufacturer Part Number
- Product Description
- UPC / EAN codes
- Launch Date
- End of Life Date
- Marketing Text
- Product Specifications
- Key Selling Points
- Product Features
- What’s In The Box
- Primary Product Image
- Additional Images
- Product Data Sheet
- User Manual
- Quick Start Guide
- Material Safety Data Sheet
- Warranty Card
- Installation Guide
- Product Brochure
Standard XML Feed
Format Requirements
- Standard XML Feed should be delivered as a set of XML files: a separate XML file for each market-language pair.
- Each XML file must be compliant with our schema defined in standard_feed.xsd.
- Each product must be defined in a separate <Product> section.
- Market and language must be defined in each XML file in the <Feed> section. Markets and languages dictionaries are defined in the standard_feed.xsd file.
Example: <Feed Language="en" Market="us">
Standard Excel Feed
Format Requirements
- Each Excel file must be compliant with our Standard Excel feed example standard_feed.xlsx.
- Each product must be defined in a separate row. A product cannot be defined in more than one row at a time.
- Market and language must be defined as a worksheet name in the Excel file.
- Market and language codes should be selected from this article.
- Standardized Excel Feed can have more than one worksheet for different market‐language pairs.
- Separate Excel files for each market-language are acceptable. Market and language must be defined in a worksheet name.
Automatic SKU Creation
If your contract includes automatic SKU creation for ContentCast, then all SKUs in Standard Feed should include Part Numbers and Product Description components. Without them automatic SKU creation will not work. Details about all components are presented in the next chapter of this guide.
Activate your SPAF Feed for ContentCast:
In order to activate the SPAF Feed, please contact the Customer Support. Our teams will guide you through the test phase and the setup of the Feed.
You can find additional information to help you setup the SPAF Feed in the following articles:
