Orders
Where the hammer becomes money
Every invoice, every line — hammer, buyer's premium, VAT, settlement status, payment method — the data that closes the loop between the rostrum and the bank.
Data domains
The settlement layer
Orders pick up where bids end. Once a lot is hammered, an order is created — capturing the buyer paddle, the winning hammer, the buyer's premium tier applied, any VAT, the agreed settlement currency, the chosen payment method, and the settlement status as it changes from `pending` to `paid` to `released`.
Because orders are stored as line items keyed to the lot and the buyer, they connect cleanly to both the Lots and Customer domains. That's what lets an AI tool answer 'what's our day-sales-outstanding by buyer region for the last twelve months' without going outside the platform.
Ask your data
From a question to a settlement aging view
Ask how fast a region settles. The MCP server joins orders with customer geography and returns a region-level days-to-settle view.
Access & governance
Finance-sensitive, audit-heavy
Orders carry the money. Headline aggregates are accessible to analyst roles; per-invoice detail and any access that would let a role infer a buyer's payment behaviour is gated.
Aggregate revenue, DSO, and settlement-rate metrics are accessible to all analyst roles.
Per-invoice detail — hammer, premium, payment method on a named buyer — requires the finance role.
Any export of more than 50 invoices is logged with the requesting role and the bounding filter, and surfaces in the finance audit dashboard.
Related domains
Orders close the loop
Let's talk
Ready to modernize your auction house?
Book a personalised demo and see Auction Rabbit tailored to your sale calendar