A dealer says the file has a problem — what now?

When a dealer requests a revision, the order returns to your queue as Revision requested, carrying their description of what went wrong. It is the same order — same credits, same thread, same history.

Work the revision

1. Read the dealer's problem description on the order page, and ask follow-up questions in the chat — error behaviour, logs, when it occurs.

2. Rework the file and deliver again on the same order. The redelivered file goes through the same check against the original as a first delivery (see delivering-a-file), so an amber note may appear before you deliver, and a flagged revision keeps a flagged for review badge in the order's file list afterwards. The status returns to Delivered, and the file reaches the dealer under the filename you gave it — a name with no extension gains ".bin".

   

   

There is no separate "revision fee" mechanic: revisions ride the original order until it is accepted or resolved another way.

When a fix isn't possible

Some cars cannot be made to work — hardware faults, unsupported ECU variants, a read that turns out corrupt. Then the honest exit is a refund or cancellation rather than an endless revision loop: refunds-and-cancellations covers which applies.

When you and the dealer disagree

If a thread is going nowhere, Escalate on the conversation opens a support ticket with the order attached. That request alone does not change the order's status. An order that actually reaches Escalated is held for platform review; see escalated-orders. Keep the car's evidence — logs, photos and the dealer's report — in the conversation for the support team.