Overview
The Awin product feed is a structured data format that merchants use to supply product information to the Awin affiliate network. Awin uses this feed to populate product listings across its affiliate partner network, enabling publishers to promote merchant products with accurate, up-to-date information. The feed serves as the single source of truth for product details, pricing, availability, and categorisation across all Awin-affiliated promotional channels.
Merchants submit product feeds to Awin to ensure their products appear correctly in affiliate marketing campaigns, comparison shopping tools, and promotional content managed by Awin's publisher partners. Without a properly structured feed, products may be rejected during approval, displayed with incomplete information, or excluded from high-performing campaigns.
Core Product Feed Fields
The Awin product feed uses a defined set of fields to describe each product. The following table outlines the primary fields, their purpose, and data requirements.
| Field | Purpose | Data Type | Required | Notes |
|---|---|---|---|---|
| aw_product_id | Unique identifier assigned by Awin | String | Yes | Generated by Awin; do not modify |
| merchant_product_id | Your internal product identifier | String | Yes | Must be unique within your feed; used for tracking and reconciliation |
| product_name | Product title for display | String | Yes | Keep under 150 characters; include key attributes like colour or size variant |
| description | Detailed product description | String | Yes | 50 to 5000 characters; should highlight features, materials, and use cases |
| brand_name | Manufacturer or brand name | String | Yes | Must match official brand name; affects searchability and filtering |
| product_type | Category classification for the product | String | Yes | Use consistent taxonomy; affects how Awin categorises the product |
| search_price | Price used for search and comparison | Decimal | Yes | Include currency code; affects price-based filtering in affiliate tools |
| display_price | Price shown to end consumers | Decimal | No | If omitted, search_price is used for display |
| product_price_old | Previous or RRP for comparison | Decimal | No | Shown alongside current price to highlight discounts |
| currency | ISO 4217 currency code | String | Yes | Examples: GBP, EUR, USD; must match your market |
| in_stock | Product availability status | Boolean or String | Yes | Values: true, false, or 'in stock', 'out of stock' |
| stock_quantity | Number of units available | Integer | No | Helps Awin publishers prioritise in-stock items |
| category_name | Awin standard category | String | Yes | Must match Awin's predefined category taxonomy |
| merchant_category | Your internal category structure | String | No | Complements category_name; useful for your own reporting |
| colour | Product colour variant | String | No | Include only if product is available in multiple colours |
| condition | Product condition status | String | No | Values: New, Refurbished, Used |
| mpn | Manufacturer part number | String | No | Improves product matching and deduplication |
| product_model | Model name or number | String | No | Distinguishes variants within a product line |
| merchant_image_url | Direct URL to product image | URL | No | HTTPS required; 500x500 pixels minimum; JPG or PNG format |
| specifications | Additional product specifications | String | No | Structured as key:value pairs or JSON; supports up to 2000 characters |
Field Mapping and Data Requirements
Identifier Fields
Both aw_product_id and merchant_product_id serve distinct purposes. The aw_product_id is assigned by Awin when your feed is first processed and acts as Awin's internal reference. The merchant_product_id is your responsibility; it must uniquely identify each product in your catalogue and remain consistent across feed submissions. If you change a merchant_product_id between submissions, Awin treats it as a new product, breaking historical performance data and affiliate tracking.
Use your internal SKU or product database identifier for merchant_product_id. If your products have variants (size, colour, material), create a separate feed entry for each variant with a distinct merchant_product_id. Do not reuse the same merchant_product_id for different products or variants.
Pricing Fields
The search_price field is mandatory and used by Awin's affiliate partners to filter products by price range in campaigns and comparison tools. Set search_price to the current selling price after any discounts or promotions.
The display_price field is optional. If you provide both search_price and display_price, Awin may display the display_price to consumers while using search_price for filtering logic. If display_price is omitted, search_price is used for both purposes.
The product_price_old field allows you to show a previous price or recommended retail price (RRP) alongside the current price. This field is useful for highlighting discounts. Always ensure product_price_old is higher than search_price; if it is lower or equal, Awin may reject the entry or ignore the field.
All prices must be submitted as decimal numbers without currency symbols. The currency field specifies the currency code separately. Example: search_price value is 29.99, currency value is GBP.
Categorisation Fields
The category_name field must match one of Awin's predefined categories. Awin maintains a fixed taxonomy of categories such as 'Electronics > Computers > Laptops', 'Fashion > Womens > Dresses', or 'Home & Garden > Furniture > Sofas'. Using an incorrect or non-standard category name causes feed rejection or miscategorisation.
Before submitting your feed, obtain the complete Awin category list from your Awin account manager or the Awin merchant portal. Map each of your products to the most specific Awin category available. If a product does not fit neatly into a single category, choose the primary category where most affiliate partners would search for it.
The merchant_category field is optional and allows you to include your own internal category structure alongside the Awin category. This is useful for your own reporting and reconciliation but does not affect how Awin processes or displays the product.
Product Description and Attributes
The product_name field is the primary title shown to consumers and affiliate publishers. Keep it concise (under 150 characters) but descriptive. Include key attributes such as colour, size, or material if the variant is important. Avoid generic names like 'Item' or 'Product'. Example: 'Blue Cotton T-Shirt, Size M' is better than 'T-Shirt'.
The description field should provide detailed information about the product. Use natural language and focus on features, benefits, materials, dimensions, and care instructions. Aim for 100 to 500 words depending on product complexity. Awin publishers often use the description in their promotional content, so clear, engaging copy improves conversion rates.
The colour field should be used only if the product is available in multiple colour variants. If you are submitting separate feed entries for each colour, include the colour value in product_name and optionally in the colour field. Do not include colour in the colour field if the product is only available in one colour.
Stock and Availability
The in_stock field indicates whether the product is currently available for purchase. Use a boolean value (true/false) or string value ('in stock' / 'out of stock'). Awin publishers use this field to filter products; out-of-stock items are typically excluded from active campaigns.
The stock_quantity field is optional but recommended. If provided, it allows Awin to show real-time stock levels to publishers, helping them prioritise in-stock items and avoid promoting products with limited availability. Stock_quantity should be an integer representing the number of units available.
Update the in_stock field and stock_quantity in every feed submission. If your inventory changes frequently, consider submitting updated feeds daily or multiple times per day to keep stock status current.
Image URLs and Visual Assets
The merchant_image_url field should contain a direct, publicly accessible HTTPS URL to the product image. The image must be:
- Minimum 500x500 pixels in size.
- In JPG or PNG format.
- Hosted on a reliable server with high uptime.
- Accessible without authentication or login.
Awin and its affiliate partners use this image in promotional materials, comparison tools, and publisher websites. A missing or broken image URL results in a blank product tile, reducing click-through rates and conversions.
Test all image URLs before submitting your feed. Use a URL checker tool to verify that each URL returns a 200 HTTP status code and displays the correct image. If you change image URLs between feed submissions, ensure old URLs remain accessible for at least 30 days to avoid broken images in cached content.
Product Identification and Specifications
The mpn (manufacturer part number) field should contain the official part number assigned by the product manufacturer. The mpn helps Awin deduplicate products across multiple merchants and improves product matching in comparison tools. If your product does not have an mpn, leave this field empty.
The product_model field contains the model name or number. Use this to distinguish variants within a product line, such as 'iPhone 15 Pro' or 'Canon EOS R5'. If your product_name already includes the model, you may omit the product_model field.
The specifications field allows you to include additional structured data about the product. Format specifications as key:value pairs separated by semicolons, or as JSON. Example: 'Material: Cotton; Weight: 200g; Warranty: 1 Year'. Limit specifications to 2000 characters. Awin publishers may use specifications in detailed product comparisons, so include relevant technical details.
The condition field indicates the product condition: 'New', 'Refurbished', or 'Used'. If omitted, Awin assumes 'New'. Use 'Refurbished' for products that have been restored to working condition by the manufacturer or a certified refurbisher. Use 'Used' only for genuine second-hand items sold as-is.
Feed Submission and Validation
Feed Format and Structure
Awin accepts product feeds in XML, CSV, and JSON formats. The most common format is XML, specified in the Awin XML product feed specifications and field mapping guide.
When preparing your feed, ensure that:
- All required fields are present in every product entry.
- Field values are properly encoded and escaped (e.g., ampersands as & in XML).
- Prices are formatted as decimal numbers with up to two decimal places.
- Dates, if included, use ISO 8601 format (YYYY-MM-DD).
- The feed file is valid according to the XML schema or CSV format specification.
Feed Upload and Processing
Merchants upload feeds to Awin via the merchant portal or via a direct HTTPS POST request to the Awin feed API endpoint. Your Awin account manager provides the API endpoint URL and authentication credentials.
After upload, Awin processes the feed asynchronously. Processing typically takes 1 to 4 hours depending on feed size. During processing, Awin validates each product entry against the field requirements and category taxonomy. Products with missing required fields, invalid prices, or incorrect categories are flagged with error messages.
Access the feed processing status and error report in the Awin merchant portal. Review error reports carefully and correct any issues before resubmitting. Common errors include:
- Missing or empty required fields (product_name, description, search_price, category_name).
- Invalid category_name values that do not match Awin's taxonomy.
- Malformed URLs in merchant_image_url.
- Prices with invalid formatting (e.g., '£29.99' instead of '29.99').
- Currency codes that do not match the merchant account's primary currency.
Feed Update Frequency
Awin recommends submitting updated feeds at least once per week. If your inventory or prices change frequently, submit feeds daily or multiple times per day. More frequent updates ensure that affiliate partners have current stock and pricing information, improving campaign performance and reducing returns due to out-of-stock items.
Set up an automated feed generation and submission process if possible. Use your product database or e-commerce platform to generate the feed directly, rather than manually creating or editing feed files. Automation reduces errors and ensures consistency.
Optimisation Strategies
Improving Feed Approval and Visibility
Awin's approval process evaluates feeds for completeness, accuracy, and compliance with its guidelines. To improve approval rates:
- Provide accurate, detailed product descriptions. Avoid placeholder text or generic descriptions copied from other sources.
- Use high-quality, original product images. Avoid watermarked or low-resolution images.
- Ensure category_name values exactly match Awin's predefined taxonomy. Use the Awin category tool or your account manager's guidance to verify.
- Include brand_name for all products. Affiliate publishers often filter by brand, and missing brand data reduces visibility.
- Set in_stock to true only for products with positive stock_quantity. Out-of-stock products should have in_stock set to false.
- Verify that search_price and display_price are realistic and match your website's actual selling price. Mismatched prices cause publisher complaints and feed rejection.
Enhancing Affiliate Performance
Affiliates use product feed data to create promotional content. To improve affiliate engagement and conversion rates:
- Write compelling product descriptions that highlight unique selling points, benefits, and differentiators. Include specific details such as materials, dimensions, and warranty information.
- Provide accurate colour and product_model information. Affiliates use this to create targeted campaigns for specific product variants.
- Include product_price_old to highlight discounts. Products with visible savings generate higher click-through rates.
- Use the specifications field to include relevant technical details, certifications, or awards. This helps affiliates position the product in comparison content.
- Ensure merchant_image_url points to high-quality, professional product images. Affiliates use these images in their promotional materials; poor images reflect poorly on both the product and the affiliate.
- Update stock_quantity accurately. Publishers prioritise products with high stock levels in their campaigns.
Handling Product Variants and SKUs
If your product catalogue includes variants (different sizes, colours, or configurations), create a separate feed entry for each variant. Each entry must have a unique merchant_product_id and should include variant-specific information in product_name, colour, product_model, and specifications fields.
Example: If you sell a T-shirt in three colours (blue, red, black) and two sizes (S, M, L), create six separate feed entries:
- merchant_product_id: 'TSHIRT-001-BLUE-S', product_name: 'Blue Cotton T-Shirt, Size S'
- merchant_product_id: 'TSHIRT-001-BLUE-M', product_name: 'Blue Cotton T-Shirt, Size M'
- merchant_product_id: 'TSHIRT-001-RED-S', product_name: 'Red Cotton T-Shirt, Size S'
- And so on.
This approach allows Awin and its affiliate partners to promote specific variants and track performance separately. If you submit a single entry for all variants, publishers cannot promote specific sizes or colours, reducing campaign effectiveness.
Currency and Market Considerations
Ensure that the currency field matches your merchant account's primary currency. If you operate in multiple markets (e.g., GBP for UK, EUR for EU), submit separate feeds for each market with the appropriate currency code.
If Awin requires feed submission in a specific currency (e.g., always in GBP), convert prices from your local currency using current exchange rates. Update exchange rates regularly (at least weekly) to keep prices accurate.
Avoid mixing currencies within a single feed. If a product is sold in both GBP and EUR, create separate entries with different merchant_product_ids and currency values.
Troubleshooting Common Issues
Feed Rejection and Error Messages
If your feed is rejected during processing, check the error report in the Awin merchant portal. Common issues and solutions:
Missing Required Fields: Ensure all products have values for product_name, description, search_price, category_name, brand_name, and in_stock. Do not submit empty strings or null values for required fields.
Invalid Category Names: Verify that category_name values exactly match Awin's predefined categories. Use the category lookup tool in the merchant portal or request the full category list from your Awin account manager.
Malformed Prices: Ensure prices are formatted as decimal numbers without currency symbols or thousand separators. Example: 1299.99, not '£1,299.99' or '1.299,99'.
Broken Image URLs: Test all merchant_image_url values before submission. Use an online URL checker or curl command to verify that each URL returns a 200 status code and displays the correct image.
Character Encoding Issues: If your feed contains special characters (accents, symbols), ensure the feed file is saved in UTF-8 encoding. XML feeds should include the encoding declaration: <?xml version="1.0" encoding="UTF-8"?>.
Performance and Visibility Issues
If your products are approved but receiving low traffic or conversions:
- Review affiliate campaign reports in the Awin merchant portal. Identify which products are being promoted and which are not.
- Check that product descriptions and images are compelling. Affiliates may avoid promoting products with poor descriptions or missing images.
- Verify that prices are competitive. If your search_price is significantly higher than competitors, affiliates may prioritise other products.
- Ensure that in_stock and stock_quantity are updated frequently. Out-of-stock products are excluded from campaigns.
- Consider adding product_price_old to highlight discounts. Products with visible savings generate more interest.
- Review category_name assignments. If a product is in the wrong category, it may not be found by affiliates searching for that product type.
Summary
The Awin product feed is the foundation of your affiliate marketing presence on the Awin network. A well-structured, complete, and frequently updated feed ensures that your products are approved, visible to affiliate publishers, and promoted effectively.
Focus on providing accurate, detailed product information across all required fields. Pay particular attention to product descriptions, images, pricing, and category assignments, as these directly influence affiliate engagement and campaign performance.
Submit updated feeds regularly (at least weekly, ideally daily) to keep inventory and pricing current. Monitor feed processing reports and address any errors or warnings promptly. Use the Awin merchant portal to track product performance and publisher feedback, and iterate on your feed content based on campaign results.
By following these guidelines and maintaining feed quality, you will maximise your visibility on the Awin network and drive higher affiliate-generated sales.