Auction rules.

Signed in

You must be authenticated on an account that is active and in good standing.

Email confirmed

The email address on the account must have been verified through the link we send.

Identity approved

Your identity verification must have been reviewed and approved. Pending and rejected accounts cannot bid.

Not the seller

A seller may not bid on their own lot, directly or through a related account.

Lot is live

The lot must be published and open, and the server clock must be between the start and closing times.

Valid amount

The amount must be a positive figure that satisfies the increment or decrement rule for that lot.

If any condition fails, the bid is rejected and nothing is recorded as accepted. The reason is shown to you in the auction room.

Opening bid

The first bid must be at least the published starting price.

Subsequent bids

Each bid must be at least the current highest accepted bid plus the lot's minimum increment.

Winner

The highest accepted bid at closing, provided the reserve price has been met.

Reserve not met

If the reserve is not reached, no sale occurs. The seller and the top bidder are notified and the lot closes unsold.

Opening bid

The first bid must be at or below the published ceiling price.

Subsequent bids

Each bid must be at or below the current lowest accepted bid, less the lot's minimum decrement.

Floor

No bid may fall below the configured minimum for the lot.

Winner

The lowest accepted bid at closing, subject to that floor.

This is a descending sealed-outcome format defined by the platform, not a traditional Dutch clock auction: the first bidder to accept a falling price does not immediately win, and bidding continues until the lot closes.

If a bid is accepted when less than 120 seconds remain, the closing time is moved to 120 seconds from that moment. This can happen up to ten times on a single lot. Every extension is written to the lot record, recorded in the audit trail and broadcast to everyone in the auction room. Your browser always re-reads the authoritative closing time from the server rather than trusting its own countdown.

No withdrawal

Accepted bids cannot be edited, retracted or cancelled by the bidder for any reason.

Administrator invalidation

Only an administrator may invalidate a bid, and only with a recorded reason. The original record is retained.

Seller cancellation

A seller may not cancel a lot once it has received an accepted bid. Cancellation from that point is an administrator action.

Automatic bidding

Proxy or automatic bidding is not offered. Every bid is placed deliberately by the bidder.

At the closing moment the platform locks the lot, blocks further bids, evaluates every accepted bid, applies the reserve, writes exactly one outcome record, creates the settlement record and notifies the parties. The process is idempotent: even if the closure job runs twice, a lot can only ever produce one result.

Where two accepted bids are equal, the bid the server recorded first wins. Server sequence, not the time shown on any device, is decisive.

Reserve price

Published on the lot page before bidding opens.

Bid activity

Amounts and timestamps are visible to everyone in the auction room.

Bidder identity

Never shown to other bidders. Bidders appear under masked labels.

Winning price

After close, visible only to the seller, the winner and administrators.

All auctions are conducted in PHP. The winner's total is the winning bid plus value-added tax and the buyer's premium — 12% and 5% by default, unless the lot page states otherwise. All money calculations are performed with exact decimal arithmetic on the server at closing.

Lot-specific questions should be raised through the lot page or with our team well before the closing time. Questions and their answers are public so that all bidders compete on the same information.