A silent auction needs more than photographs of the lots and a box for an amount. The organiser needs to know which bids are valid, when bidding closes and what should happen after a winner is identified.
Agree the auction rules first
Each lot could have a description, photographs, a starting amount and any bid increments you choose. Participants would need a clear account or registration process and access to the rules before bidding.
Decide whether bidders see the current leading amount, whether identities remain hidden from other participants and how simultaneous or tied bids are handled. Any conditions applying to your auction would need appropriate confirmation before launch.
Make the bid history understandable
The system could record the lot, bidder, amount and acceptance time. A connection problem should not leave someone assuming a bid succeeded when it did not. Participants need a clear confirmation, and the organiser needs an auditable history.
Closing should follow a defined server-side time and the rules you approve. Automatic extensions, if wanted, are a separate feature rather than something to assume.
Plan what happens after the bidding
A winning bid is not the same as completed payment or collection. Staff need separate records for contacting the winner, receiving payment and handing over the item.
If online payment is included, the provider, supported transactions and any charges would form part of the proposal. A simpler first version could record payments handled through your agreed existing process.
Test a complete auction before launch
Digital Solutions can help scope a small pilot with a limited number of lots. Test a late bid, two bids arriving together, a withdrawn lot and an unpaid winning bid, alongside the normal successful journey.
Explore the relevant software
You can also explore our custom software development and mobile app development services, or email info@digitalsolutions.help.