Freeze the shared number
Tell registration and clerking staff that bidder number [number] is temporarily blocked. Do not issue, reprint or reuse it.
REFERENCE / REGISTRATIONIDENTITY COLLISION RECOVERY
Duplicate Bidder Number Assigned During a Live Auction
Use this field procedure when two different registered bidders unexpectedly receive the same bidder number, paddle number or bid card number.
Freeze the shared identifier before it collects more bids, winning lots, invoices or pickup records. Separate the two registrations first; correct individual lots only if the collision has already contaminated sale history.
BUILT FORSmall auction housesRegistration staffClerksAuctioneersCashiers & managers
FIRST 60 SECONDS
Stop the duplicated number from attaching to more activity.
The first task is containment. Freeze the identifier, not the auction: if the collision is contained and the clerk can reliably distinguish every other bidder, unrelated bidding can continue while the back office reconciles the two affected records. Do not begin by moving lots or merging people.
FREEZE → LABEL → SCOPE → SEPARATE
Identify both registrations
Open the two bidder records and label them internally as Record A and Record B so staff can discuss them without relying on the duplicated number.
Secure both physical cards
Mark or collect both paddles or bid cards. Do not let two people continue showing the same number while the software record is being reviewed.
Hold checkout on that number
Pause invoices, card charges, settlement and property release tied to the shared identifier until ownership of each transaction is known.
List every affected transaction
Search the bidder number across bids, wins, invoices, payments, pickup lists and manual sheets. Record the complete scope before editing either registration.
Assign one new number only after the audit
Keep one number with the verified record and issue a new unique number to the other bidder through the supported registration workflow.
INTENT BOUNDARY
This is a registration collision, not a wrong-bidder clerking error.
The recovery path depends on where the error began. Keeping these two failure types separate prevents unnecessary sale-record edits.
Two different people share one bidder number.
The identifier itself is duplicated across two registrations. The first job is to separate the identities and determine which activity belongs to each person.
One lot was recorded against the wrong bidder.
If the registrations are unique but a sold lot was clerked to the wrong valid bidder number, use the Wrong Bidder Number correction runbook instead.
Two people are not a duplicate person record.
Do not merge distinct bidders simply because the number matches. A merge can combine bids, winnings, payments or contact history that should remain separate.
Confirm the number was not intentionally shared.
Some events or systems may deliberately link household members or a shared buying account. Verify the auction's registration policy before treating a shared identifier as accidental.
OPERATING PRINCIPLE
Treat the bidder number as a routing key across the sale.
A bidder number can connect registration, bid history, winning lots, invoices, card payments, tax status, pickup documents and seller settlement. When two people share the same number, every downstream record attached to that identifier becomes potentially ambiguous.
Do not solve the problem by immediately overwriting one registration. First capture both original records and determine whether the duplicated number has already been used. If no activity exists, the fix is a clean registration reassignment. If activity exists, separate identity from transaction history before the new number is issued.
Registration collision
Two bidder records show the same active number.217Record A · Morgan H.active
217Record B · Taylor R.collision
The shared number is compromised. Identify people by their separate registration records until the collision is resolved.
Block new use of the number
Stop registration, reprints, manual cards and clerking against the duplicated identifier until the collision is contained.
Find everything already attached
Search bid history, sold lots, invoices, payments, pickup documents and offline records before changing either bidder profile.
Attribute activity to a person
Use registration details, card possession, timestamps, floor location and source logs to assign affected activity to Record A or Record B.
Create one clean unique identity
Issue one bidder a new number, verify the downstream effect, replace the physical card and document the change.
Published August 12, 2026 · Prepared by Jasper Auction’s small volunteer community
HOW DUPLICATES ARE CREATED
Find the registration path that bypassed uniqueness.
The same visible symptom can come from several different processes. Fixing the source matters because the duplicate may still be spreading.
A number was typed over an existing assignment
An administrator, cashier or registration operator may have manually entered a familiar number without noticing that it was already active.
Manual registrations were imported after doors opened
A paper or offline fallback list may use numbers that the live system has already assigned to walk-in bidders.
A bidder-number range was restarted too early
A second day, ring or registration station may begin again at a range that remains active in the same sale database.
The software is unique but the physical card is not
A reprint, handwritten card or spare paddle may duplicate a number even when the registration records themselves are technically unique.
An older bidder list was merged into the current event
Imported registrations, restored backups or copied event data can collide with numbers already created in the current sale.
A household or team-sharing rule was applied to the wrong people
Confirm whether shared numbers are allowed at all. A feature intended for one buying account should not silently connect unrelated bidders.
SCOPE THE INCIDENT
The amount of recovery work depends on how far the shared number traveled.
Start with the lowest-risk state and expand the hold only when transaction history shows that the duplicate affected live bidding or checkout.
| State | Immediate action | Recovery depth | Do not |
|---|---|---|---|
| Duplicate found before either bidder has bid | Freeze the number and both cards. | Reassign one unique number, verify both records and replace the affected card. | Create lot-level corrections when no sale activity exists. |
| Bids exist but neither bidder has won | Stop new use and save bid history. | Attribute existing bids where practical, then reassign one bidder before more bidding. | Assume all historic bids belong to the bidder whose profile currently displays the number. |
| One bidder has winning lots | Hold those lots from invoice, payment and release. | Verify which person won each affected lot before renumbering and regenerating documents. | Rename the bidder profile and assume prior lots followed the right person. |
| Both bidders have winning lots | Hold every transaction tied to the shared number. | Reconstruct activity lot by lot, separate invoices, then give one bidder a new identifier. | Merge the two people or split the invoice by guesswork. |
| Payment has been applied | Freeze refunds, transfers and settlement changes. | Reconcile buyer, invoice, payment ledger and receipt before any reallocation. | Move money between bidder accounts without a traceable accounting action. |
| Property has been released | Escalate and preserve the release record. | Document possession, payment and identity; obtain management or legal direction where needed. | Hide the incident with a silent back-office number change. |
RECOVERY RUNBOOK
Separate the two bidder identities in a fixed order.
Capture the original state before editing either record. The goal is to preserve transaction history, create one unique identifier for each person and leave a clear explanation of any records that changed.
This is an operational procedure, not legal advice. Sale terms, platform behavior and local law determine how disputed transactions, payments and released property are handled.
Escalation boundary: If either bidder has left the venue, a payment has settled, property has been released, or either party disputes the correction, stop routine record editing. Preserve the original records and escalate the incident to management and, where appropriate, legal counsel before changing the buyer of record.
Recovery sequence
Separate identity before editing history.FreezeStop new use of the duplicated number.
ScopeList bids, wins, invoices, payments and release records attached to it.
VerifyAttribute each affected activity to Record A or Record B.
ReassignGive one bidder a verified unused number through the supported workflow.
RecheckConfirm invoices, payments, cards and pickup records after the change.
ResumeRelease the hold only after the duplicate scan is clean.
- 01
Block the duplicated bidder number everywhere
Tell registration, clerking, simulcast and cashier staff not to use the number. Stop card reprints and manual reuse. If the platform supports a note or hold flag, place it on both affected registrations.
- 02
Capture both original bidder records
Save bidder name, registration ID, contact details, approval status, tax or resale status, payment method, registration time, operator and the bidder number shown before any edit.
- 03
Secure and distinguish the physical bidder cards
Collect or clearly mark both duplicate paddles. Use neutral temporary labels such as Record A and Record B while reconciling the incident; do not create a second unofficial bidder number on paper.
- 04
Search the duplicated number across the entire sale
List floor bids, online or phone references, winning lots, invoices, payment records, pickup documents, clerk notes and any handwritten sale sheets connected to that identifier.
- 05
Determine which activity belongs to which person
Match each affected item using the strongest available evidence: registration timestamps, card possession, bidder location, clerk notes, online account, phone sheet, room recording and contemporaneous staff observations.
- 06
Decide which registration keeps the original number
Follow the platform and event policy for deciding which registration keeps the original number. If neither defines the choice, use a documented local rule that minimizes unnecessary historical changes rather than choosing whichever invoice is easiest to edit.
- 07
Assign the other bidder a new unique number
Use the software's supported edit or re-registration path. Before saving, confirm that the new number is unused and check whether the platform will retroactively relabel bids, lots or invoices.
- 08
Correct only the transactions proven to be misattributed
If a lot, invoice or payment is attached to the wrong person because of the collision, use the platform's supported correction workflow. If a sold lot itself was clerked to the wrong valid bidder number, follow the separate wrong-bidder runbook.
- 09
Replace cards and buyer-facing documents
Issue the new physical bidder card, void obsolete cards, regenerate affected invoices or pickup documents and tell the cashier which version is active.
- 10
Run a second duplicate-number scan before release
Search the active bidder list again, verify that every active person has the intended identifier and close the incident only when bids, invoices, payments and release records reconcile.
IDENTITY EVIDENCE
Prove person-to-activity links without trusting the duplicated number.
Because the identifier itself is compromised, use evidence that can distinguish the two people independently of that number.
System record created for each person
Use internal record IDs, timestamps, operator names and contact details that remain unique even when the visible bidder number does not.
Who held which card and where
Record the bidder's location, card handed out at registration and any reprint or handwritten replacement issued during the sale.
Online account, phone sheet or room position
Match a bid to a channel that identifies the person independently of the duplicated paddle number.
Invoice, payment and pickup identity
Use buyer-facing documents, payment authorization and identity checks as supporting evidence, while remembering that downstream records may have inherited the same number collision.
SYSTEM IMPACT CHECK
Know what changes when a bidder number is edited.
Different auction platforms handle identifiers differently. Test or verify the effect before the operator changes a live bidder record.
| Record | Question before edit | Verify after edit | Risk |
|---|---|---|---|
| Bid history | Does changing the profile number relabel earlier bids? | Each historic bid still points to the intended person and source. | A clean new number can rewrite the apparent history. |
| Winning lots | Are lots linked by bidder ID or visible bidder number? | Buyer identity, hammer amount and lot status remain correct. | Lots may move automatically or remain attached to the old number. |
| Invoice | Will the invoice follow the bidder profile automatically? | Only the correct person's lots, fees, tax and contact details remain. | Two people's purchases may stay combined. |
| Payment | Is payment linked to invoice, profile or account token? | Receipts and balances match the correct bidder. | Money may be moved without the transaction history following it. |
| Pickup / release | Which identifier is printed on the release document? | The active card, invoice and release list all match one person. | Property can be released on an obsolete duplicate card. |
| Seller settlement | Are buyer-side changes reflected in settlement calculations? | Lot status, fees and proceeds still reconcile. | Back-office records can diverge from corrected buyer documents. |
PREVENTION
Make duplicate assignment difficult at every registration path.
Software validation helps only when every registration passes through it. Prefer platform-assigned bidder numbers and built-in uniqueness validation where available; manual numbering should be the exception, not the default. Include walk-ins, imported bidder lists, offline fallback, card reprints and multi-day events in the same uniqueness control.
Before doors open, export or search the active bidder list for duplicate numbers. During registration, keep a simple card-issuance log so a physical paddle cannot be duplicated even when the database is correct.
Pre-sale control
Make duplicate assignment hard to create.214A. PatelOK215R. DiazOK216J. ChenOK217Morgan H.IN USE218Next availableFREEUnique checkReject a number that is already active.
Card logTrack who received each physical paddle and every reprint.
Range controlKeep manual and offline ranges from colliding with live assignments.
Final scanSearch the active bidder list for duplicates before bidding opens.
- 01
Require a uniqueness check on every manual assignment
Do not let an operator overwrite an automatically generated number without checking the active bidder list first.
- 02
Keep one bidder-card issuance log
Record number, bidder name, registration ID, card print time and operator. Mark every reprint and voided card.
- 03
Reserve separate ranges for offline fallback
If paper registration is required during a system outage, use a pre-reserved range that cannot collide with numbers the live system is still assigning.
- 04
Scan imported lists before activation
Check for duplicate bidder numbers after importing registrations from a prior event, partner system or backup file and before those records can bid.
- 05
Define whether shared household numbers are permitted
Make the policy explicit. If sharing is allowed, require an intentional link to one buying account; otherwise every individual bidder receives a unique number.
- 06
Run a final duplicate report before live bidding
Search active bidder numbers, resolve every collision and confirm that physical cards match the final registration list before the auctioneer opens the first lot.
INCIDENT RECORD
Keep a compact record of the two identities and the split.
The record should show why the shared number was frozen, which activity belonged to each person and what identifier each bidder used after recovery.
Printable duplicate bidder number incident record
Copy this form into the sale file or download the plain-text version for the registration or clerk station.
DUPLICATE BIDDER NUMBER INCIDENT RECORD SALE / RING: ______________________________________________ DATE / TIME FOUND: _________________________________________ DUPLICATED BIDDER NUMBER: __________________________________ RECORD A NAME: ______________________________________________________ INTERNAL REGISTRATION ID: __________________________________ REGISTRATION TIME / OPERATOR: ______________________________ PHYSICAL CARD STATUS: ______________________________________ RECORD B NAME: ______________________________________________________ INTERNAL REGISTRATION ID: __________________________________ REGISTRATION TIME / OPERATOR: ______________________________ PHYSICAL CARD STATUS: ______________________________________ ACTIVITY FOUND UNDER SHARED NUMBER: [ ] Bids only [ ] Winning lots [ ] Invoice generated [ ] Payment applied [ ] Pickup / release document [ ] Seller settlement affected [ ] Offline / paper records Other: ____________________________________________________ ACTIVITY ATTRIBUTED TO RECORD A: ___________________________________________________________ ___________________________________________________________ ACTIVITY ATTRIBUTED TO RECORD B: ___________________________________________________________ ___________________________________________________________ ORIGINAL NUMBER KEPT BY: ___________________________________ NEW UNIQUE NUMBER ASSIGNED TO: ______________________________ NEW NUMBER: ________________________________________________ DOCUMENTS / RECORDS CORRECTED: ___________________________________________________________ ___________________________________________________________ AUTHORIZED BY: _____________________________________________ SOFTWARE CHANGE MADE BY: ___________________________________ CARDS REPLACED / VOIDED BY: _________________________________ FINAL DUPLICATE SCAN COMPLETED BY: __________________________ ROOT CAUSE: ___________________________________________________________ PREVENTION ACTION: ___________________________________________________________ NOTES: ___________________________________________________________ ___________________________________________________________
OPERATING QUESTIONS
Common questions when two bidders share the same number.
These answers focus on identity separation and registration recovery. Software behavior varies by platform.
- Q1
What if the duplicate is found before either bidder has bid?
Freeze the number, verify both registrations and cards, then assign one person a new unique number. If no bids, wins, invoices or payments are attached, no lot-level correction should be necessary.
- Q2
What if one bidder has already won a lot?
Hold affected invoices and stop property release. Determine which person made each bid and won each lot before changing the registrations, then verify the lot and invoice again after one bidder receives a new number.
- Q3
What if both bidders have winning lots?
Hold every transaction tied to the shared number and reconcile lot by lot. Separate the two people's purchases before final invoicing, payment allocation or property release.
- Q4
Can staff simply change one bidder number and continue?
Only after checking what the software will do to historical bids, lots, invoices and payments. Capture the original state first, make one controlled change and verify every affected record afterward.
- Q5
Should the two bidder records be merged?
Not when they represent two different people. Merge only when staff have confirmed that both profiles belong to the same bidder and understand what the platform will do to bids, winnings, payments and login credentials.
- Q6
What if the software normally prevents duplicate numbers?
Check manual cards, offline registration, imported lists, restored data, multi-day ranges and administrator overrides. The collision may have been created outside the normal validation path.
- Q7
Can the auction continue while the duplicate is resolved?
If the issue is contained, management may keep unrelated bidding moving while the duplicated number and its transactions remain blocked. Stop if the clerk cannot reliably distinguish bidders or the collision may affect more records.
- Q8
How can duplicate bidder numbers be prevented?
Use uniqueness validation, a physical card log, controlled number ranges, a pre-sale duplicate scan and a rule that offline or imported registrations are reconciled before live bidding begins.
FIELD RULE
When one number points to two people, stop trusting the number.
Freeze the identifier, preserve both registrations, map every attached transaction to the correct person and only then assign one new unique number. Correct a sold lot only when the collision actually caused a sale-record error.