Your auction knows a great deal about your bidders. Most platforms waste it.

Events, not exports

A nightly CSV export tells you what happened yesterday. An event stream tells you what is happening now, while you can still do something about it.

The platform emits an event when a bidder registers, when a bid is placed, when a bidder is outbid, when a lot closes, when an invoice is issued. You subscribe to the ones you care about and receive them as they occur.

How it reaches you

Delivery is push, not polling. The platform calls your system over outbound webhooks the moment something happens, and each endpoint carries its own agreed secret, so your side can verify the call really came from us. Nothing on your side asks “anything new?” every thirty seconds; your CRM is simply told. If your system is down, delivery retries on a widening schedule for more than a day, so an outage costs you a delay, not the data.

The full delivery contract — what a notification carries, the retry schedule, and why a repeat is safe — is documented in notifications and webhooks.

Into your CRM

This is what most customers use it for. Point the event stream at your CRM and it accumulates a real profile of each bidder: which categories they bid in, which price bands, how often they win, how far they push before stopping, which auctions they registered for and skipped.

That profile is the difference between sending every consignment announcement to your whole list, and telling the forty people who bid on Dutch modernist paintings that you have taken in a Dutch modernist painting. The auction house owns this data. We just make sure it reaches you in a usable form.

Automated communication

Events can also drive communication directly — an onboarding sequence when a bidder registers, a reminder when a watched lot approaches its close, a confirmation when an invoice is paid. The trigger is the event; the message is yours.

Worth being honest about

An event system is not useful on its own. It is useful when you have somewhere to send the events and something you intend to do with them. If you do not yet run a CRM, the sensible order is to start with one and connect it afterwards — we can advise on the shape of that, and the integration is straightforward once the destination exists.