Bids
Every bid, every channel, in order
From the first absentee filed two weeks before the sale to the floor bid that landed the hammer — every bid recorded with sub-second timing and channel attribution.
Data domains
The atomic unit of a sale
A bid is the smallest event in the auction system: someone, on a channel, at a moment in time, offered an amount on a lot. The Bids domain stores every one — winning and losing, accepted and rejected, on-platform and floor — with the channel attribution intact so you can study the difference in behaviour between online, phone, absentee, and rostrum bids.
Because bids carry timing down to the millisecond, the domain supports analysis the printed result book can't: increment dynamics, channel competition, opening-bid effects, and end-of-lot timing patterns. All of it queryable from your BI tool or an MCP-compatible AI.
Ask your data
From a question to a channel-share answer
Ask what proportion of winning bids each channel produced. The MCP server traces every bid through to the hammer and returns the breakdown.
Access & governance
Open to analysts, audited to the bid
Bid data is operationally important and broadly accessible to analyst roles. Per-bid identification (which paddle placed which amount) is subject to the Customer domain's PII rules when joined.
Aggregate bid analytics (counts, channel mix, increment distribution) are available to all authenticated roles without joining to PII.
Joining bids to paddle identity for a named bidder requires the `customers.read.pii` capability.
Every retrieval of identified bid data is logged for downstream compliance review.
Related domains
Bids depend on lots, customers, and auctions
Let's talk
Ready to modernize your auction house?
Book a personalised demo and see Auction Rabbit tailored to your sale calendar