Technical Readiness

System requirements for running ADP Car Market Hub on WordPress

Review the WordPress, hosting, PHP, database, cron, SSL and API access requirements needed to run ADP Car Market Hub reliably in a production environment. Confirm the server can handle vehicle imports and image processing.

Open Requirements Docs View Pre Installation Checklist

Technical readiness at a glance

Use this overview to confirm that the WordPress installation, hosting environment and external API access are ready before enabling live vehicle imports.

WordPress environment

The plugin requires a stable WordPress installation with suitable permissions, permalink handling and admin access.

View related docs

PHP and database

The server must support the required PHP version, database storage and processing capacity for imported vehicle data.

View related docs

Scheduled processing

Cron processing is required for recurring imports, background tasks, cleanup routines and reliable automation.

View related docs

External API access

The server must be able to reach the configured API endpoints through HTTPS without firewall or SSL issues.

View related docs

Production readiness

A staging test, backup strategy and pre installation checklist should be completed before go live.

View related docs

System readiness matrix

The requirements below define the technical baseline for a reliable production setup.

Area Requirement Why it matters Documentation
WordPress Supported WordPress version and standard WordPress environment Required for plugin activation, admin screens and frontend rendering WordPress Requirements
PHP Supported PHP version and required extensions Required for API communication, imports and background processing PHP and Database Requirements
Database MySQL or MariaDB compatible database with sufficient storage Required for vehicle data, logs, leads, analytics and settings PHP and Database Requirements
Cron Reliable scheduled processing Required for recurring imports, cleanup and background tasks Cron and Background Processing
SSL Valid HTTPS environment Required for secure admin, API communication and frontend trust API, Network and SSL Requirements
Outbound network Server can call external API endpoints Required for AutoScout24 API access and other external integrations API, Network and SSL Requirements
Storage Sufficient disk space for vehicle images, generated files and logs Required for image import, PDF output and operational stability Hosting Requirements
Email Reliable WordPress mail delivery Required for enquiries, search alerts and operational notifications Technical System Requirements

Hosting and server environment

A stable hosting environment is important because vehicle imports, image processing and API communication create recurring server workload.

Recommended environment

  • Managed WordPress hosting with reliable cron support
  • Dedicated server or VPS for larger inventories
  • Sufficient memory limit
  • Stable PHP worker capacity
  • HTTPS and current TLS support
  • Server-side cron where possible

Operational resources

  • CPU capacity for imports
  • Memory for image handling
  • Database capacity for vehicle data and logs
  • Disk storage for images and generated files
  • Backup and restore process
  • Monitoring for recurring import jobs
Open Hosting Requirements

WordPress, PHP and database requirements

The plugin relies on a standard WordPress environment, supported PHP configuration and a database that can handle recurring vehicle imports.

WordPress

Admin screens, custom post types, taxonomies, permalinks and frontend rendering depend on a healthy WordPress installation.

WordPress Requirements

PHP

API requests, import processing, image handling and PDF related workflows require the correct PHP configuration.

PHP and Database Requirements

Network, SSL and API access

The server must be able to communicate securely with configured API services. SSL, firewall and outbound connection settings should be checked before go live.

Valid HTTPS setup
Outbound HTTPS requests allowed
API base URL reachable from the server
No firewall blocking API calls
DNS resolution works reliably
SSL certificate chain is valid
Connection test completed in plugin admin
Open API, Network and SSL Requirements Open API Credentials Setup

Cron and background processing

Recurring imports and background tasks should not depend on unreliable visitor triggered execution in production environments.

Standard

WordPress Cron

WordPress cron may be sufficient for small demo environments, but production sites should be reviewed carefully.

Recommended for production

Server Cron

Server-side cron is recommended for reliable scheduled imports, cleanup processes and recurring background tasks.

Open Cron and Background Processing Open Server Cron Setup

Storage, media and import workload

Vehicle imports can include structured data, images, logs and generated files. The hosting environment should be sized for the expected inventory volume.

Images and media

Image imports and media processing require sufficient disk storage and PHP resources.

Hosting Requirements

Generated output

PDF datasheets, logs and frontend assets should be considered in storage and maintenance planning.

Technical System Requirements

Frontend and theme compatibility

The plugin output should be tested with the active WordPress theme, permalink structure and frontend modules before the site goes live.

Archive pagesVehicle detail pagesShortcodesComparison viewFavoritesSearch alertsLocation blocksOpening hoursTemplate overridesPage builder compatibility
Open Frontend Guide Theme Integration Template Override Guide

Pre installation checklist

Before installing the plugin on a production website, review the following checks with the hosting provider or technical administrator.

WordPress version checked
PHP version checked
Database compatibility checked
HTTPS active
Outbound API access possible
API credentials available
Cron strategy defined
Backup available
Staging test completed
Permalinks reviewed
Email delivery tested
Storage capacity reviewed
Theme compatibility checked
Admin permissions confirmed
Open Pre Installation Checklist

Non recommended environments

Some environments can work for simple demonstrations but are not recommended for reliable production imports.

Very limited shared hosting

May not provide enough resources for recurring imports and media handling.

Unreliable WordPress cron only

Can delay imports and background jobs when the website has low or irregular traffic.

Blocked outbound API requests

Prevents external API communication and connection testing.

No HTTPS configuration

Creates security and trust issues for admin and frontend usage.

No backup process

Increases risk during imports, updates and go live migration.

No staging environment

Makes integration testing and template validation harder.

Requirements documentation

Open the relevant requirements documents directly in the public documentation repository.

System Requirements section

Documentation links follow the active website language. English is the source language. Other language folders use localized folder and file names.

Continue exploring

Open the full plugin documentation or jump directly to the integration guide.

Open Documentation Open Integration Guide