SOARR Inventory SPA
Developer Integration Guide

One inventory source. Your dealership's website.

The SOARR Inventory SPA is a configurable inventory presentation layer for dealership websites. Available units, details and photos remain managed through SOARR while the website presents inventory in a style suited to your dealership and buyers.

This guide describes the recommended integration process. The exact production script, account configuration, approved inventory endpoint and any authorization requirements are supplied by SOARR during implementation.

Choose a presentation that fits the dealership.

The interactive demonstration shows the layout concepts. Production behavior, data and modules may vary with the dealer's enabled SOARR features.

Before you begin

• Identify the dealership's SOARR account and the approved website host/domain.
• Request the current integration package and configuration instructions from SOARR.
• Confirm which unit types, locations and inventory statuses should appear publicly.
• Choose the page structure and whether inventory listings require crawlable detail URLs.
• Agree on who owns the site's navigation, analytics, conversion tracking and design customization.

Recommended installation workflow

1. Provision: Obtain the dealership-specific integration details from SOARR. Do not reuse the live demo's dealer account.
2. Place: Add the approved inventory integration in a dedicated website section or template.
3. Configure: Set the supported layout, visible fields, inventory scope and lead actions.
4. Style: Match the dealership's typography, colors, spacing and mobile navigation.
5. Validate: Test listing counts, filters, photos, detail views, inquiry paths and crawlability.

For an implementation-ready code example, request the current SOARR-provided snippet for your dealer configuration. A generic snippet here could imply unsupported endpoints or options.

WordPress and other CMS platforms

A WordPress site can reserve a full-width content area for the inventory experience and load the approved SOARR integration using the supported code-insertion approach. The installation method depends on the dealer's theme, caching, content security policy and the approved integration package.

• Keep the website header/footer outside the inventory component.
• Use a container with enough width for filters, cards and mobile controls.
• Load scripts only on the appropriate inventory pages when supported.
• Validate interaction with optimization, caching and consent plugins.

SEO: make inventory discoverable

A fast interactive shopping interface is useful for buyers, but a client-rendered inventory screen alone does not guarantee discoverable detail pages.

• Provide stable, indexable unit detail URLs where supported.
• Ensure important vehicle details and meaningful page metadata can be rendered or exposed in an indexable form.
• Maintain canonical URLs and avoid unintentional duplicate inventory paths.
• Include appropriate structured data only when the content and page type support it.
• Generate and maintain an inventory XML sitemap when the site's architecture supports crawlable unit URLs.
• Check actual rendered output and Google Search Console indexing rather than assuming JavaScript pages are indexed.

Validation & troubleshooting

Acceptance checks

• Desktop and mobile layouts work without filter-panel overlap or horizontal scrolling.
• Search, filters and sorting behave consistently.
• Listing photos, details and inquiry links resolve correctly.
• Newly published and archived inventory updates behave as expected.
• Critical detail URLs are crawlable where an SEO implementation is required.
• No account keys, private endpoints or unrelated dealer names appear in publicly served source.

Common trouble spots

If inventory is blank, first confirm the provisioned account and host configuration. If filters behave unexpectedly, check for script duplication, caching and incompatible theme JavaScript. If indexed pages are missing, inspect the server-rendered page and sitemap strategy.