How to Read a Mazda Digital Service Record

Read a Mazda Digital Service Record by identifying the vehicle first, then separating visit dates, recorded mileage and named maintenance tasks. The document can help you understand what was entered for a visit. It should not be expanded into proof that every scheduled task was completed, that no other work occurred or that the car is mechanically sound today.

This guide explains an existing, anonymised Mazda CX-5 example published by VinHistory. The original document is in Polish. The explanations below are in English, but the source has not been translated into a new-looking manufacturer report. Layout, language, access and the fields supplied can differ between vehicles and markets.

Identify the vehicle and the document before reading the visits

A maintenance record is useful only if it concerns the correct vehicle. For an actual purchase, compare the full VIN and available identifying details with the vehicle and its registration paperwork. Do not treat a document for another CX-5, a similar engine or the same registration year as evidence for the car you are considering.

Our public example has identifying references removed. That protects the source vehicle, but it also means you cannot use the public sample to identify your own Mazda. Use it to understand the reading method. The vehicle-details section describes a CX-5 and identifies Poland as the original market. Those details provide context for the language and units appearing in this particular example.

The VIN comparison guide explains the first identity checks. If a seller supplies only a small crop, request the relevant full page before interpreting a date or a line of work. A heading outside the crop may change what that line means.

Enlarge authentic sample extract ↗

Keep the warranty start separate from the service timeline

The example’s vehicle-details section includes a warranty start of 22 November 2018. That is an administrative starting point shown in this source. It is not a service visit, and it should not be counted as evidence that oil, filters or another maintenance item were changed on that date.

Keep manufacturing, first registration, warranty start, document-printing and workshop-event dates in separate fields when they are present. A later printout can describe several earlier visits. Reading the print date as the most recent service would therefore create a false maintenance timeline.

A historic warranty-related field also does not decide present eligibility for any manufacturer programme. If current cover matters to your purchase, ask Mazda about the exact vehicle and applicable terms. This guide interprets the existing record; it does not determine a warranty claim.

Read the visit date and its original mileage unit together

The visit-table excerpt shows readings of 20,511 km in 2019, 33,964 km in 2020 and 50,168 km in 2021. They form an increasing sequence of recorded observations. Keep each number attached to the corresponding year and original document rather than quoting only the largest reading.

The unit matters when comparing a car subsequently advertised in Britain. A current odometer or MOT observation may be in miles while this example is in kilometres. Convert into a separate comparison column and retain the original value. For example, 50,168 km is approximately 31,173 miles using 1 mile = 1.609344 kilometres. The rounded conversion is an aid to comparison, not another recorded odometer event.

Source observation	How to retain it	What not to infer
2019: 20,511 km	Year, original reading and unit	Exact use between visits
2020: 33,964 km	A separate dated observation	That every scheduled task was completed
2021: 50,168 km	The source reading, with any conversion separately	Guaranteed lifetime mileage

A sensible sequence is useful supporting evidence. It is not independent proof that each number was entered correctly or that there were no unrecorded periods. Compare it with the seller’s invoices, any relevant inspection records and the current display.

Read the named tasks instead of counting every row as a full service

The 2021 row in the published example includes a cabin-filter task and a body inspection. Those descriptions help identify what is recorded. A body inspection is not automatically an engine-oil change, and a cabin-filter item does not establish that every filter or fluid on the vehicle was replaced.

Make a task list for the claims that matter to the purchase. If the advert mentions a particular major job, look for evidence naming that job. A general servicing label, a visit date or a large payment amount may not answer the question. Ask for an itemised invoice where the summary does not provide enough detail.

Also distinguish completed work from a recommendation. A workshop can inspect an item, advise future replacement, investigate a symptom or carry out a repair. Those are different actions. Read the verb and any outcome rather than treating the appearance of a component name as confirmation that it was renewed.

Enlarge authentic sample extract ↗

Use the original Polish example with its English explanation

The two anonymised excerpts accompanying this guide show the visit table and the vehicle-details area. They are authentic extracts from the existing example, not generated teaching documents. You can also open the anonymised two-page Mazda sample PDF to read the source in context.

Keep an unfamiliar word beside any translation used in your notes. An English explanation helps you understand the function of a field, but it should not replace the original text. If an important maintenance claim depends on a term you cannot confidently interpret, request clarification from the source rather than choosing the most reassuring translation.

Do not assume the same column order, wording or coverage will appear in a report for another country or a different Mazda. This is a method for reading one example. It is not a universal template of all records available for every VIN.

Compare the DSR summary with the invoice behind the visit

A digital summary and a workshop invoice may describe the same event at different levels of detail. Link them using the vehicle, event date, mileage and workshop reference where available. The invoice can help explain parts, materials and individual tasks that a short record does not spell out.

Use our invoice evidence checklist when evaluating those supporting documents. Keep copies together so that one visit is not counted multiple times. Record any explanation from the workshop beside the original evidence; do not overwrite a source reading to make two documents agree.

As a practical fictional exercise, imagine an invoice naming an oil change and a cabin filter, while a summary names only a general maintenance visit. The shorter summary does not contradict the detailed invoice merely because it has fewer words. The useful question is whether the identifiers and event information support linking the two documents.

Follow up a missing or unclear entry through the right source

First define the missing item. Is the visit absent, is an invoice missing, or is the app showing a different type of information? Those situations need different requests. Mazda’s service and maintenance information describes its Digital Service Record, while its MyMazda guidance provides context for the owner-facing view.

Ask the owner to contact the workshop with the relevant vehicle details, approximate date and any invoice reference. Ask whether a record was entered and what document can be supplied. Do not assume a third party can amend manufacturer records or that access to an app will reveal every historical invoice.

For the document-request process, use our missing-history recovery guide. If the issue is an empty or unexpected app screen, the manufacturer-app checklist helps separate display scope from evidence of completed work.

Turn the record into focused purchase questions

Before the viewing, prepare a short list: which vehicle does the document identify, which visits and tasks are supported, which periods have independent corroboration, and which specific claims still need an invoice? That is more useful than a conclusion based only on the number of rows.

If additional manufacturer information could address a gap, our Mazda service history report explains the available VIN-based service and its limits. Keep its role separate from an inspection of the actual car. A well-read history helps frame questions; it does not diagnose present condition or guarantee that an archive is complete.

Sources and further reading

• Mazda UK: service and maintenance FAQ
• Mazda UK: MyMazda FAQ
• Mazda UK: official contact routes, including DSR enquiries
• VinHistory: existing anonymised Mazda source example

By VinHistory. Sources reviewed on 30 October 2026. The document extracts are genuine anonymised examples; the explicitly described comparison exercise is fictional. Record availability and language vary.