Frequently asked questions
Clear answers before the workflow conversation.
Start here for the practical questions about publishing, dealer websites, commerce, locations, reporting, and working with systems already in place.
Publishing and endpoints
Where inventory can go
What counts as a Varius endpoint?
An endpoint is a configured destination that can receive structured inventory from Varius. That may be a dealer WordPress website, a supported listing channel, or a planned commerce feed. Each endpoint has its own account and data requirements.
Which publishing endpoints are supported?
Current supported paths include the dealer WordPress website endpoint, AgDealer, Kijiji, Fastline, Equipment Trader, AutoTrader Heavy Equipment, and IronSearch. Availability is confirmed during discovery because channel requirements can change.
Are Facebook and Google commerce feeds included?
Facebook Commerce Manager and Google Merchant Center are planned commerce integrations. They depend on the dealer account, feed eligibility, catalogue structure, and platform policy requirements.
Is MarketBook or Sandhills a supported endpoint?
MarketBook and other Sandhills properties should not be assumed to accept a Varius feed. We confirm every requested destination before including it in an implementation scope.
Website and inventory
How the connected website behaves
What does “dealer-owned inventory pages” mean?
Inventory pages live on the dealership website and carry the dealership brand, navigation, typography, colours, calls, forms, and tracking. Buyers are not pushed into an AgDealer, MarketBook, or other provider-branded search experience.
How quickly does website inventory update?
The Varius WordPress endpoint is designed for a connected, real-time inventory experience. Exact caching and search indexing behaviour is confirmed during implementation so updates remain fast without slowing the website.
What happens when a unit sells?
The listing status is updated from the Varius record. Website and supported endpoint behaviour can then follow the configured sold, removed, redirected, or archived rules for that dealership.
Can Varius work with our existing website provider?
Sometimes. Varius may fit first as an inventory or supported publishing layer, or as a staged path to a connected WordPress website. Discovery starts with the current provider, data access, forms, analytics, and endpoint commitments.
Locations, commerce, and reporting
How the broader dealership fits
How does location assignment work?
Multi-location support is a Varius inventory capability. A listing is assigned to the correct dealer location, then that store’s phone, text, address, and contact details can appear with the equipment on the website.
Can the website include WooCommerce?
Yes. The Commerce plan is designed for a unified WordPress and WooCommerce experience on the dealership domain, using the same brand system, type, colours, spacing, navigation, and interaction patterns as the main site and equipment inventory.
What does the Website Visibility Report show?
The report connects website health, search visibility, inventory engagement, buyer actions, sources, campaigns, and publishing health. It is designed to show which units and paths are creating attention and action, not only total pageviews.
Can our internal marketing team use Varius without giving up control?
Yes. The internal team keeps brand, campaign, audience, and content direction. Varius supplies the structured inventory, website, publishing, source tracking, and reporting infrastructure behind that work.
How is accessibility handled?
Responsive and accessibility foundations are part of the website system and launch QA. Specific AODA requirements, content responsibilities, third-party tools, and ongoing maintenance are confirmed in the website scope.
Still sorting out the fit?
Bring the current website, endpoints, and inventory workflow.
We will map what is already working, identify the duplicated handoffs, and explain what Varius can support without making promises around unavailable endpoints.