JATO Vehicle Data Import
The import process retrieves vehicle information from JATO and synchronises it with the Catch-e vehicle database.
Process Flow

Vehicle Information Imported
The integration imports a wide range of vehicle information, including:
Vehicle Details
Make
Model
Variant
Vehicle type
Body style
Seating capacity
Number of doors
Build year
Model year
Availability dates
Engine and Drivetrain
Fuel type
Power output
Torque
Transmission
Drive type
Powertrain classification (ICE, Hybrid, PHEV, EV)
Pricing
Retail price
Base price
GST component
Electric Vehicle Information
Where available, additional EV information is imported, including:
Battery capacity
Driving range
Charging capability
Battery warranty information
Equipment and Options
The integration imports:
Standard equipment
Optional equipment
Paint colours and paint options
Vehicle Creation and Updates
Each vehicle supplied by JATO contains a unique identifier which is used to determine whether the vehicle already exists in Catch-e.
New Vehicles
If a vehicle does not already exist in Catch-e:
A new vehicle variant record is created.
Associated options and specifications are imported.
The vehicle becomes available for quoting and ordering.
Existing Vehicles
If a vehicle already exists:
Changes to specifications, pricing, or equipment are updated.
Existing references remain intact.
Vehicle information remains synchronised with JATO.
Vehicle Availability Management
JATO identifies whether a vehicle is currently available or has become outgoing. The integration uses this information to maintain vehicle status in Catch-e.
If a vehicle is no longer supplied by JATO, it is automatically marked as inactive rather than being deleted. This preserves historical quote and contract data.
Quote Copy Behaviour
When a quote references a vehicle that has since become inactive, the system supports the use of successor vehicle records.
Where a replacement vehicle has been identified:
The successor vehicle is automatically used when the quote is copied.
Where no replacement exists:
The user must be made aware that the selected vehicle is no longer active and choose an alternative vehicle.
Build Year Rules
JATO does not provide a separate build year value.
For all imported vehicles:
Build Year is derived directly from Model Year.
Model Year and Build Year will therefore always be identical for JATO imported vehicles.
Model Month Rules
Model Month remains a Catch-e specific field.
Where JATO does not provide a reliable value:
Model Month is stored as 0.
No assumptions or calculations are applied to derive a month value.
Powertrain Classification
Vehicles are automatically categorised into Catch-e powertrain types.
Any unrecognised powertrain classifications are logged for review but do not stop the import process.
Data Not Provided by JATO
Some vehicle information currently maintained within Catch-e is not available from JATO and therefore cannot be automatically populated. Examples include:
Previous variant relationships
Next variant relationships
Service profiles
Residual value data
Certain legacy vehicle classifications
Where applicable:
Existing values are retained.
Default values may be applied.
Catch-e continues to manage these values independently.
Scheduling and Monitoring
Currently under development
The import runs automatically through the Catch-e scheduler framework.
The process records:
Import start and finish times
Numbers of vehicles created and updated
API errors
Processing warnings
Last successful import date
This information supports operational monitoring and troubleshooting of the integration.
Benefits
The JATO Vehicle Data Integration delivers:
Improved vehicle data quality.
Reduced manual data maintenance.
Faster availability of new vehicle releases.
Better support for EV and hybrid vehicle information.
Consistent vehicle pricing and specification data across the platform.
Automated lifecycle management of active and inactive vehicle variants.
This ensures Catch-e maintains an accurate and scalable vehicle catalogue while reducing the administrative effort required to manage vehicle master data.