goodfolkBook a Call

How to clean a refurbished electronics marketplace catalog

Resolve device variants, standardize supported specifications, and preserve unit-level inspection evidence in an electronics resale catalog.

Refurbished electronics catalog automation should resolve exact device identity, standardize supported specifications, and preserve inspection results for each physical unit. A product family's original specifications do not establish a used device's battery health, network status, or present condition.

That distinction should shape both the data model and the review process.

Identify the configuration before enriching it

An illustrative seller submits “Phone 12, black, 128, good.” Before adding specifications, establish the manufacturer, exact model, storage unit, regional version where relevant, and seller's meaning of “good.”

Do not assume a missing unit or interpret a seller's informal grade as your marketplace's approved condition grade. Resolve those fields with evidence or seller clarification.

Product identity affects the specifications you retrieve, compatible accessories, and the filters buyers use. Treat a model mismatch as a blocking issue for enrichment, not a minor title problem.

Keep four layers separate

LayerExample fieldsSource
Device modelManufacturer and model identifierVerified product reference
ConfigurationStorage, color, region, network variantExact variant evidence
Physical unitBattery test, damage, repair historyCurrent inspection and seller records
OfferPrice, warranty, stockCurrent seller terms and inventory

Where a marketplace has serial numbers or similar identifiers, limit access and avoid exposing them unnecessarily in public listings. The automation does not need every private field to improve a display title.

Standardize condition without inventing it

Different sellers may use “excellent,” “A grade,” and “very good” differently. Define your marketplace's grade criteria and map seller grades only where there is an approved equivalence.

eBay publishes category-specific condition guidance, which illustrates why one condition vocabulary cannot be assumed to mean the same thing everywhere. Your own criteria need to be explicit and visible to reviewers.

When evidence does not support a mapping, preserve the seller grade and request review. Never turn an absent inspection into “tested,” “unlocked,” or “battery healthy.”

Use automation for supported catalog facts

Once identity is established, a research workflow can retrieve published dimensions, display specifications, or connection types. Store the exact source and version context. Validate units and avoid mixing accessories with the device itself.

The manufacturer research guide covers source selection and ambiguous model matches. For supplier specification sheets, use the PDF extraction process.

If current inspection records conflict with a generic product reference, do not resolve the conflict by trusting the cleaner source. A refurbished device may have replacement components or modifications that require a specialist decision.

Keep unit photos truthful

Use the individual device's images when showing wear. A manufacturer stock image may explain the model but cannot document that unit's condition. Label any stock imagery appropriately under your own presentation policy.

Background removal must preserve scratches, cracks, and color. Route uncertain edits for review and retain originals. An image should not imply a better cosmetic grade than the inspection report supports.

Measure errors with different consequences separately

Wrong storage capacity, missing secondary descriptions, and incorrect condition grades are different failures. Track them independently. Include near-identical configurations in a checked evaluation set.

A Goodfolk pilot should begin with a bounded specification or normalization task, not automated authenticity or inspection decisions. Measure exact-variant matches, correct supported fields, review effort, and the ability to withdraw a batch. Those measures give your operations and engineering teams a shared basis for deciding whether to expand.

Sources

Source references checked October 22, 2026. The workflows and examples are Goodfolk’s recommendations.

GOODFOLK

Bring us the catalog work your team keeps doing

We’ll discuss the records, sources, and review rules needed for a useful pilot

Book a Call