Sales Records
A sale record should preserve more than the fact that a collectible changed hands. It should allow another person to reconstruct the transaction: who bought the item, what they agreed to buy, how and when payment became available, which instructions were authorised, what each party said, how possession transferred and how the transaction finally concluded.
For a routine low-value marketplace sale, much of that evidence may remain inside the platform. For a rare, fragile, expensive, privately arranged or disputed sale, weak records can leave a seller unable to prove even basic facts. The purpose is not to create a private dossier on the buyer. It is to create a fair, proportionate and verifiable account of the sale while keeping unnecessary personal information out of the long-term collection record.
Central principle
A listing, payment entry, tracking number or message may each prove one fact. A sound sale file links them so that identity, agreement, money, address, delivery and resolution support one another. Several consistent records are usually stronger than one impressive-looking screenshot.
Chapter map
The record should be readable as a sequence. Each stage answers a different question, and weakness in one stage can break the connection between the others.
Preserve the buyer reference that actually connects the person or account to the order: marketplace username, bidder number, account ID, invoice name or other stable identifier.
Record the item, price, included components, condition disclosures, delivery method, deadlines, return terms and any special concessions or conditions.
Distinguish requested, pending, authorised, cleared, refunded, reversed and charged-back funds. Preserve provider and order references rather than payment credentials.
Connect the authorised address or collection arrangement to dispatch, tracking, delivery, signature or handover evidence.
Record receipt, complaint, return, partial refund, cancellation, dispute or final closure so the file reflects the true outcome rather than the intended sale.
Separate the object's long-term sales history from personal and transactional data that should be restricted, reviewed, redacted, anonymised or deleted.
Collector scenario
A collector sells a scarce boxed figure through a marketplace. The buyer pays, then sends a message asking for delivery to a workplace because nobody will be at home. The seller wants to be helpful and changes the label manually.
What now conflicts
The order address, payment record and actual dispatch address no longer describe the same authorised transaction.
Why it matters
Marketplace or payment protection may depend on sending to the address shown in the transaction and retaining valid shipment or delivery evidence.
Safer response
Follow the platform's approved change process, or cancel and recreate the order with the correct details rather than relying on an informal message.
Diagnosis
These diagnostic tests reveal whether a record is merely populated or genuinely usable. The test is not how many fields exist, but whether the evidence can be joined into a coherent account.
Can the buyer be connected to the order, payment and message thread?
Strong position
A buyer reference, stable account identifier and transaction-specific name are retained together.
Warning sign
Only a common name, nickname or remembered identity remains, with no reliable link to the platform account.
Can another reader reconstruct what was promised?
Strong position
The final listing, accepted offer, disclosures and special terms form one intelligible agreement record.
Warning sign
The price is known, but condition, included components, delivery or return terms are scattered across messages.
Can the financial life of the sale be followed to its final state?
Strong position
Gross price, fees, payment reference, cleared status, refunds and net proceeds reconcile.
Warning sign
The item is marked sold because the buyer said payment was sent, or because an email appeared to confirm it.
Was the item sent or released under an authorised arrangement?
Strong position
Order address, payment address where relevant, actual dispatch address and any approved change are documented.
Warning sign
A post-payment message redirects the parcel to an address that is not reflected in the protected transaction.
Does the file show the final outcome rather than stopping at dispatch?
Strong position
Delivery, acceptance, return, refund, dispute or cancellation is recorded with a closure date.
Warning sign
The record ends when the label was printed, leaving later complaint or refund activity outside the sale file.
Is each retained personal detail necessary for a defined purpose?
Strong position
Private transaction evidence is restricted and public provenance is redacted or generalised.
Warning sign
Addresses, phone numbers, identity documents or financial screenshots are kept indefinitely because they might be useful one day.
Buyer records
The buyer record should distinguish the party to the sale and connect that party to the transaction. Depending on the channel, the most useful identifier may be a marketplace username, bidder number or account ID rather than a legal name. A familiar online identity is useful evidence of account participation, but it is not automatically proof of real-world identity.
Record buyer capacity factually where it matters - private collector, business, institution, agent or not established. Avoid speculative labels. Buying several items does not by itself prove that someone is a dealer.
A current buyer record may hold a preferred email, known account names and useful shipping preferences. Each sale must still preserve its own historical facts: the address used, payment method, terms, messages and delivery evidence. Updating a repeat buyer's profile should never rewrite an earlier transaction.
Safer field
Buyer capacity: private collector / business / institution / agent / not established
Payment records
A sale can be agreed without being paid, paid without being cleared, cleared and then reversed, or completed and later partially refunded. The payment record should show that movement rather than collapsing everything into a single sold flag.
A communication event only. It should trigger checking, not dispatch.
The transaction exists, but it may be pending, held, reversible or under review.
The seller has verified the status in the provider or bank and can act according to the agreed terms and platform rules.
Cash leaves little independent evidence unless the seller creates a receipt. A bank transfer may show only a payer name, amount and reference. In both cases, identify the item precisely and confirm payment through the seller's own records.
Ambiguity about deposits and part-payment commonly produces disputes. State whether a deposit reserves the item, forms part of the price, is refundable, is conditional on inspection, or is forfeited if the buyer defaults.
Full card numbers, security codes, banking credentials, provider passwords and unrelated account information do not strengthen the sale record. Retain transaction references, amount, date and status. Where a screenshot is necessary, crop or redact unrelated balances, payments and personal data while keeping the original securely if there is a justified evidential need.
Communication records
Communications often determine the meaning of the sale. They may establish that a repair was disclosed, a component was excluded, a price included delivery, a buyer requested additional photographs, or a partial refund settled a specific complaint. Keep important agreements on-platform where possible so the messages remain connected to the registered account, listing and dispute process.
Retain when material
Record with context
Factual note
14 July 2026, 15:20 - spoke to buyer by telephone. Buyer confirmed acceptance of the repaired lower corner shown in photographs 8 and 9 and asked that dispatch take place on 16 July.
Unhelpful commentary
Buyer is obviously trying it on again.
Internal notes may later be read by a platform, insurer, accountant, solicitor, buyer or court. Record the report and evidence, not an emotional conclusion.
A screenshot may omit the date, username, listing number, earlier messages, URL or indication that content was edited. Prefer platform-generated order records, original email files, full thread exports, original attachments and case records where available.
Keep original correspondence intact. A summary, translation, redacted working copy or annotated image can be useful, but save it separately and label it clearly, for example: Annotated copy - original retained.
Condition disputes
A condition dispute may turn on whether a fault was described clearly, whether the buyer asked a direct question, which images were supplied and whether later damage is consistent with packing or transit. Vague language such as good condition for age is weaker than a measured, located description tied to specific photographs.
Weak description
Good condition for age.
Evidential description
A 22 mm tear is present at the lower right edge, visible in photographs 6 and 7.
Final listing text and photographs
Additional images supplied before sale
Buyer's exact questions
Seller's exact answers and uncertainty language
Packing and dispatch-condition images
Buyer unboxing or damage images
Return tracking and return-condition images
Inspection, authentication or repair evidence
Refund and final resolution record
Evidence strength
Records do not all carry equal weight. A seller-created summary can organise a case, but it is not equivalent to a provider's transaction record. A buyer-supplied image can be relevant, but it should not replace independent verification.
Evidence
Shows the registered account, item, order number, date, authorised address, payment state and platform context.
Meaning
It links several parts of the transaction inside the system through which the sale occurred.
Collector risk
The account may later be closed or the listing removed. Export or archive significant records while access remains available.
Evidence
Shows amount, currency, payer reference, transaction ID, status, holds, reversals and refunds.
Meaning
It establishes what the provider recorded, not merely what either party claimed about payment.
Collector risk
A visible balance is not always cleared money, and an emailed confirmation may be forged or detached from the real account.
Evidence
Preserves questions, disclosures, offers, instructions, changes, complaints and resolutions in sequence.
Meaning
It can show what the buyer knew, what the seller represented and when an agreement changed.
Collector risk
Cropped screenshots remove context. Off-platform conversations can fragment the evidential chain and may conflict with platform rules.
Evidence
Includes dispatch receipt, tracking, delivery scan, signature, collection receipt or witnessed handover.
Meaning
It connects possession of the item to the authorised destination or collecting representative.
Collector risk
A tracking number alone may prove only that a label existed. Valuable sales need evidence proportionate to delivery risk.
Evidence
Records a contemporaneous summary, telephone call, action, decision or cross-reference.
Meaning
It helps organise the file and preserve events that have no automatic platform record.
Collector risk
It is supporting evidence, not a replacement for original messages, provider records or independent confirmation.
Evidence
May show a payment screen, damage image, message or bank instruction supplied by the buyer.
Meaning
It records the buyer's assertion and may support a wider chronology.
Collector risk
It may be incomplete, altered, outdated or unrelated. Verify important facts through the seller's own account or an independent source.
Action hierarchy
The most valuable action is usually preserving the native record before it disappears. Organisation, summaries and redaction come afterwards.
First
Start with the strongest records produced by the marketplace, payment provider, auction house, carrier or bank.
Then
A folder of files is not yet an intelligible sale record. Show how agreement, payment, dispatch and outcome relate.
Before closure
The completed file should reflect what actually happened, including any cancellation, short payment, partial refund or returned item.
Finally
Preserve the object's history without exposing personal data that is unnecessary for provenance or long-term collection management.
Proportionate practice
Value matters, but so do fragility, rarity, authenticity sensitivity, cross-border delivery, payment method, marketplace protection, buyer history and the likelihood that the sale will later matter to provenance.
A compact record may be enough where the item is replaceable, payment and delivery are straightforward, and little provenance value is likely to arise.
Record bundle
Typical triggers
More context is warranted where condition, completeness, fragility, rarity or an unusual agreement could later matter.
Record bundle
Typical triggers
The file should be capable of supporting a dispute, insurance claim, ownership history or later provenance review without relying on memory.
Record bundle
Typical triggers
Disputes and reversals
A marketplace dispute and a payment-provider chargeback may be different processes with different evidence windows. Do not send an unstructured mass of files. State the allegation, provide a concise chronology and label each exhibit so the reviewer can see how it answers the issue.
Record the complaint, evidence, agreed adjustment, whether the item is retained or returned, the refund transaction ID and the date the case closed. State what the payment resolves.
$35 refunded by agreement in respect of the damaged acrylic display case. Buyer retains the collectible and no return is required.
Myth versus reality
Myth
The buyer's name is enough.
Reality
A name may not connect reliably to the account, order, payment or delivery address. Preserve the stable transaction identifier as well.
Myth
A payment screenshot proves payment.
Reality
It proves only that an image was supplied. Verify the transaction in the seller's own provider or bank account and record its actual status.
Myth
Successful sales do not need their messages.
Reality
Disputes, chargebacks, insurance issues and provenance questions can arise later. Retain the messages that define the agreement and its outcome.
Myth
More personal data creates stronger evidence.
Reality
Excessive data increases privacy and security risk. Strong evidence comes from relevance, context and consistent records, not indiscriminate collection.
Myth
A partial refund closes the matter automatically.
Reality
Record what the refund settles, whether the buyer keeps or returns the item, and whether any further claim remains open.
Myth
The latest buyer profile should replace the old details.
Reality
A repeat buyer's current contact record may change, but each historical sale must preserve the address, username and terms used at that time.
Documentation checklist
A significant sale does not need an elaborate legal file, but it should have a clear reference and a predictable set of records. Consistent filenames make the bundle intelligible without opening every document.
Final listing or catalogue archive
Accepted offer, winning bid or agreed-sale record
Invoice or receipt
Buyer and order reference
Payment confirmation from the relevant provider or bank
Material communication thread
Condition and packing photographs
Shipping label, dispatch receipt or collection record
Tracking and delivery evidence
Refund, return, dispute or chargeback records where applicable
Final sale summary and closure date
Privacy and retention
Buyer records contain personal data. The practical discipline is to define why each category is retained, restrict access, separate public from private records and review whether the information remains necessary. A collecting database should not become an unrestricted archive of old addresses, financial screenshots and private messages.
Potentially retained for the life of the record:
Retain while needed for a defined purpose:
Material that is unnecessary or excessively sensitive:
Specialist threshold
More formal support is warranted where a transaction combines high value with title, authenticity, fraud, export, tax, insurance or data-protection complexity.
Return to the records that preserve how the item was presented and described before agreement.
Return to the complete Sales Records section and its transaction-documentation topics.
Continue into the final object, financial, fulfilment and collection records created after completion.
Reconcile gross sale price, costs, deductions, refunds and the amount actually realised.
Build the evidential link from authorised dispatch through delivery, signature, collection or controlled handover.
Document complaints, returns, refunds, chargebacks and the final resolution of a challenged transaction.
Decide what to preserve, restrict, redact, back up, anonymise or delete after the immediate transaction need has passed.
