Skip to main content
JATO

Importing Vehicle Data from JATO

Importing Vehicle Data from JATO

Overview

Catch-e can now import vehicle data from JATO, giving administrators an additional vehicle data source for quoting alongside the existing Glass's Guide and RedBook integrations.

Prerequisites

  • An active JATO subscription, with credentials configured against your Catch-e environment by Catch-e.

  • JATO must be set as the vehicle data source for the organisation (or for an individual quote), using the same control that selects Glass's or RedBook today.

  • Three timeout controls govern the import, one each for the discover, fetch and import stages. Defaults are provided out of the box (10 minutes, 20 minutes and 30 minutes respectively) and can be adjusted if needed.

  • Unlike Glass's, JATO has no file to configure. There is no filename, import type or warning-days setting, because JATO's data is fetched directly from the JATO web service rather than from an uploaded file.

  • Fuel figures, kerb weight and standard equipment are only populated when your subscription uses JATO's full leasing data set ("JaaS API Default").

How It Works

  1. A JATO import can be started in either of two ways: automatically on a schedule via the Scheduler, or manually from Fleet > Import Data > JATO Data, the same way a Glass's import is triggered today.

  2. Once started, JATO begins discovering the latest available vehicle data. Catch-e waits for the amount of time JATO itself suggests before checking in, rather than a fixed interval, so the first check lines up with when JATO expects to be ready.

  3. Once discovery finishes, Catch-e automatically moves on to fetch the discovered data from JATO.

  4. Once fetching finishes, Catch-e automatically imports the data.

  5. Each of the three stages (discover, fetch and import) runs under its own timeout, so a delay in one stage does not affect the others.

  6. When the import completes, a summary email is sent showing how many vehicle instances were found, fetched, inserted, updated, deactivated and failed, the number of warnings raised, and the job's start and completion times.

Expected Behaviour

Successful Import

  • Whether triggered via the Scheduler or via Fleet > Import Data > JATO Data, the import proceeds automatically through the discover, fetch and import stages to completion.

  • A summary email is sent with the import counts and timestamps described above.

  • Newly imported or updated vehicle data becomes available wherever JATO is set as the vehicle data source.

Import Completes With Warnings

  • An import that raises warnings (for example, a variant description that had to be shortened, or a retail price below base price plus GST) still completes.

  • The summary email lists each type of warning once, with how many times it occurred and which records were affected.

JATO Reports a Failure

  • If JATO reports a failure at the discover stage, the import stops immediately and fetch and import are never attempted.

  • If JATO reports a failure at the fetch stage, the import stops before the import stage begins.

  • If JATO reports a failure at the import stage, the error is recorded and surfaced along with JATO's own error detail.

  • In every case, the recorded error names the stage that failed, so it is clear where the import stopped.

A Stage Exceeds Its Timeout

  • If the discover, fetch or import stage runs longer than its configured timeout, the import stops with an error identifying that specific stage. The three timeouts are independent of one another.

Quoting With JATO Data

  • Once JATO is set as the vehicle data source for an organisation or an individual quote, a quote can be generated using JATO-sourced vehicle data.

Existing Vehicle Data Sources Unaffected

  • Glass's and RedBook imports, and quoting against Glass's or RedBook data, continue to work exactly as before. JATO is purely an additional option.

Related Articles