Import Pipeline

From AutoScout24 source data to native WordPress vehicles

A controlled pipeline receives, validates, maps and publishes each listing as a native WordPress vehicle record, with full operator visibility at every step.

Back to Features overview View Image Queue

From source to native vehicle

How inventory moves through the Import Pipeline

Source listings enter on the left, the pipeline processes them inside WordPress, and each record exits as a native WordPress vehicle page that the operator fully controls.

Visual representation. Field names follow the AutoScout24 source payload and the imported as24ci_car post type.

Pipeline at a glance

Six structured stages, end to end

Every listing follows the same predictable sequence so results are reproducible and operators always know which stage a record is in.

Inside each stage

What happens at every stage

Each stage has a clear job, a controlled outcome and visible signals so the team understands what the pipeline is doing right now.

01

Receive

Authenticated requests page through every configured seller and collect activated, live listings without blocking the editor.

02

Validate

Records without an id or with a non-active status are skipped early so only meaningful data continues into the pipeline.

03

Detect change

lastModifiedDate is compared first; when missing, a content hash is used. Unchanged listings are skipped and only the sync timestamp is refreshed.

04

Map

Source fields are normalised into the typed vehicle schema, with backwards-compatible postmeta kept in place for templates and filters.

05

Persist

The vehicle is inserted or updated as a native WordPress post and the AI Lock guards editorial copy from being overwritten.

06

Publish

The configured post status is applied and the as24ci_vehicle_imported action fires so integrations can react to the change.

Media handoff

Images stay out of the critical path

During mapping the pipeline extracts image URLs and hands them off to the background image queue, so vehicle records publish immediately and media is processed independently.

Pipeline Map · extract image URLs
Image Queue Pending → Imported
3 imported 21 pending

Operator visibility

Every run is transparent and reviewable

Each import run records inserted, updated, skipped and error counters in the WordPress admin so the team can confirm the pipeline ran exactly as expected.

Native output

Vehicles end up as native WordPress content

The pipeline does not produce a black-box feed. Each imported vehicle is a real WordPress post the operator can edit, restyle, translate and link from anywhere on the site.

Pipeline capabilities

The building blocks that make the import pipeline reliable, transparent and operator-friendly.

Predictable processing

Every listing runs through the same sequence of validation, mapping and persistence so results are reproducible across cron, manual and REST runs.

Change detection

lastModifiedDate is checked first; when missing, a content hash is used. Unchanged records are skipped and updates only touch what really changed.

Editorial AI Lock

When AI Lock is enabled on a vehicle, the importer keeps the existing post content and excerpt so curated copy survives every re-import.

Stable slugs

Slugs are anchored to the listing id so vehicle URLs remain stable across re-imports, protecting SEO and existing inbound links.

Background media

Image URLs are extracted during mapping and handed to the image queue, so the pipeline stays fast and vehicle records publish without waiting for downloads.

Run-level visibility

Every run records inserted, updated, skipped, errors and api_active counters in the admin so the team can verify the catalogue size and recent activity.

Continue exploring

Where to go next in the showcase

The pipeline connects API ingestion, background media, scheduling and the vehicle data model. Continue with the related capabilities that surround it.

01 Source AutoScout24 API Import The authenticated API connection that supplies raw listings into the import pipeline. 02 Media Image Queue Background processing for vehicle images handed off by the pipeline, with retries and rate control. 03 Schedule Automation & Scheduling Scheduled jobs that trigger the pipeline on a recurring basis without manual intervention. 04 Data model Vehicle Data Structure The schema that the pipeline maps incoming data into before publishing native WordPress vehicles.

Continue exploring ADP Car Market Hub

Return to the Features overview or explore a related capability to see how the import pipeline supports the full platform.

Back to Features overview View Image Queue Contact us