How a vehicle gets valued

For: Fleet Managers · Cypress Managers

Before anyone argues about price, Cypress puts a neutral number on the table. This chapter explains where that number comes from, what makes it move, and how to read the card that presents it.

The stack: an engine below, a specialist above

Orbis is the valuation engine — an app of its own that Cypress calls for every vehicle. With a VIN and Black Book configured, the number comes from Black Book's wholesale channel, adjusted for mileage and condition. Without them, Orbis falls back to its own heuristic so no vehicle is ever unvalued. Sequoia is the specialist that interprets the number: comparable listings, the market trend, and a plain sell-or-hold read, presented as the Sequoia card on the vehicle.

What the card shows

• Wholesale — the headline. This is the number the three-prices ladder anchors on.
• Bands — wholesale above/below and trade-in, when the source provides them; retail-clean appears as the CM's ceiling reference.
• Source badge — Black Book, MMR, or Orbis Heuristic, with provenance (publish date, mileage-at-valuation, condition used). If you ever see "Mock data — not real" in amber, you are looking at fixture data on a test environment — never quote it.
• Staleness — valuations age. A stale badge means the inputs have moved (mileage, condition, or time) and a refresh is due.

What makes it move

A valuation is a snapshot of its inputs. It re-runs when:

• the condition score changes — the tiers map to Black Book's adjustment bands, so a 3.5 → 4.5 move is real money;
• the mileage is corrected materially;
• a batch import lands (imports value in bulk automatically);
• someone asks — Request valuation on the vehicle, or Cedar's request valuation action for a set.

The full Orbis report

Behind the card sits the Orbis engine's full report — open it with View in Orbis on any valuation. It carries the complete picture: the wholesale/retail/trade-in bands with the above/below spreads, the exact inputs used (mileage at valuation, condition tier, region), Black Book provenance (UVC, publish date, data frequency), and the valuation history so you can see the number move as inputs changed. For deeper market context a CM can trigger live market research — comparable retail listings scraped on demand, deduplicated into a market read (price quartiles, average days on market) that Sequoia folds into its narrative. Research is deliberate and CM-triggered, never an invisible background cost.

The ±% deltas

Wherever the floor and listing price appear, you'll see ±N.N% vs Orbis under each (in the Seller Hub, vs Orbis retail) — the distance between the human numbers and the computed one. Green means priced above the valuation; deep red (below −5%) is the platform's nudge that the number deserves another look. The offer panel's offer check — "Set a floor price to unlock the offer check" — reads offers against those two lines; it is Sell's own rule, not the plan's advice.

Worked example

The Transit (18,412 miles, condition 4.5, Texas) values at $31,400 wholesale from Black Book, trade-in $29,700, published this week. The Sequoia card lists three comparable Transits within 200 miles — $30,900, $31,800, $32,400 — and reads "SELL — cargo vans in this band are trending down ~2%/month; days-on-market rising." Maria floors at $29,000 (−7.6% vs Orbis, shown amber), Alex lists at $32,500 (+3.5%, green). Neither number argues with the valuation — they bracket it, which is what healthy pricing looks like.

Business rules

• Valuations are advisory: no rule forces the floor or ask to track them. The deltas inform; humans decide.
• Every Black Book call is metered and logged — valuation spend is real money and shows in the platform audit.
• Deep market research (live scraping of retail listings) is a CM-triggered extra, not part of the standard valuation.

Under the hood

Valuations persist per-vehicle with full provenance (source, UVC, condition at valuation, publish date) and an isStale flag; the condition tiers map 1.0–5.0 scores onto Black Book's bands exactly as the CSV importer and the API do. Integrators see valuation-bearing fields on vehicle reads — see the developer docs.