Custody Exceptions

Loaners and stored tires are customer property in your custody, and the worst custody problems are the quiet ones: a loaner marked "checked out" that no agreement explains, two storage records that look like one physical set of tires, a paid loaner charge that never reached an invoice. Custody Exceptions is where those inconsistencies surface — automatically — and stay until a person deals with them.

What lands here

ShopCommander opens an exception whenever custody records stop reconciling:

• Orphan checkout — a loaner shows "checked out" but no open agreement exists.
• Damage hold — a loaner came back with reported damage. It stays out of the fleet until the damage is resolved here (or on the fleet card) with a recorded reason.
• Cleaning — a routine return awaiting cleaning; marking the vehicle ready resolves it automatically.
• Unbilled paid loaner — a paid agreement whose charge has no repair-order line item, so the books can't see it.
• Duplicate active set / bin collision — two active tire records that look like one physical set, or two sets claiming the same explicit bin.
• Stale scheduled swap — a set still marked "scheduled" after its appointment was cancelled.
• Over capacity — a configured storage location holding more sets than it's set up for.

A nightly reconciliation sweep re-checks the whole shop, so anything that drifts reappears here on its own.

Resolving vs overriding

Every exception offers two exits, and they mean different things:

• Resolve — the underlying problem was actually fixed (the damage was repaired, the duplicate was merged, the charge was billed). Add a short note about what you did.
• Override — you're accepting the state as-is. A reason is required, and it's recorded with your name and the time. Overrides are for judgment calls — "customer genuinely has two identical sets" — not for making the list shorter.

Filter by domain (Loaners / Tires) with the chips at the top. High-severity items are the ones that can cost you a dispute — clear those first.