Offer Rules: your auction bands
Configure how offers answer themselves — auto-accept, auto-decline, and the band you personally review.
TL;DRAI summary
This chapter explains how Cypress can automatically accept or decline offers for you based on price bands you set. This saves you time by only routing offers that need your personal judgment for review.
For: Fleet Managers · Cypress Managers
This chapter is where delegation bites hardest. Under the lifecycle switch Cypress can configure your bands (with your floor as the anchor); under the sell switch Cypress can also decide the offers your bands route to review — accept or reject anything between floor and target.
Never delegable, under any switch: accepting an offer below your floor price — that decision is always your own Fleet Manager’s.
Everything done under delegation is logged with a Cypress · on behalf badge and notifies your Fleet Managers. Manage the switches in Settings → Organization → Permissions — the full story is in Delegation — Cypress on your behalf.
A live listing gets offers at all hours. Offer Rules are the standing instructions that answer them instantly — so a serious buyer at 11pm gets an answer at 11pm, and only the offers that genuinely need your judgment wait for you. They are found on the Offer Rules tab of the Seller Hub vehicle panel.
The three bands
Offer Rules split the price axis into three zones. The diagram reuses the price ladder — same axis, now with an incoming offer tested against it:
- Auto-accept at or above — the offer accepts on the spot, every other open offer is declined, and the closing opens. The floor-consent rule is why this is safe: the accept line sits at or above the floor, so instant acceptance is consent the seller already gave. Cypress staff setting a seller's rules are refused a line below the floor, and so are Cypress's automations; only the seller's own Fleet Manager or admin can draw it lower, which is that consent given in advance.
- Review between — the vehicle moves to Under Offer and the offer waits in the Seller Hub for the Fleet Manager — or for Cypress, when the org has delegated review-range decisions. If the amount is below the floor, it escalates: the notification says so, and only the seller's own Fleet Manager can accept it — delegation never covers below-floor offers.
- Auto-decline below — the buyer hears "no" immediately, with the vehicle staying live. No noise in your queue.
No rules configured (or rules disabled) means everything goes to review — safe, but slow. The bands are what make a listing feel alive.
Setting the bands
On the vehicle's Offer Rules tab, set the two lines. Three things fill them in automatically if you don't:
- A pricing rule that matched at launch computes all three numbers — see Pricing rules.
- The launch dialog lets the launcher type them by hand.
- A price set any other way (the vehicle panel, a bulk edit, Cedar, an approved price change, or prices pushed over the API) draws them by one rule: auto-decline below the floor, auto-accept at or above the listing price, and your review in between.
Changing the floor or listing price later re-arms the bands to match, and the change is logged with before and after values. A vehicle priced by a pricing rule keeps its rule: when its floor moves, the rule's bands are worked again from the new floor. Any other bands (accepting at the floor, say) are a pricing rule's or an automation's to set: the Apply pricing rule action draws them from the floor or the listing price, plus or minus an amount.
How Cedar can help here
Offer Rules are a natural Cedar conversation: "set offering rules for this van — accept at floor, decline under 27" becomes a proposal card with the bands drawn on the ladder. Sequoia advises the levels — its market read flags an accept line set below where comparable vans are clearing. Rules configured through Cedar are audited like every agentic write: proposed, confirmed by you, logged with both names.
Worked example
The Transit lists at $32,500 with a $29,000 floor. Alex arms the bands: auto-accept at $29,000 (the floor — Maria's standing consent), auto-decline below $27,000.
Three offers arrive the first week:
| Offer | Band | What happened |
|---|---|---|
| $25,900 | below $27,000 | Declined instantly. The buyer was told within seconds; Maria never saw it. |
| $28,200 | $27,000–$29,000 | Routed to review, flagged below floor — only Maria can accept this one. |
| $30,100 | ≥ $29,000 | Accepted instantly at 10:41pm. Closing opened before Maria woke up. |
(In our running story, the $28,200 offer is the one that turns into a negotiation — picked up in the next chapter.)
Business rules
- The bands answer offers; the Buy Now button is separate consent — it transacts at the listing price with no bands involved.
- Auto-accepted offers set both approvals (
autoProcessed: truein the audit trail) — the log always shows a decision was rule-made. - Every instant decision writes to the vehicle's Activity tab with the rule line that made it ("auto-accepted: ≥ $29,000").
- An auto-accepted offer is an accepted deal like any other: an automation's Offer
Accepted trigger runs for it, and partners hear
OFFERS.ACCEPTEDwithautoProcessed: true. See Offers in automations. - Disabling rules never cancels open offers — it only stops new instant answers.
Under the hood
The bands live per-vehicle as the auction rule
(autoAcceptAbove / autoDenyBelow with a review band between), carrying
an immutable audit snapshot of what configured them. Integrators read and
set the same numbers through listing prices — the mapping is in the
developer pricing docs.