Automotive Automation
Automated Car Listing Videos for Dealerships
Map vehicle inventory into a Zvid template with an iterated photo gallery, optional price states, specs, dealer CTA, and review.
Published July 18, 2026

Automated Car Listing Videos for Dealerships
Automated car listing videos work when the dealership feed supplies clean vehicle data and a reusable template controls the creative. In Zvid, the template can swap the year, make, model, price, dealer, phone, CTA, driving clip, and photo array; repeat one gallery scene for each photo; and hide optional price or disclaimer elements with conditions.
The important word is “listing.” This is not a cinematic video invented from a VIN. The output should accurately represent a real inventory record, use approved vehicle media, and preserve dealer review before it reaches a vehicle detail page or social channel.
Zvid's Template Basics and Dynamic Content guide cover the variable, condition, and iteration model used here. The visual system can be built and tested in the Zvid Editor before it becomes an API template.

Map approved vehicle fields into one reusable listing-video template.
Normalize the vehicle before touching the template
Dealer feeds use different field names and conventions. Build one internal vehicle contract and keep source-specific translation outside the creative.
{
"stockId": "CPO-1842",
"year": "2024",
"make": "Example Motors",
"model": "Apex GT",
"trim": "Touring",
"mileage": "12,480 mi",
"transmission": "Automatic",
"drivetrain": "AWD",
"price": "$38,900",
"showPrice": true,
"dealerName": "Northline Auto",
"phone": "+1 555 014 8820",
"cta": "Schedule a test drive",
"drivingVideoUrl": "https://cdn.example.com/inventory/CPO-1842/drive.mp4",
"photos": [
{ "url": "https://cdn.example.com/inventory/CPO-1842/front.webp", "label": "Front three-quarter" },
{ "url": "https://cdn.example.com/inventory/CPO-1842/interior.webp", "label": "Cabin" },
{ "url": "https://cdn.example.com/inventory/CPO-1842/cargo.webp", "label": "Cargo space" }
]
}
The values are illustrative, not a real dealership claim. In production, every field should come from the approved inventory source.
Normalize before rendering:
- Choose one display format for mileage and price.
- Remove placeholder photos and unsupported file types.
- Order the gallery deliberately.
- Decide whether a blank price hides the price or blocks the video.
- Keep public and internal notes separate.
- Validate phone, dealer name, and CTA against the destination channel.
- Preserve the source stock ID for reconciliation.
Design the template around one vehicle story
A practical listing video has four roles:
- Hook: identify the vehicle quickly with real footage or the best hero image.
- Gallery: show approved exterior and interior views.
- Specs: present a small number of decision-relevant facts.
- Dealer CTA: make the next action and source clear.
Do not turn the feed into a wall of text. Viewers do not need every equipment code in a fifteen-second reel. Select the facts that match the channel and link to the full VDP for detail.
Use variables for facts and media slots
The template declares defaults so it can be previewed before request data arrives.
{
"variables": {
"year": "2024",
"vehicle": "Example Motors Apex GT",
"trim": "Touring AWD",
"mileage": "12,480 mi",
"price": "$38,900",
"showPrice": true,
"dealerName": "Northline Auto",
"phone": "+1 555 014 8820",
"cta": "Schedule a test drive",
"drivingVideoUrl": "https://videos.pexels.com/video-files/5309381/5309381-hd_1920_1080_25fps.mp4",
"photos": [
{ "url": "https://images.pexels.com/photos/116675/pexels-photo-116675.jpeg", "label": "Exterior" },
{ "url": "https://images.pexels.com/photos/3764984/pexels-photo-3764984.jpeg", "label": "Interior" }
]
}
}
Use media URLs as variables rather than rewriting element objects per vehicle. Keep the designed positions, dimensions, timing, transitions, and typography inside the template.
Iterate the photo gallery inside one video
iterate repeats a scene for every item in the photos array. iterateAs gives the current item a readable name.
{
"id": "gallery",
"iterate": "photos",
"iterateAs": "photo",
"duration": 2.4,
"transition": "fade",
"transitionDuration": 0.4,
"visuals": [
{
"type": "IMAGE",
"src": "{{photo.url}}",
"width": 1080,
"height": 1920,
"position": "center-center",
"resize": "cover",
"zoom": true,
"track": 0
},
{
"type": "TEXT",
"text": "{{photo.label}}",
"x": 70,
"y": 1600,
"anchor": "top-left",
"track": 2,
"style": {
"fontSize": "36px",
"fontWeight": 700,
"color": "#FFFFFF",
"backgroundColor": "#111827",
"borderRadius": "14px"
}
}
]
}
Cap the photo count in your application. A feed with 42 images should not silently become a two-minute social reel. Select the best views or use different templates for a short listing reel and a longer VDP tour.
Model optional price states with a condition
Do not render an empty price box or a literal null. Calculate a boolean in the inventory adapter and let the template prune the price element.
{
"type": "TEXT",
"condition": "{{showPrice}}",
"text": "{{price}}",
"x": 70,
"y": 1380,
"anchor": "top-left",
"style": {
"fontSize": "76px",
"fontWeight": 900,
"color": "#FDE68A"
}
}
Use the same pattern for an optional warranty badge, certified-pre-owned line, trade-in CTA, or disclaimer. condition accepts a boolean state; calculate more complex eligibility before submission.
Keep vehicle media honest and visually consistent
Automated listing videos fail quickly when the media feed is weak.
Validate:
- The hero clip or photo shows the same vehicle as the listing.
- Watermarks and dealer overlays are approved.
- Aspect ratios have safe crops for the target format.
- Interior photos are not stretched or blurred.
- The gallery order does not repeat nearly identical angles.
- File URLs are public, stable, and large enough for the rendered slot.
- The driving clip's audio is muted unless it is intentionally part of the creative.
For a vertical social template, test landscape dealer photography with cover and explicit crop regions. For a VDP output, a landscape template may preserve more of the source. One template does not need to serve every channel.
Preview edge cases in the Zvid Editor
The editor is the best place to inspect visual states before inventory volume arrives.
Preview:
- A long make/model/trim combination
- Price shown and hidden
- Two photos and the maximum approved photo count
- A very bright exterior shot and a dark cabin shot
- Long dealer name and CTA
- The final frame before the dealer end card exits
The Variables panel resolves placeholders on the stage. The Scenes view previews the iterated gallery with the first item and exposes condition states. After approval, save the project as a template and keep its ID/version in the integration.
Render one listing through the API
curl -X POST https://api.zvid.io/api/render/api-key \
-H "x-api-key: $ZVID_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"template": "tpl_xxxxxxxxxxxxxxxxxxxx",
"variables": {
"year": "2024",
"vehicle": "Example Motors Apex GT",
"trim": "Touring AWD",
"mileage": "12,480 mi",
"price": "$38,900",
"showPrice": true,
"dealerName": "Northline Auto",
"phone": "+1 555 014 8820",
"cta": "Schedule a test drive",
"drivingVideoUrl": "https://cdn.example.com/inventory/CPO-1842/drive.mp4",
"photos": [
{ "url": "https://cdn.example.com/inventory/CPO-1842/front.webp", "label": "Exterior" },
{ "url": "https://cdn.example.com/inventory/CPO-1842/interior.webp", "label": "Interior" }
]
},
"overrides": { "name": "listing-CPO-1842" },
"webhookUrl": "https://example.com/hooks/zvid/inventory"
}'
Store the stock ID beside the returned job ID. A completion event should update the listing's render state, not automatically publish the video.
Design for the dealership outcome, not only the render
Automated car listing videos should help a shopper understand a vehicle before contacting the dealership. That makes the source inventory and destination more important than novelty. A useful vehicle video identifies the exact unit, presents a coherent photo order, highlights verified specs, and gives the sales team a clear next action.
The workflow can support several formats. A VDP video on the dealership website may be a concise photo walkaround with price and mileage. Social clips may use a faster opening and vertical layout. An in-house sales follow-up may prioritize the specific features a shopper asked about. All three can reuse the same approved car record without pretending that a slideshow is a filmed walkaround video.
Automation should also improve operations. When staff upload inventory photos, the system can validate resolution, remove duplicate angles, and flag missing hero media before it tries to generate a render. That is more useful than asking AI to invent features or enhance the vehicle beyond the listing facts. The goal is to transform dealership inventory into reliable automotive video assets while keeping every claim traceable.
A conversion-focused listing-video checklist
Before a car dealership automates publishing, test whether the video builds trust. Confirm that the first frame identifies the vehicle, the photo sequence resembles a logical walkaround, the voiceover or captions match the record, and the CTA leads to the correct dealership website or sales team. A 360 spin, when available, is a different source asset from a slideshow and should be labeled honestly.
Track the user experience after release: video starts, completion, VDP engagement, lead conversion, and any complaints about stale pricing. Automated solutions are useful only when the inventory and media stay synchronized. That feedback should improve the template and selection rules, not encourage AI to embellish the listing.
Support multiple dealerships without mixing inventory
For multiple dealerships, partition source records, templates, media, approvals, and destinations by tenant. A shared automation service can produce listings at scale, but every job needs the dealership ID, inventory snapshot, template version, and destination account. That prevents one location’s pricing, CTA, or branding from entering another location’s video.
The same ledger connects video production to inventory management and the automotive sales process. It can analyze completion, social media marketing engagement, and inquiry conversion by template without changing vehicle facts. An AI agent may draft a script or surface key features, while dealership staff approve the automated video. This is more reliable than a one-click promise that bypasses capture quality, compliance, and optimization.
Feed-led automation vs one-click capture
Car dealerships may start from an inventory feed or an on-site capture workflow. In a capture-first product, staff scan the VIN, capture video or photos in the showroom, and send vehicle information to video software. In a feed-led system, a third-party inventory source and media library provide the approved record. Both can automate production; neither should imply that one click removes fact and media review.
For the automotive industry, the valuable connection is the pipeline into dealership sales. The completed asset can update the VDP, CRM, SMS follow-up, or a page for potential buyers. AI-powered or AI-driven selection may simplify prioritization, but a seamless workflow still records source, reviewer, and destination. Walkaround videos captured by staff and template-rendered listing videos should remain clearly labeled because they create different shopper expectations.
Watch a real Zvid car-listing template
The demo below is adapted from Zvid's published Car Listing Reel template. It includes a driving hook, a photo gallery generated from an array, a ruled spec scene, and a dealer end card with optional content.
<video controls playsinline preload="metadata" poster="https://cdn.zvid.io/images/1/blog-10-demo_thumbnail-1784280520395.jpg" aria-label="Zvid-rendered auto-listing-reel demonstration for Automated Car Listing Videos" style="width:100%;height:auto;"> <source src="https://cdn.zvid.io/videos/1/blog-10-demo-1784280519197.mp4" type="video/mp4"> Your browser does not support embedded video. </video>
A real Zvid render adapted from the published auto-listing-reel example for this workflow.
This is the kind of real template a dealership integration should map into: media and facts change, while the designed scene system remains reviewed and stable.
Review before scaling to the full inventory
For one listing, inspect:
- Opening identification: correct year, make, model, and media
- Every gallery crop
- Price and optional states
- Mileage and spec accuracy
- Dealer phone and CTA
- Total duration after gallery iteration
- Transitions and final frame
- Mobile readability
Only after those checks should the integration move to the native bulk workflow. The live Bulk Video Generation API guide covers batches, item errors, webhooks, and reconciliation. For general product creative, see Automated Product Videos.
Common mistakes
- Building a new timeline object per vehicle instead of using template variables
- Passing raw feed values directly into public creative
- Iterating every feed photo without a gallery policy
- Showing a blank or stale price
- Using the same crop for VDP, landscape, and vertical outputs
- Letting a completed render publish without inventory or creative review
- Losing the stock ID after the render request
- Updating the template without recording a new version
FAQs
Can Zvid create a gallery scene from a vehicle photo array?
Yes. A template scene can use iterate so each photo object creates one scene with its own URL and label.
How should a listing with no public price be handled?
Calculate a showPrice boolean in the inventory adapter and use condition to remove the price element or scene. Do not render an empty placeholder.
Do automated listing videos replace custom dealership creative?
No. They are strongest for repeatable inventory formats. Hero campaigns, dealership brand films, and unusual vehicles may still need bespoke production.
Build one difficult listing first: long title, mixed photo orientations, optional price off, and the largest approved gallery. If that output works, the template is ready for an operations test.