11WorldSync Global Community
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Customer Community
- Customer Community Knowledge Base
- PartnerAccess Knowledge Base
- PA Documentation
- SPAF Feed: Content Fields Details for PartnerAcces...
Options
- Article History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
1WSCGomez
Moderator
Options
- Article History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 08-17-2023 08:39 AM
Content Fields Details
Manufacturer Part Number
The original manufacturer part number is used to identify the product in the channel.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <PartNumber> | |
|
Field name in XLS File
|
Part Number
|
Note: Please make sure all the cells in the 'Part Number' column are in General format. |
| To check it, select 'Part Number' column, right-click on the selection and choose ‘Format Cells…’ in the shortcut menu. Check if ‘General’ cell formatting type is selected on the 'Number' tab. | ||
| Format | Text | |
| Max size | 40 | |
| Nullable | Not null | The field is mandatory. We map content to products only by Manufacturer Part Number |
| Multi-value | No |
Product Description
The product’s relevant title that clearly describes it.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <ProductDescription> | |
| Field name in XLS File | Product Description | |
| Format | Text | Should not include HTML or markup codes. |
| Max Size | 200 | |
| Nullable | Not null | The field is mandatory. We can automatically create SKU by Part Number only in case Product Description exists. |
| Multi-value | No |
UPC / EAN codes
The product's EAN-8, UPC-12, EAN-13 or GTIN-14 unique identifier.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <UpcEan> | |
| Field name in XLS File | UPC / EAN / GTIN | |
| Format | Text | |
| Max Size | 14 | |
| Nullable | null | |
| Multi-value | Yes | Only one UPC / EAN code should be defined in each field. Any extra characters are not allowed. |
Launch Date
If a launch date is provided, the shipment of product content will be held until that date. Launch dates that occur in the past will be used for reference purposes only.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <LaunchDate> | |
| Field name in XLS File | Launch Date | |
| Format | Date | We suggest using the ODBC format: YYYY-MM-DD |
| Max Size | 10 | |
| Nullable | null | |
| Multi-value | No | One Launch Date for each market. |
End of Life Date
The date that your product should stop showing or product discontinued date.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <EndOfLifeDate> | |
| Field name in XLS File | End of Life Date | |
| Format | Date | We suggest using the ODBC format: YYYY-MM-DD |
| Max Size | 10 | |
| Nullable | null | |
| Multi-value | No | One End of Life Date for each market. |
Marketing Text
The marketing copy text is used for product description.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <MarketingText> | |
| Field name in XLS File | Marketing Text | |
| Format | Text | Should not include HTML or markup codes. |
| Max Size | 4000 | Minimum size - 65 |
| Nullable | null | |
| Multi-value | No | One Marketing Text for each market-language pair. |
Product Specifications
The product’s technical attributes information.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <AttributeGroup> | |
|
Field name in XLS File
|
Product Specification
|
name | value (one per line within the cell) |
| Include any attributes information you have for this product | ||
| Format | Text | |
| Max Size | 4000 | For each Attribute Group, Attribute Name and Attribute value. |
| Nullable | null | |
| Multi-value | Yes | You can define more than one Attribute Group and Attribute in the groups. |
Key Selling Points
Reasons to buy (product feature bullets description).
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <KeySellingPoints> | |
| Field name in XLS File | Key Selling Points | Feature | value (one per line within the cell) |
| Format | Text | Should not include HTML or markup codes. |
| Max Size | 400 | For each Key Selling Point. |
| Nullable | null | |
| Multi-value | No | One Key Selling Points group for each market-language pair. |
Product Features
Detailed product features description.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <ProductFeatures> | |
|
Field name in XLS File
|
Product Features.
|
Each product feature should be entered in a separate cell. |
| You may add additional columns for the product features. | ||
| Format | Text | Should not include HTML or markup codes. |
| Max Size | 4000 | For each Product Features Header and Product Features Text fields. |
| Nullable | null | |
| Multi-value | No | One Product Features group for each market-language pair. Each Product Feature Header must have related Text. |
What's in the Box
Items included in a shipping box.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <WhatIsInTheBox> | |
| Field name in XLS File | What's in the Box | Item | value (one per line within the cell) |
| Format | Text | |
| Max Size | 400 | For each What's In The Box item. |
| Nullable | null | |
| Multi-value | No | One What's In The Box group for each market-language pair. |
Primary Product Image
Downloadable publicly accessible URL to a primary product image.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <HeroImage> | |
| Field name in XLS File | Primary Product Image | |
| Format | Text |
Each field should contain only one downloadable FTP or HTTP URL. Password-protected URLs are not supported.
The following image extensions are not supported: .gif,.eps,.zip,.exe,.ai,.psd,.ppt,.doc,.docx,.txt,.xls,.xml, .ps
|
| Max Size | 2000 | For each URL |
| Nullable | Not null | The feed should have at least one Image. |
| Multi-value | No |
Additional Images
Downloadable publicly accessible URLs to product Gallery / Multiple images. Primary product image does not have to be listed in the Gallery Images list.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <Images> | |
| Field name in XLS File | Additional Images | |
| Format | Text |
Each field should contain only one downloadable FTP or HTTP URL. Password-protected URLs are not supported. The following image extensions are not supported: .gif,.eps,.zip,.exe,.ai,.psd,.ppt,.doc,.docx,.txt,.xls,.xml, .ps
|
| Max Size | 2000 | For each URL |
| Nullable | null | |
| Multi-value | Yes |
Product Data Sheet
Downloadable publicly accessible URL to a document - typically a PDF or a DOC file - that provides an overview of the product and its technical specifications.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <PdfProductDataSheet> | |
| Field name in XLS File | Product Data Sheet | |
| Format | Text | Each field should contain only one downloadable FTP or HTTP URL. Password-protected URLs are not supported. |
| Max Size | 2000 | For each URL |
| Nullable | null | |
| Multi-value | Yes |
Product Brochure
Downloadable publicly accessible URL to a document - only in a PDF file format.
| Field Name | Value | Comment |
| Example | PartnerAccessDataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <ProductBrochures> | |
| Field name in XLS File | Product Brochures | |
| Format | Text | Each field should contain only one downloadable FTP or HTTP URL. Password-protected URLs are not supported. |
| Max Size | 2000 | For each URL |
| Nullable | null | |
| Multi-value | Yes |
User Manual
Downloadable publicly accessible URL to a document – only in a PDF file format.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <PdfUserManual> | |
| Field name in XLS File | User Manual | |
| Format | Text | Each field should contain only one downloadable FTP or HTTP URL. Password-protected URLs are not supported. |
| Max Size | 2000 | For each URL |
| Nullable | null | |
| Multi-value | Yes |
Quick Start Guide
Downloadable publicly accessible URL to a document - only in a PDF file format.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <PdfQuickStartGuide> | |
| Field name in XLS File | Quick Start Guide | |
| Format | Text | Each field should contain only one downloadable FTP or HTTP URL. Password-protected URLs are not supported. |
| Max Size | 2000 | For each URL |
| Nullable | null | |
| Multi-value | Yes |
Material Safety Data Sheet
Downloadable publicly accessible URL to a document - only in a PDF file format.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <PdfMsds> | |
| Field name in XLS File | Material Safety Data Sheet | |
| Format | Text | Each field should contain only one downloadable FTP or HTTP URL. Password-protected URLs are not supported. |
| Max Size | 2000 | For each URL |
| Nullable | null | |
| Multi-value | Yes |
Warranty Card
Downloadable publicly accessible URL to a document - only in a PDF file format.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <WarrantyCards> | |
| Field name in XLS File | Warranty Card | |
| Format | Text | Each field should contain only one downloadable FTP or HTTP URL. Password-protected URLs are not supported. |
| Max Size | 2000 | For each URL |
| Nullable | null | |
| Multi-value | Yes |
Installation Guide
Downloadable publicly accessible URL to a document - only in a PDF file format.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <InstallationGuide> | |
| Field name in XLS File | Installation Guide | |
| Format | Text | Each field should contain only one downloadable FTP or HTTP URL. Password-protected URLs are not supported. |
| Max Size | 2000 | For each URL |
| Nullable | null | |
| Multi-value | Yes |
Accessories
Product accessories part numbers.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <AccessoriesPartNumbers> | |
| Field name in XLS File | Accessories | PartNumber | value (one per line within the cell) |
| Format | Text | |
| Max Size | 40 | For each Part Number |
| Nullable | null | |
| Multi-value | No | Only one Accessories section can be defined in the feed. |
Main Products Part Numbers
Main products (parents) part numbers for the product.
| Field Name | Value | Comment |
| Example | PartnerAccess/DataSource Integration Example | |
| Source Code Example | Example | |
| Field name in XML File | <MainProductsPartNumbers> | |
| Field name in XLS File | Main Products Part Numbers | PartNumber | value (one per line within the cell) |
| Format | Text | |
| Max Size | 40 | For each Part Number |
| Nullable | null | |
| Multi-value | No | Only one Main Products Part Numbers section can be defined in the feed. |
Labels:
Version history
