What Is a Dealer Stock Feed?
A dealer stock feed is an automated data file that contains your complete vehicle inventory, formatted in a standardised structure that external platforms can read and process. Rather than manually uploading each vehicle to multiple listing sites, the feed allows your inventory management system to broadcast stock information automatically, typically updating every 15 minutes to 24 hours depending on the platform. This file includes essential details such as registration number, make, model, price, mileage, specification, and images, packaged in a format that third-party systems can parse and display.
Stock feeds eliminate the manual work of maintaining listings across multiple channels. When you sell a vehicle or adjust a price in your dealer management system (DMS), those changes propagate automatically to every connected platform. For dealers listing on multiple sites, this automation prevents the common problem of advertising vehicles that have already sold, which damages customer trust and wastes staff time fielding enquiries for unavailable stock.
The feed operates as a one-way data transmission from your system to external platforms. Most feeds use either XML (Extensible Markup Language) or JSON (JavaScript Object Notation) formats, with XML remaining the dominant standard in the UK automotive sector. The file sits on a web server, and listing platforms retrieve it at regular intervals, comparing the new data against their existing records to identify additions, changes, and deletions.
Understanding XML Format for Vehicle Listings
XML structures data using nested tags that describe each piece of information. A basic vehicle entry in XML format contains opening and closing tags for each data field, creating a hierarchical structure that machines can reliably interpret. For example, a price might appear as <price>15995</price>, where the tags identify what the number represents and the content between them provides the actual value.
The format's strength lies in its flexibility and human readability. Unlike proprietary binary formats, you can open an XML file in any text editor and understand its contents. Each vehicle in the feed typically appears within a <vehicle> or <car> tag, containing nested elements for registration, make, model, derivative, colour, mileage, fuel type, transmission, doors, and other attributes. Image URLs usually appear as separate tags, either within the main vehicle block or in a dedicated images section.
XML feeds include a declaration at the top specifying the encoding (usually UTF-8) and version, followed by a root element that contains all vehicle entries. Well-formed XML must follow strict syntax rules: every opening tag requires a matching closing tag, attribute values must appear in quotes, and tags must nest properly without overlap. These rules ensure that automated systems can parse the file without ambiguity, preventing data corruption when your stock information reaches listing platforms.
Common Stock Feed Formats in the UK Market
The UK automotive industry uses several competing XML standards, each with different tag names, structures, and required fields. The most widely adopted format is the AutosOnShow (AOS) standard, originally developed by a consortium of dealers and software providers. This format uses tags like <vrm> for registration numbers, <capid> for CAP identification codes, and <retailprice> for asking prices. Many DMS providers and listing platforms support AOS as their primary or fallback format.
Motors.co.uk developed its own XML schema, which some platforms still accept alongside or instead of AOS. The Motors format uses slightly different tag names and structures certain data differently, particularly around images and optional equipment. AutoTrader historically required its own proprietary format, though modern integration often happens through direct API connections rather than XML files.
Some DMS providers have created their own variants, adding custom fields or restructuring standard elements to suit their internal data models. This fragmentation means dealers often need multiple feed formats to cover all their chosen listing platforms. Progressive platforms now accept multiple formats, automatically detecting which standard an incoming feed uses and transforming it internally, reducing the integration burden on dealers.
Essential Data Fields Every Stock Feed Must Include
Regardless of format, certain fields appear in every functional vehicle feed. The registration number (VRN or VRM) serves as the unique identifier, allowing platforms to match vehicles across updates and prevent duplicate listings. Make and model fields identify the manufacturer and model name, while derivative or trim level provides the specific variant (for example, "1.5 TSI SE Technology" rather than just "Golf").
Price information requires careful specification. Most feeds include a retail price field, and some platforms also accept trade or part-exchange values. The currency should be explicit (GBP for UK dealers), and the figure should represent the on-the-road price including VAT where applicable. Mileage appears as a numeric value with an accompanying unit (typically miles in the UK), and the odometer reading date helps buyers understand how current the figure is.
Technical specifications form the next essential layer: fuel type (petrol, diesel, electric, hybrid), transmission type (manual, automatic, semi-automatic), engine size (usually in litres or cc), body type (hatchback, saloon, SUV, etc.), number of doors, number of seats, and exterior colour. Registration date or year of manufacture helps buyers filter by age, while MOT expiry date provides important roadworthiness information that builds buyer confidence.
Optional Fields That Improve Listing Performance
Beyond the mandatory basics, additional fields significantly improve how your vehicles appear in search results and attract buyer interest. A detailed description field allows you to highlight unique selling points, service history, and condition notes that don't fit into structured fields. Well-written descriptions improve conversion rates, particularly for higher-value or unusual vehicles where buyers need more context.
Image URLs deserve careful attention. Most feeds support multiple images per vehicle, typically between 10 and 50. The order matters; your primary image should showcase the vehicle's best angle, usually a three-quarter front view in good lighting. Subsequent images should cover all exterior angles, interior cabin, boot space, engine bay, and any notable features or imperfections. High-resolution images (minimum 800 pixels wide, ideally 1200+) display better on modern devices and allow buyers to zoom in on details.
Service history indicators, number of previous owners, and warranty information build trust. If your DMS tracks this data, including it in the feed helps serious buyers shortlist your vehicles. Optional equipment lists (sat-nav, leather seats, parking sensors, etc.) allow buyers to find vehicles with their must-have features. Some advanced feeds include finance examples, showing monthly payment options that help buyers understand affordability at a glance.
How Stock Feeds Connect to Listing Platforms
The technical connection between your feed and listing platforms typically follows one of two patterns: pull or push. In a pull model, your DMS or website generates an XML file and places it at a fixed URL (for example, https://yourdealership.co.uk/stock-feed.xml). The listing platform retrieves this file at regular intervals, checking for changes and updating its database accordingly. This approach requires minimal configuration on your side once the initial URL is provided.
Push models reverse the flow: your system actively sends updated data to the platform whenever changes occur. This usually happens through an API (Application Programming Interface) where your DMS makes HTTP requests to the platform's servers, transmitting new or modified vehicle records in real-time. Push systems offer faster updates, with sold vehicles disappearing from listings within minutes rather than waiting for the next scheduled pull.
Some platforms support both methods, allowing dealers to choose based on their technical capabilities and update frequency requirements. Integrating your dealer stock feed with modern platforms has become increasingly straightforward, with many providers offering step-by-step wizards that detect your feed format automatically and map fields without manual configuration.
Feed Validation and Common Technical Issues
XML feeds must validate against the platform's expected schema to process successfully. Validation checks ensure that required fields are present, data types match expectations (numbers in numeric fields, dates in date fields), and the overall structure follows the standard. Many platforms provide validation tools where you can upload or link your feed and receive a report identifying any errors or warnings before going live.
Common problems include malformed XML syntax (unclosed tags, special characters not properly escaped), missing mandatory fields, incorrect data formats (text in numeric fields, invalid date formats), and broken image URLs. Character encoding issues cause particular frustration; if your DMS exports descriptions containing special characters (pound signs, apostrophes, accented letters) without proper UTF-8 encoding, the XML parser may reject the entire feed.
Image hosting represents another frequent pain point. External platforms must be able to access your image URLs over the public internet, which means images stored on internal servers behind firewalls won't display. The URLs should use HTTPS rather than HTTP for security, and the image files should remain at stable URLs rather than changing filenames with each export. Some dealers solve this by hosting images on cloud storage services (AWS S3, Azure Blob Storage) that provide reliable, fast access.
Managing Stock Feeds Across Multiple Platforms
Dealers typically advertise on several platforms simultaneously, each potentially requiring a different feed format or configuration. The most efficient approach uses your DMS as the single source of truth, generating multiple feed formats from one central inventory database. Modern DMS systems include feed management modules that can export your stock in various formats, allowing you to serve different platforms without maintaining separate data sets.
When managing multiple feeds, consistency becomes critical. Price changes, mileage updates, and sold vehicles should reflect across all platforms simultaneously to prevent customer confusion and wasted enquiries. Some dealers schedule feed updates to run every hour, ensuring that major changes propagate quickly while balancing server load and platform update frequencies.
The total cost of ownership for dealer advertising platforms includes not just subscription fees but also the staff time required to manage feeds and troubleshoot integration issues. Platforms that charge thousands monthly often provide dedicated technical support for feed problems, while free alternatives may require more self-service problem-solving. However, the technical complexity of XML feeds has decreased significantly, with many free platforms now offering integration quality that matches or exceeds paid competitors.
Stock Feed Best Practices for Maximum Visibility
Update frequency directly impacts how quickly your inventory changes appear to buyers. Daily updates represent the minimum acceptable standard, with hourly or real-time updates providing the best customer experience. Sold vehicles that remain advertised for hours or days frustrate buyers and damage your reputation, while newly arrived stock that takes 24 hours to appear gives competitors a head start.
Image quality and quantity matter more than many dealers realise. Feeds with 15-20 high-resolution images per vehicle consistently outperform those with 5-6 basic shots. Buyers want to see every angle, interior details, boot space, and any cosmetic imperfections. Consistent photography style across your inventory (same background, lighting, angles) creates a professional impression that builds trust.
Descriptions should be detailed but scannable. Include key selling points in the first sentence (low mileage, full service history, recent MOT), then expand with specification highlights, condition notes, and any unique features. Avoid generic template text that applies to any vehicle; specific details about this particular car perform better in both traditional search engines and AI-powered discovery tools.
The Role of Stock Feeds in Modern Vehicle Discovery
Search engines and AI assistants increasingly rely on structured data to understand and recommend vehicles. A well-formatted stock feed provides this structure, allowing your inventory to appear in voice search results, AI chat responses, and featured snippets. When a buyer asks an AI assistant to "find diesel SUVs under £20,000 near Manchester," platforms with clean, comprehensive feeds can match and present relevant vehicles accurately.
This shift towards AI-powered vehicle discovery means feed quality affects not just how your vehicles appear on listing sites but also whether they surface in next-generation search experiences. Fields like precise location data (postcode, latitude/longitude), detailed specifications, and accurate categorisation help AI systems understand which vehicles match complex, conversational queries.
Platforms that route traffic directly to dealer websites rather than keeping buyers on a marketplace preserve your customer relationships and brand identity. When evaluating where to send your stock feed, consider not just the audience size but also why direct-to-dealer traffic matters for building long-term customer relationships and avoiding commission fees on completed sales.
Future-Proofing Your Stock Feed Strategy
The automotive data landscape continues evolving, with new standards emerging and existing formats expanding to accommodate electric vehicles, subscription models, and enhanced media types. Future-proof feeds include fields for battery capacity, electric range, charging speed, and emissions data that buyers increasingly prioritise when comparing vehicles.
Video content integration represents the next frontier. Some platforms now accept video URLs within stock feeds, displaying walkaround videos, test drive footage, or detailed feature demonstrations alongside static images. As bandwidth costs decrease and buyer expectations rise, video will likely become standard rather than optional.
API-based integrations are gradually replacing file-based XML feeds for some applications, offering real-time two-way communication between systems. Rather than generating a complete file periodically, API integrations can push individual vehicle updates instantly and receive confirmation that the change processed successfully. However, XML feeds remain the most widely compatible option, supported by virtually every platform and DMS in the UK market.
Frequently Asked Questions
How often should I update my stock feed?
Update your stock feed at least once daily, with hourly or real-time updates providing the best customer experience. Most modern DMS systems can generate feeds automatically every hour without manual intervention. Platforms typically check for updates between every 15 minutes and 24 hours depending on their architecture, so more frequent updates ensure changes propagate quickly. Sold vehicles should disappear from all listings within hours rather than days to prevent wasted enquiries and customer frustration.
Can I use one stock feed for multiple listing platforms?
You can often use one feed for multiple platforms if they accept the same format (such as AutosOnShow standard), but many platforms require format-specific variations. Modern DMS systems solve this by generating multiple feed formats from your single inventory database. Rather than maintaining separate data for each platform, you update your stock once and the system exports appropriate formats for each destination. Some aggregators also accept a single feed and redistribute it to multiple platforms, though this adds an intermediary layer.
What happens if my stock feed contains errors?
Most platforms validate feeds before processing and will reject feeds with critical errors like malformed XML or missing mandatory fields. Minor errors (missing optional fields, invalid image URLs) typically result in partial processing, where valid vehicles appear but problematic entries are skipped. Platforms usually provide error logs identifying specific issues, allowing you to correct problems in your source data or export configuration. Regular validation using platform-provided tools helps catch errors before they affect live listings.
Do I need technical expertise to set up a stock feed?
Basic stock feed setup requires minimal technical knowledge if your DMS includes feed generation functionality. Most modern systems provide wizards that guide you through selecting fields, choosing output format, and specifying where to publish the file. The DMS handles the XML generation automatically. However, troubleshooting validation errors, configuring custom field mappings, or setting up advanced features may require assistance from your DMS provider's support team or a technical colleague.
How do stock feeds handle sold vehicles?
When you mark a vehicle as sold in your DMS, the next feed generation should exclude that vehicle entirely. Listing platforms compare the new feed against their existing records and remove any vehicles that no longer appear. This is why update frequency matters; if your feed only updates daily, a vehicle sold this morning may continue appearing on listing sites until tomorrow's update. Some advanced integrations support explicit deletion messages, immediately notifying platforms when specific vehicles sell rather than waiting for the next full feed refresh.