Operational Workflows

Operational workflows for native WordPress vehicle inventory

ADP Car Market Hub helps dealer and agency teams monitor imports, publishing state, lead routes and inventory updates inside the dealer website workflow, so the operational picture stays clearer after launch.

More than running an import

What operational workflows really mean after launch

Operational workflows go beyond a working import. They connect inventory updates, publishing state, lead routes and frontend availability into a picture that teams can monitor, explain and hand over.

  • Inventory connection. The AutoScout24 inventory is imported into native WordPress vehicle records.
  • Update visibility. Vehicle updates are visible inside the WordPress admin instead of disappearing into a feed.
  • Publishing state. Each vehicle has a clear status: imported, updated, published or under review.
  • Lead routes. Contact, favorites and comparison stay on the dealer website where teams can see them.
  • Handover state. The same operational view can be shared between agency, dealer and support teams.

Day-to-day sequence

The daily inventory workflow at a glance

Inventory does not stand still. ADP Car Market Hub structures the daily flow from a vehicle update, added in the backend or via the AutoScout24 API, into a visible WordPress record, a frontend archive entry, a clear lead route and an operational review.

  1. Source AutoScout24 inventory update New, updated and removed vehicles arrive from the AutoScout24 inventory. Source data
  2. ADP Car Market Hub Import and sync The plugin imports the inventory and writes each vehicle into native WordPress. Plugin step
  3. WordPress WordPress vehicle record Each vehicle becomes a native WordPress entry with publishing state and history. Native record
  4. Frontend Archive and detail page output The vehicle becomes visible in the inventory archive and on its own native detail page. On site
  5. Customer action Lead route and customer action Visitors save, compare and contact — the lead route stays on the dealer site. Intent signal
  6. Operational loop Operational review Teams check what is live, updated and ready — and what still needs attention. Reviewed

Directional sequence — exact steps depend on each WordPress site setup, but every step lives inside the dealer website workflow.

Daily monitoring

What operational teams need to monitor

A clear set of operational signals helps dealer and agency teams understand what is happening with the vehicle inventory — without diving into raw logs or third-party dashboards.

InventoryLive

Published vehicles

How many vehicles are live on the dealer website right now — the operational baseline.

UpdatesTracked

Recently updated vehicles

Which vehicles have changed since the last operational check — useful for daily review.

ReviewReview

Missing or review-required data

Vehicles where media or attributes may need attention before they read well on the dealer site.

LeadsActive

Lead route coverage

Whether contact, favorites and comparison routes are reachable from the vehicle pages.

FrontendReachable

Archive and frontend availability

Whether the inventory archive and vehicle detail pages are reachable on the dealer domain.

ReportingShared

Reporting visibility

A shared operational view that agency, dealer and support teams can read together.

Signal · meaning · action

From operational signal to action

Each operational signal becomes easier to interpret when it is paired with a short meaning and a clear next step — so teams know what is informational, what needs review and what to do.

  • Vehicle updated New vehicle data is available in WordPress. Refresh the native page output and confirm visibility. Informational
  • Missing media A vehicle card may need review before it reads well. Check the asset queue and the related vehicle record. Review
  • Lead route inactive A customer action path may be incomplete. Review the contact flow and confirm the route is reachable. Review
  • Import delayed Inventory freshness may need attention. Check the AutoScout24 connection state and the schedule. Attention
  • Vehicle removed A vehicle is no longer part of the AutoScout24 inventory. Confirm the WordPress record state and the archive view. Informational
  • Frontend archive empty The inventory archive may not be returning results. Check filters, taxonomy and the archive template wiring. Review
Directional guidance — exact next steps depend on the dealer site setup.

Operational roles

How the workflow supports different teams

Different teams care about different parts of the inventory workflow. ADP Car Market Hub gives each role a clearer view of what is live, what is updated and what still needs attention.

Dealership

Dealer management

Monitors Inventory volume, publishing state and frontend availability.

Easier to Explain what is live on the dealer website and what is in review.

Sales

Sales team

Monitors Vehicle availability, lead routes and customer actions on the site.

Easier to See which vehicles are reachable for visitors and trust what they share.

Marketing

Marketing team

Monitors Recent updates, frontend archive readiness and reusable inventory blocks.

Easier to Plan campaigns around real, native vehicle pages on the dealer domain.

Agency

Agency or implementation partner

Monitors Import health, publishing state and the operational handover view.

Easier to Hand over a controlled WordPress vehicle inventory workflow to the dealer.

Technical

Technical administrator

Monitors AutoScout24 connection, scheduling, asset queue and update pipeline.

Easier to Diagnose what is happening inside the WordPress plugin instead of guessing.

Support

Support team

Monitors Review-required vehicles, lead route coverage and reported issues.

Easier to Reproduce, explain and resolve operational questions with a shared view.

Operational visibility

A single operational view of the inventory workflow

A shared operational visibility board makes it easier for dealer and agency teams to read where the inventory workflow stands today — and what is closer to ready, in review or still pending.

  • One place to read import, publishing and lead route state.
  • Aligned labels, values and status badges — no guessing.
  • Reusable across dealer, agency and support conversations.

Operational view

Inventory workflow readiness

  • Status summary Ready
  • Inventory update progress On track
  • Lead route coverage Active
  • Archive readiness Tracked
  • Handover visibility Review
  • Recent activity Logged
A controlled inventory workflow that teams can read together.

Why this matters

Why operational workflows matter after launch

Controlled operational workflows support clearer day-to-day ownership, less ambiguity around inventory state and a stronger handover between agency, dealer and support teams.

OwnershipOwned

Clearer day-to-day ownership

Each operational area has a visible status, so it is easier to know who looks at what.

ClarityClearer

Less ambiguity around inventory state

A shared view of imported, updated and published vehicles helps reduce manual ambiguity.

CommunicationExplainable

Better explanation for client teams

Agencies and implementation partners can explain what is live and what is in review with one view.

LeadsOn site

More controlled lead routes

Contact, favorites and comparison stay on the dealer site, where teams can monitor coverage.

ReusableRepeatable

Reusable operational model

The same operational pattern can be applied across dealerships, dealer groups and garages.

HandoverVisible

Stronger handover visibility

A shared operational view supports a smoother handover between agency, dealer and support.

Ready to see it

See the inventory workflow on a real dealer site

Open the inventory demo to see how native WordPress inventory moves from import to visible dealer website output — or jump into the full features overview for the complete capability map.