Auction modes

Every auction on Haubot runs in one of two operating modes. The bidding mechanics are identical — same increment rules, same anti-sniping, same binding-bid rule. The difference is who acts as seller of record and who handles the post-auction process.

Seller Managed auctions

A verified third-party seller publishes the lot. The seller is the principal: when the auction closes, the winning buyer pays the seller directly, and the seller arranges invoice, release and handover. Haubot is the auction operator and dispute arbiter — not a party to the underlying transaction.

Trust model

• Haubot does not hold the purchase price, does not issue the seller's invoice, does not act as escrow agent.
• Both parties lock a tier-based deposit to participate. Deposits secure platform obligations (binding bids, no-payment defaults) — they are not transferred between the parties.
• Haubot runs a structured 3-round dispute process if the buyer claims to have paid and the seller denies receipt (or vice versa). Haubot decides only platform consequences (deposit release / forfeit, fee status) — not money compensation between buyer and seller.

Use this mode when

• You want full control of invoicing, payment terms and release.
• You're comfortable settling payment directly with the buyer once the auction closes.
• The lot is at your site or otherwise handled outside Haubot's logistics.

Haubot Managed auctions

Haubot (or a named Haubot entity) publishes the lot — either from Haubot's own stock or as a consignor's lot taken on consignment. Haubot is the seller of record vis-à-vis the buyer: Haubot issues the invoice, receives payment, coordinates release and handles post-sale administration.

Trust model

• Buyer pays Haubot, not the underlying owner. For consigned lots, Haubot settles separately with the consignor under a written consignment agreement — that relationship is invisible to the buyer.
• Both sides still lock the same tier-based deposit; the buyer's deposit secures the buyer's obligations and Haubot's deposit covers the seller-side of platform enforcement.
• Disputes follow the same 3-round process. The pool of disputable events is narrower — buyer-seller payment disputes don't arise, because payment goes through Haubot — but reserve-not-met, no-bids, and post-sale collection or documentation disagreements still apply.

Use this mode when

• You're consigning a lot to Haubot and want Haubot to run the entire sale.
• You want centralised invoicing, payment handling and release coordination.
• The lot is high-value enough to justify the managed structure.

How to tell which mode you're in

The auction page, lot card and auction confirmation all carry the badge. The named selling entity, payment instructions and invoice issuer appear on the lot page and on any documents Haubot generates.

What the modes share

• Tier-based deposits (USD 100 / 1,000 / 5,000 / 10,000) — see Deposits and fees.
• 5%-of-starting-price bid increments with a USD 50 floor and a USD 500 ceiling — see Bidding rules.
• 2-minute / 2-minute anti-sniping (a bid in the last 2 minutes extends the close by 2 minutes).
• Hidden reserve with a public "reserve met / not met" indicator.
• Binding, irrevocable bids.
• 3-round, 24-hour-per-round dispute process — see Disputes.
• "As is, where is" basis unless a specific written warranty is displayed on the lot.

What's NOT supported (yet)

• Sealed-bid auctions — all bids are visible to other bidders during the auction.
• Reverse auctions (buyer posts wanted, sellers bid down) — Wanted listings exist but not as an auction format.
• Multi-lot auctions — one listing equals one lot. A dealer with 12 forklifts publishes 12 separate listings.

If your use case fits one of these, talk to support — we may add depending on demand.