Year, make, and model are only the beginning. A maintainable fitment system has to manage the product relationship, qualifiers, imports, categories, publishing, and the shopper’s current vehicle.
Distinguish All Bodies, All Trims and All Engines from specific restrictions.
Keep qualifiers, application notes and product references with the mapping.
Actual Pro-A-Motors interface captures. Private identities and contact details are covered or outside the crop; screen data has not been replaced.
What improved
Make vehicle compatibility something staff can inspect.
The business problem
Compatibility data existed, but it was difficult to inspect and maintain at product scale. The workbench was created to make the mapping visible before it reaches search and the storefront.
What we changed
A dedicated workbench exposes make, model, year and other compatibility attributes for product-level maintenance.
What the team can do now
The catalog team can manage the mappings while shoppers get a cleaner path from “what fits?” to an available product.
Read the actual screen
The year range and scope are explicit.
The inspected mapping shows Cadillac Escalade, start year 1999 and end year 2000, with All Bodies, All Trims and All Engines enabled.
Make / model
Cadillac Escalade
Year range
1999–2000
Scope
All bodies / trims / engines
Mapping edits
None
What the screen shows
The editor exposes the selected years, scope switches, qualifiers, application notes, OEM and Partslink. It was closed without saving changes.
What the team does next
Review the mapping’s scope and any qualifiers before changing compatibility. These are existing catalog values, not a fitment recommendation for a vehicle.
What the next team receives
Catalog staff retain a mapping whose year coverage and restrictions can be inspected and maintained.
How the work moves
Follow the work from one decision to the next.
01
Build the compatibility record
Each product relationship can express make, model, year range, body, trim, engine, and qualifiers.
02
Import and review at scale
Bulk data and legacy mappings enter through controlled paths instead of bypassing the model.
03
Apply catalog safeguards
Publishing, categories, stock messaging, and year restrictions prevent misleading choices.
04
Keep the shopper’s vehicle in context
The selected vehicle follows search, categories, and product decisions until the shopper changes it.
Built, used, refined
How the workflow improved over time.
Constrain the vehicle-year choice
Added year restrictions to the website picker.
Preserve the selected year
Kept the vehicle year through the search flow.
Carry fitment context forward
Refined persistence of the shopper’s fitment selection.
About these dates
Dates identify recorded implementation changes, not claimed rollout dates or measured results. Reviewed revisions: f472edc, f38797a, 62f1f93.
Build notes and background
Ecommerce UXData integration
Make the exceptions part of the workflow.
A broad scope is a deliberate value
All Bodies, All Trims and All Engines are visible choices, not missing labels.
Qualifiers need their own field
Application notes and searchable compatibility restrictions serve different purposes.
One mapping must satisfy the selection
Year, make and model criteria are checked against the same fitment detail row by the catalog search extension.
Existing records are shown as captured. Private identities are covered or outside the crop. No business records were changed for this collection. Implementation history supports behavior beyond the visible screen; a still image is not an end-to-end test or a measured productivity result.
Substantially extended from an existing commercial automotive-fitment foundation and standard Odoo product and website-commerce features. Toro’s work is the maintenance workflow, safeguards, data handling, and storefront behavior described here.
