Item arrived damaged
Scratches, cracks, dents, broken components, water damage, and other defects.
Marketplace evidence
Verify marketplace dispute photos before issuing a refund or payout
Buyer and seller photos can directly affect refunds, payouts, account restrictions, and support decisions. essential-fd checks that evidence for technically verifiable signs of manipulation, reuse, and inconsistency.
File history
A few plausible photos often determine a support decision while their source and history remain unclear. essential-fd analyzes the file itself and returns a clear OK or FLAG result.
Dispute categories
Scratches, cracks, dents, broken components, water damage, and other defects.
Evidence of differences in listing, description, size, color, condition, or components.
Compare buyer evidence with seller photos, listings, and packaging documentation.
Images of incomplete orders, opened packaging, accessories, and product contents.
Compare buyer, seller, warehouse, and return-processing evidence.
Analyze packaging, labels, delivery conditions, and products before and after shipment.
Support disputes for used products, electronics, clothing, furniture, and collectibles.
How it works
The buyer or seller uses the existing application, dispute portal, ticket, or email workflow.
Check metadata, software, source, duplicate relationships, compression, encoding, and cross-file consistency.
OK means no defined finding. FLAG identifies a specific technical issue requiring attention.
Display it in the case, route automatically, or add it to the agent’s review information.
Evidence checks
Exact duplicates and related versions across orders, accounts, and support cases.
Characteristics associated with downloading, resaving, screen capture, or another source.
Technical properties indicating screen capture rather than a direct camera file.
Compare available dates with order, delivery, dispute, return, and shipping timelines.
Inconsistent device, software, dimensions, or encoding across one claimed sequence.
Assess whether editing, cropping, annotation, conversion, or resaving matches the expected workflow.
Both sides of the case
Compare buyer and seller photos with listing images, warehouse inspections, packaging, delivery evidence, return-processing images, and earlier disputes.
Identify listing-image reuse, damage predating a transaction, files repeated across cases, and inconsistent technical histories. Findings should be assessed with transaction and support data.
Fairer decisions
Run checks in the background. Cases without defined findings continue normally; concrete findings reach experienced reviewers before refund, payout, or account decisions.
Find repeated or externally sourced evidence.
Assess buyer and seller files by the same technical rules.
Connect images and patterns across cases.
Record the concrete reason for specialist review.
Integration
Use results to approve cases, route flags, request new evidence, compare prior disputes, enrich a risk model, support abuse investigations, or preserve audit evidence.
More informed decisions
Check buyer and seller photos without adding friction to every case.
FAQ
No. It analyzes files for defined technical findings that the marketplace evaluates with transaction data and statements.
Yes, where listing images and other case files are provided.
Some retain downloading, screenshot, software processing, or prior-use traces. Not every downloaded image can be identified.
It can identify reused images and related patterns across disputes for use in a wider fraud system.
No. Images already submitted through the marketplace can be analyzed.
This workflow focuses on images. Video support depends on deployment requirements.