What if I enter the same VIN twice on a pack?
No second credit is used. A repeat VIN on the same pack matches the job that already exists, and the wallet tells you no second credit was spent.
Check the review date and linked sources for context. Live availability, prices and record coverage can vary by VIN, source, jurisdiction and time.
Nothing is double-charged. If you submit a VIN that is already assigned to that pack, the wallet answers: that VIN is already assigned to this pack — no second credit was used. It is enforced in the database, not just in the wording: a report job is unique per order and VIN, so the repeat submission matches the existing job instead of creating a second one.
- The uniqueness rule is one job per order and VIN, so the same VIN cannot open two jobs on one pack.
- You get a plain confirmation message rather than a silent no-op, so you can tell a duplicate from a new assignment.
- The rule is scoped to the order: the same VIN on a different order is a separate purchase and spends that order's credit.
The duplicate is caught before any credit moves
The VIN you type is normalized and hashed, and the insert that would create a new report job carries a uniqueness constraint on the pair of order and VIN hash. A second submission of the same VIN therefore cannot create a second job. The server reports it back as already queued, the endpoint answers with a success status and an alreadyQueued flag, and the wallet prints the message you see.
Because your pack's capacity is measured by counting live jobs, and no new job was created, the remaining-credit count does not move either.
Two nearby cases that behave differently
If the earlier job for that VIN was cancelled while the order was temporarily undeliverable, re-submitting the VIN re-queues that same job rather than refusing it — a deliberate choice so a cancelled job does not sit on a slot for a credit you still own.
If the earlier job failed terminally because the provider holds no vehicle-history record for that VIN, the repeat is not reported as queued at all. You are told no report can be produced for it and that your credit is untouched, so you can point that credit at a different vehicle.
| State of the earlier job | What happens on re-submission |
|---|---|
| Still preparing or already delivered | Recognized as already assigned; no second credit used |
| Cancelled while the order was undeliverable | The same job is re-queued; no extra credit is taken |
| Terminally failed — no provider record | Refused with a no-record message; the credit stays available |
| On a different order entirely | Treated as a new assignment on that order and spends its credit |
What this does not cover
- Uniqueness is per order, not per account: if you buy two packs and assign the same VIN on each, each order spends one of its own credits.
- The check matches the normalized 17-character VIN, so it cannot catch a near-miss — one wrong character is a different vehicle to the system.
- A duplicate submission does not speed up a report that is already being prepared.
Sources reviewed
Open the underlying public source and verify that its scope matches the question you are asking.
Frequently asked questions
Will a duplicate submission restart a report that is stuck?
Only if the earlier job was cancelled. A pending, running or delivered job is left exactly as it is and the message tells you it was already assigned.
Can I swap a VIN I typed wrong for the right one?
There is no self-service way to un-assign a VIN. If the wrong VIN returns no provider record, its credit is released automatically; otherwise use the contact page with your order ID and the VIN's last six characters.
Does the duplicate message mean my report is ready?
No. It only means that VIN already has a job on this pack. Check the numbered report list on the order page for that job's actual status.