Documentation · Overview
Product Overview
This document introduces the ADP Car Market Hub WordPress plugin: what it does, who it is for, and how it fits into a typical dealer website.
When to use this document
Read this document when you are evaluating the plugin for the first time, when you need a short summary to share with a colleague or stakeholder, or when you want to confirm whether a particular use case is in scope before reading the detailed sections.
Overview
ADP Car Market Hub connects a WordPress site to the official AutoScout24 API and turns its vehicle inventory into native WordPress content. Imported listings are stored as a custom post type (as24ci_car), enriched with vehicle-attribute taxonomies, and exposed through the plugin's templates, shortcodes and admin tools.
The plugin is designed for car dealers and dealer groups that already have AutoScout24 API access. It does not scrape the public AutoScout24 website. All vehicle data is retrieved through the configured API endpoint with credentials supplied by your provider.
Headline capabilities:
- Import and synchronise vehicle listings, images, equipment and prices from the configured API.
- Schedule recurring imports through WP-Cron or an external system cron with a token-secured REST trigger.
- Manage vehicles in the WordPress admin and present them on the front-end through the bundled archive, single, compare and favorites templates.
- Capture leads from contact forms and Test Drive requests and route them to the configured recipient address.
- Maintain plugin-managed dealership sales contacts (CMH Team) shown on vehicle pages and used to route leads.
- Optional add-ons for AI-generated descriptions, Content Studio marketing text, Search Alerts (Smart Stock Alerts), Analytics, a Financing Calculator, a PDF datasheet, Locations, Market Insights and more.
Audience
- Dealer staff and editors — manage inventory, leads and front-end presentation through the WordPress admin.
- Site administrators — install, configure and operate the plugin, including credentials, cron and integrations.
- Developers and integrators — extend the plugin, build custom integrations or theme overrides.
Where this fits in the documentation
The English documentation is split into the following top-level sections:
- Getting Started — installation and first connection.
- System Requirements — hosting, PHP and network prerequisites.
- User Handbook — daily editorial workflows.
- Admin Reference — every admin screen explained.
- Technical Documentation — architecture, data model and internal behaviour.
- Integration Guide — credentials, server cron, themes and page builders.
- Frontend Guide — what visitors see and how it is composed.
- Operations and Maintenance — running the plugin in production.
- Privacy, Security and Compliance — data handling, consent and access control.
- Troubleshooting — problem-driven recipes.
- Release Notes — versioned changes.
- Appendices — quick references for shortcodes, settings, hooks and endpoints.
- Developer Documentation — extension points for custom code.
Out of scope
- Scraping HTML pages from AutoScout24 or any third party.
- Acting as a replacement for an AutoScout24 dealer contract or API access.
- Hosting the WordPress site itself; the plugin runs inside a customer-managed WordPress installation.
Operational notes
- The plugin uses the WordPress option table to store its configuration. Sensitive secrets are protected at rest: the AutoScout24 API client secret is stored using authenticated AES-256-GCM encryption (with the key derived from the WordPress salts), and the cron-import token is stored as a one-way HMAC-SHA256 hash. The plaintext cron token is only displayed in the admin for a short window after generation. Database backups should still be treated as sensitive, because they also contain leads, settings and other operational data.
- Optional features such as the AI Assistant, Webhooks, Search Alerts and the public REST API are disabled until an administrator turns them on.
- Localised admin labels and translation files are shipped with the plugin. The English documentation is the source language and may use cautious wording where behaviour depends on customer configuration. Verify any behaviour you intend to publish customer-facing against the current plugin version.