Import Engine Extension Points

This page covers the import engine at the integration level only. Internal class names, hook names, payload shapes and orchestration details are implementation details and are not published here.

What the import engine does

The plugin's import engine pulls vehicle listings from the configured upstream marketplace and synchronises them into WordPress on a schedule controlled from the admin UI.

Integration surfaces

Supported configuration is exposed entirely through the plugin's admin UI:

• Connection credentials and seller selection.
• Import scope and frequency.
• Image-processing options.
• Diagnostic export for support.

Internal hook names, queue mechanics, retry strategy, locking primitives and data-mapping rules are not part of the public integration contract and may change between releases. If you need to react to imported data from external code, do so through standard WordPress mechanisms that observe the vehicle content type rather than by hooking into internal pipeline events.

Supported public integration surfaces

When integrating with the plugin, prefer these stable surfaces:

• The plugin admin settings UI.
• The documented shortcodes.
• Theme-level template overrides as described in Template System And Overrides.
• The general Developer Overview for orientation.

Internal class names, option keys, database tables, REST and AJAX endpoints, cron hook names, capability and nonce identifiers, and release / update infrastructure are treated as implementation details. They may change between releases without notice and are not part of the public integration contract.

Stability and change policy

Anything not listed as a supported public surface above is considered an internal implementation detail. Internal APIs, storage layout and security implementation may change between releases. Do not depend on them from third-party code, themes or external systems. Direct database writes are not supported.

Public documentation notice. This page provides a high-level integration overview only. Internal implementation details, private APIs, storage internals and security-sensitive release infrastructure are maintained separately and are not part of the public documentation. Supported integration surfaces are the documented shortcodes, template overrides, settings UI and any extension points explicitly published in this section.