Overview
The Awin product feed is the core data exchange mechanism that synchronises your product catalogue with the Awin affiliate network. Awin uses this feed to index your products, validate merchant data, enable affiliate marketing, and power performance tracking across thousands of publisher partners. A well-structured, complete feed directly impacts listing approval speed, product visibility in affiliate channels, and ultimately commission revenue.
Merchants submit product data to Awin via structured feeds (XML, CSV, or JSON). Awin validates each field against network requirements, maps your internal product identifiers to Awin's system, and distributes product information to affiliates, comparison shopping engines, and other integrated destinations.
Core Field Reference
The following table lists all standard Awin feed fields, their purpose, and data requirements.
| Field Name | Data Type | Required | Purpose | Impact on Performance |
|---|---|---|---|---|
| aw_product_id | String | Yes | Awin's unique product identifier assigned on first feed submission | Enables Awin to track product updates and performance metrics |
| merchant_product_id | String | Yes | Your internal product SKU or identifier | Links Awin data to your inventory system for synchronisation |
| product_name | String | Yes | Product title (max 150 characters recommended) | Used in affiliate listings and search indexing; truncation harms visibility |
| description | String | Yes | Full product description (HTML allowed) | Improves relevance in affiliate channels and search results |
| product_price_old | Decimal | No | Original or list price before discount | Displays savings; increases perceived value and click-through rate |
| price | Decimal | Yes | Current selling price | Determines product competitiveness and commission calculations |
| search_price | Decimal | No | Price used for comparison shopping; defaults to price if omitted | Controls visibility in price comparison channels |
| display_price | Decimal | No | Price shown to end users; defaults to price if omitted | Overrides price field for display purposes only |
| currency | String | Yes | ISO 4217 code (GBP, EUR, USD, etc.) | Ensures correct pricing in multi-currency environments |
| in_stock | Boolean | Yes | True if product is available, false otherwise | Prevents affiliates from promoting out-of-stock items |
| stock_quantity | Integer | No | Number of units available | Helps affiliates prioritise in-stock products; informs inventory management |
| category_name | String | Yes | Primary product category (Awin taxonomy) | Determines product classification and eligibility for category-specific campaigns |
| merchant_category | String | No | Your internal category structure | Supplements Awin category; useful for custom filtering |
| brand_name | String | Yes | Product brand or manufacturer | Enables brand-level filtering and affiliate targeting |
| product_type | String | No | Product classification (e.g. 'physical', 'digital', 'service') | Affects shipping, delivery, and commission rules |
| condition | String | No | Product state (new, refurbished, used) | Influences buyer confidence and affiliate channel eligibility |
| mpn | String | No | Manufacturer part number | Improves product matching and prevents duplicate listings |
| product_GTIN | String | No | Global Trade Item Number (barcode) | Enables cross-channel product matching and verification |
| ean | String | No | European Article Number (13-digit barcode) | Used for product identification in European markets |
| upc | String | No | Universal Product Code (12-digit barcode) | Used for product identification in North American markets |
| isbn | String | No | International Standard Book Number | Required for book products; enables precise matching |
| model_number | String | No | Product model identifier | Helps differentiate product variants and improves matching |
| product_model | String | No | Alternative model field; use if model_number unavailable | Provides fallback for variant identification |
| colour | String | No | Product colour or finish | Enables colour-based filtering in affiliate listings |
| size | String | No | Product size or dimensions | Critical for apparel, footwear, and home goods categories |
| material | String | No | Primary material composition | Influences product relevance in category-specific searches |
| pattern | String | No | Pattern or design (e.g. 'striped', 'floral', 'solid') | Supports visual search and style-based filtering |
| dimensions | String | No | Physical dimensions (format: LxWxH in cm or inches) | Used for shipping cost calculations and buyer decision-making |
| delivery_weight | Decimal | No | Product weight in kg or lbs | Required for accurate postage calculations |
| deep_link | String | Yes | URL to product page on your website | Directs affiliate traffic to correct product; must be unique per product |
| basket_link | String | No | Direct link to add product to shopping cart | Reduces friction and improves conversion when supported by affiliate channels |
| image_url | String | Yes | URL to primary product image (JPG, PNG; min 300x300px recommended) | Displayed in affiliate listings; missing or broken images reduce click-through |
| merchant_thumb | String | No | Thumbnail image URL (smaller version of image_url) | Optimises load times in affiliate feeds; improves user experience |
| alternate_image | String | No | Secondary product image URL | Provides additional visual context; improves product appeal |
| alternate_image_two | String | No | Third product image URL | Extends visual coverage for complex or multi-variant products |
| alternate_image_three | String | No | Fourth product image URL | Further visual documentation |
| alternate_image_four | String | No | Fifth product image URL | Maximum alternate image field in standard feed |
| large_image | String | No | High-resolution image URL for detailed product view | Used by premium affiliate channels and shopping engines |
| swatch | String | No | URL to colour or pattern swatch image | Critical for apparel and home décor; improves conversion |
| promotional_text | String | No | Marketing message or call-to-action (max 100 characters) | Highlights offers and encourages affiliate promotion |
| saving | Decimal | No | Discount amount or percentage; calculated if product_price_old provided | Displays savings message; increases perceived value |
| rrp_price | Decimal | No | Recommended retail price | Provides price context; influences buyer perception of value |
| store_price | Decimal | No | In-store price if different from online price | Enables omnichannel pricing transparency |
| delivery_time | String | No | Estimated delivery window (e.g. '2-3 business days', 'same day') | Influences buyer decision-making and affiliate messaging |
| delivery_cost | Decimal | No | Shipping cost to customer | Affects total price perception and checkout conversion |
| delivery_restrictions | String | No | Delivery limitations (e.g. 'UK mainland only', 'excludes Scottish Highlands') | Prevents unsuitable affiliate promotion and reduces returns |
| pre_order | Boolean | No | True if product is available for pre-order only | Manages buyer expectations and affiliate eligibility |
| valid_from | Date | No | Start date for product availability or promotion (YYYY-MM-DD) | Controls campaign timing and feed validity windows |
| valid_to | Date | No | End date for product availability or promotion (YYYY-MM-DD) | Prevents promotion of expired offers or discontinued products |
| warranty | String | No | Warranty terms or coverage period | Increases buyer confidence; often required by affiliate policies |
| reviews | Integer | No | Number of customer reviews or ratings received | Social proof; products with reviews see higher conversion |
| average_rating | Decimal | No | Average customer rating (typically 1-5 scale) | Displayed in affiliate listings; strongly influences click-through |
| rating | Decimal | No | Alternative rating field; use if average_rating unavailable | Provides fallback for rating data |
| keywords | String | No | Comma-separated search terms relevant to product | Improves search relevance within affiliate platforms |
| suitable_for | String | No | Intended use case or audience (e.g. 'men', 'outdoor', 'beginners') | Enables demographic and use-case filtering |
| specifications | String | No | Detailed product specifications (HTML allowed) | Supports informed purchasing decisions; improves SEO in affiliate channels |
| google_taxonomy | String | No | Google product category from official taxonomy | Required for certain comparison shopping integrations |
| energy_label | String | No | EU energy efficiency label (A-G scale) | Mandatory for certain product categories in EU markets |
| commission_group | String | No | Commission tier or group identifier | Links product to specific commission rates and affiliate tiers |
| custom1 to custom9 | String | No | Merchant-defined fields for proprietary data | Enables custom filtering, reporting, and integration logic |
| language | String | No | Product information language (ISO 639-1 code, e.g. 'en', 'de', 'fr') | Supports multi-language feed distribution |
| parent_product_id | String | No | aw_product_id of parent product in variant hierarchy | Groups related variants; improves product organisation |
| product_id | String | No | Alternative product identifier; use if aw_product_id unavailable | Provides fallback for product identification |
| last_updated | Timestamp | No | Date and time of last product data update (YYYY-MM-DD HH:MM:SS) | Helps Awin prioritise feed processing and detect stale data |
| web_offer | Boolean | No | True if product is exclusive to online channels | Manages channel-specific availability and affiliate eligibility |
Critical Fields for Feed Validation and Performance
Identifiers
Awin relies on unique, stable product identifiers to track updates and prevent duplicates. The aw_product_id field is assigned by Awin on first submission; you must retain and reuse this identifier in all subsequent feeds. The merchant_product_id must match your internal inventory system to enable real-time synchronisation. If you change merchant_product_id values between feeds, Awin treats them as new products, creating duplicates and breaking performance tracking.
Pricing Fields
Price accuracy directly affects commission calculations and competitive positioning. The price field is mandatory and must reflect the actual customer cost. If your products are sold at different prices in different channels, use search_price to control visibility in price comparison engines. The product_price_old field, when populated, automatically calculates and displays savings; this increases perceived value and click-through rates. Omit product_price_old if no discount applies, as displaying false savings violates affiliate policies and can result in feed rejection.
Product Images
Image quality and completeness significantly impact click-through and conversion. The image_url field must point to a high-quality JPG or PNG file with minimum dimensions of 300x300 pixels; smaller images appear blurry in affiliate listings and reduce engagement. Broken or missing image URLs cause Awin to reject products or display placeholder images, substantially reducing visibility. Provide alternate images (alternate_image, alternate_image_two, alternate_image_three, alternate_image_four) for products with multiple colours, angles, or configurations; products with multiple images see 20-30% higher click-through rates in affiliate channels.
Stock and Availability
The in_stock field must be updated in real-time or at least daily. Affiliates will promote out-of-stock products if this field is not current, leading to wasted clicks, poor affiliate relationships, and increased returns. The stock_quantity field is optional but recommended; it helps affiliates prioritise in-stock products and informs inventory-aware marketing strategies. Pre-order products must set pre_order to true and provide realistic delivery_time estimates.
Category and Taxonomy
The category_name field must use Awin's standard taxonomy to ensure correct product classification. Miscategorised products are invisible to category-specific affiliate campaigns and may be rejected during validation. Use merchant_category to supplement Awin's taxonomy with your own internal structure, enabling custom reporting and filtering. The google_taxonomy field, if provided, should match the official Google product taxonomy; this is required for certain comparison shopping integrations.
Feed Submission and Synchronisation
Frequency and Timing
Submit full product feed updates at least weekly, ideally daily. Awin processes feeds asynchronously; expect 2-24 hours for validation and indexing depending on feed size and complexity. Use the last_updated field to signal which products have changed; Awin can then prioritise processing of modified records. Batch updates during off-peak hours (late evening or early morning in your timezone) to avoid resource contention.
Feed Format
Awin accepts XML, CSV, and JSON formats. XML is the most widely used and provides the best support for nested data (e.g. multiple images or custom fields). CSV is simpler but offers limited support for complex data structures. JSON is useful if you are already generating feeds for other platforms. Choose the format that integrates most easily with your product information management (PIM) or e-commerce system.
Data Validation
Before submitting feeds, validate against these rules:
- All required fields (aw_product_id, merchant_product_id, product_name, description, price, currency, in_stock, category_name, brand_name, deep_link, image_url) must be present and non-empty.
- Prices must be numeric and greater than zero; currency codes must be valid ISO 4217 codes.
- URLs (deep_link, image_url, alternate images) must be absolute, valid, and publicly accessible; test each URL before submission.
- Dates must follow YYYY-MM-DD format; timestamps must include time in HH:MM:SS format.
- Boolean fields (in_stock, pre_order, web_offer) must be true or false (not 'yes', 'no', '1', '0').
- Category names must match Awin's official taxonomy; use Awin's category lookup tool to verify.
- Image dimensions must be at least 300x300 pixels; use JPG or PNG format only.
- Product names should be 50-150 characters; avoid excessive punctuation or keyword stuffing.
- Descriptions should be 100-500 characters and include key product attributes; avoid duplicate descriptions across products.
- Barcode fields (product_GTIN, ean, upc, isbn) must be valid and correctly formatted.
Handling Product Variants
For products with multiple variants (colour, size, style), create separate feed entries for each variant with unique merchant_product_id and aw_product_id values. Populate the parent_product_id field with the aw_product_id of the base product to establish the variant hierarchy. This allows affiliates to filter by specific variants while maintaining product grouping for reporting.
Optimisation Strategies
Maximise Visibility
Feed completeness directly correlates with visibility. Products with all optional fields populated (colour, size, material, specifications, reviews, rating, keywords) rank higher in affiliate search results and are eligible for more campaigns. Aim for 80% field completion as a minimum; premium merchants achieve 95%+.
Include rich, unique descriptions for each product. Avoid copying descriptions from manufacturers or competitors; write product-specific copy that highlights key benefits and differentiators. Use natural language and include relevant keywords (e.g. 'waterproof hiking boots' instead of just 'boots').
Provide multiple high-quality images. Products with 3+ images see 25-40% higher engagement than single-image products. Ensure images show the product from multiple angles, in use, and with size context (e.g. product next to a hand or ruler).
Improve Commission Performance
Use the commission_group field to tier products by profitability. Assign higher commission rates to high-margin products to encourage affiliate promotion. Use promotional_text to highlight limited-time offers and drive urgency. Populate saving and rrp_price fields to display discounts; products with visible savings see 15-20% higher click-through rates.
Set accurate delivery_time and delivery_cost values. Affiliates use these to calculate total cost and influence messaging; unrealistic delivery expectations increase returns and damage affiliate relationships.
Reduce Validation Errors
Common rejection reasons include broken image URLs, invalid category names, and mismatched currency codes. Test all image URLs weekly using an automated link checker. Maintain a mapping of your internal categories to Awin's official taxonomy; update this mapping whenever you add new product categories. Standardise currency codes across all products in a single feed; do not mix GBP and EUR in the same submission.
Leverage Custom Fields
Use custom1 through custom9 fields to store data specific to your business. Examples include internal cost, supplier ID, seasonal tag, or affiliate exclusion flag. This data is not displayed to end users but can be used for internal reporting, filtering, and integration logic. Document your custom field usage in a data dictionary to ensure consistency across teams and systems.
Practical Implementation Checklist
Before launching your Awin feed, complete the following:
- Map your internal product database to Awin field names; identify which fields you can populate automatically and which require manual entry.
- Validate that your e-commerce platform or PIM system can export data in your chosen format (XML, CSV, or JSON).
- Create a test feed with 10-20 representative products from different categories; submit to Awin's staging environment and review validation errors.
- Establish a daily or weekly feed generation schedule; automate export and submission if possible.
- Set up monitoring to track feed submission success, validation error rates, and product approval status.
- Document your category mapping, custom field definitions, and any conditional logic (e.g. rules for setting in_stock based on inventory levels).
- Train your product and marketing teams on feed requirements; establish a process for updating product data (descriptions, images, pricing) that flows through to the feed.
- Review Awin's feed validation reports weekly; prioritise fixing high-volume errors (e.g. broken images, missing categories) that affect many products.
- Monitor affiliate feedback and performance by product category; use this insight to improve feed data quality and product positioning.
- Test the deep_link and basket_link URLs monthly to ensure they remain valid and functional.
Summary
The Awin product feed is the foundation of your affiliate marketing presence. A complete, accurate, and regularly updated feed directly impacts product visibility, affiliate engagement, and commission revenue. Prioritise the core required fields first (identifiers, pricing, images, availability, category), then progressively populate optional fields to maximise visibility and performance. Implement automated feed generation and validation wherever possible to reduce manual effort and error rates. Review Awin's feed validation reports regularly and address errors systematically. By following these technical guidelines and optimisation strategies, you will establish a high-performing feed that drives sustainable affiliate revenue growth.