Superbuy Spreadsheet Fields: A Transparent Product Record

Start with identity, not a persuasive label

The first job of a row is identification. A useful record needs a stable internal ID, a neutral product title, a category and the exact destination URL. The title should describe the object that the link currently presents, not the object an editor hoped to find. A row called “black zip hoodie” should not lead to a deposit page, replacement drawstring or unrelated colour. The internal ID matters because titles and URLs can change; it lets editors discuss the same record without relying on a fragile row number.

Keep title and category separate. The title answers “what is this record?” while the category answers “where should it be browsed?” Categories should come from a controlled list, so “sneakers,” “trainers” and “shoes” do not create three accidental sections. A descriptive title can include a visible style or form, but it should avoid claims about authenticity, material or performance unless the source provides reliable evidence. Identification fields help retrieval; they are not endorsements.

• Record ID
• Neutral product title
• Controlled category
• Exact destination URL
• Listing type
• Last-verified date

Treat the destination URL as a typed field

A URL is not complete simply because it opens. The record should also label the destination type: full product, add-on, deposit, difference payment, replacement part or another clearly defined page. Similar images may appear across several link types, and a low displayed amount can belong to a deposit rather than the full item. Storing the type beside the link makes that ambiguity visible before anyone compares prices or options.

Preserve the exact destination that was checked and avoid silently swapping a dead page for a loosely similar item. When a redirect occurs, record the final destination separately from the submitted URL. If the final page no longer matches the title, image and listing type, the right status is “needs review,” not “verified.” This turns URL checking into an auditable process and prevents a spreadsheet from appearing current just because every link returns an HTTP success code.

• Full product
• Deposit
• Add-on
• Difference payment
• Replacement component
• Unknown—review required

Separate source facts from editorial fields

Source fields reproduce what can be observed on the destination page at the time of review: displayed title, available option labels, visible price snapshot, seller identifier when shown, first image and any published measurements. Editorial fields are created by the index: normalized title, category, completeness status, risk note and verification date. Mixing the two makes it impossible to know whether a phrase came from the listing or from an editor’s interpretation.

A simple convention solves the problem. Group raw source values separately from normalized values, and write notes as bounded observations. “Listing shows sizes M–XL on 14 August 2026” is traceable. “Fits true to size” is not supported without dependable measurement or fit evidence. “First image matches the black option” is a checkable relationship. “Best quality” is an undefined opinion. The Superbuy spreadsheet database becomes more trustworthy when it records the limits of each statement.

Record price as a dated snapshot

A price field needs context: amount, currency, the option to which it applies and the date checked. Marketplace pages may show a starting value, a range, a deposit or a price that changes with the selected variant. A single number without those qualifiers invites a false comparison. The spreadsheet should never convert a starting price into a claim about the full product or present an old snapshot as a live quote.

Keep any converted currency in a separate estimated field with the exchange-rate date and a clear rounding rule. That value is useful for rough sorting, not checkout. Product cost is also not delivered cost: domestic delivery, payment handling, international shipping and destination charges sit outside a basic product-price field. A transparent row therefore makes the price snapshot searchable while directing the user to verify the current amount and selected option at the destination.

Make variants structured enough to compare

Do not squeeze every colour, size and style into one free-text cell. Use separate fields for option groups, then keep the source wording where it matters. A row can say that size information is present, absent or supplied only as labels; it should not imply that an XL from one seller equals an XL from another. Measurements, when published, belong in their own field with units and the referenced variant.

Coverage is different from availability. “Recorded options: black and grey; sizes M–XL” describes the captured page. “Available now” is a volatile claim that should be checked at the destination. If the listing has too many combinations to represent accurately, use a coverage note such as “partial—open listing for full matrix.” This is better than truncating the list without warning. The goal is comparison while preserving uncertainty.

Use images as matching evidence

An image field should identify the first image used by the record and, when practical, retain a source-image reference for editorial audits. The important test is not whether an image looks attractive; it is whether the record title, selected listing type and destination page describe the same object. A product card showing a bag while the destination opens a strap-only option has failed even if both pages load correctly.

Images can change independently of URLs. Record an image-match status such as matched, changed, missing or uncertain, plus the check date. Do not use an image to infer material, authenticity, included quantity or exact colour under real lighting. If the page contains several variants, note which visible option the saved image represents. This keeps the image useful for mismatch detection without asking it to prove qualities it cannot prove.

Add completeness and confidence without fake precision

Completeness answers whether required fields are present; confidence answers how strongly the fields agree. They are not the same. A row can be complete but conflicting—for example, it contains a title, image and URL, yet the image shows a different model. Another row can be incomplete but not misleading because it openly marks a missing size chart. Use named states rather than a decorative score whose formula readers cannot inspect.

A practical completeness state is complete, usable with gaps, or hold for review. Confidence can be high when title, first image, listing type and destination agree; medium when a non-critical field is unclear; and low when identity signals conflict. Each label should have a written rule and an editor note explaining the exception. This makes prioritization possible without pretending that “92% confidence” has scientific meaning.

• Complete: all required identity and audit fields present
• Usable with gaps: identity agrees but a secondary field is missing
• Hold: identity conflict, unknown link type or stale destination
• Never publish a numeric confidence score without a disclosed method

Use a worked row audit

Imagine a row titled “navy zip hoodie.” It has record ID H-042, category Hoodies, a full-product destination, a first image that shows the same navy zip design, recorded options navy/grey and M–XL, a CNY price snapshot tied to the M option, and a last-verified date. The row also states that no measurement chart was found. That is not a perfect listing, but it is a transparent, usable record: identity signals agree and the missing fit evidence is visible.

Now change one fact: the destination redirects to a generic add-on page. The record should move to hold even if the old title, image and price remain populated. Editors should not preserve a high-confidence label from the last audit or substitute a similar hoodie without recording a new identity. The recovery sequence is exact-link check, listing-type check, image/title comparison, variant review, then a fresh date. One conflict can outweigh many filled cells because identity is the foundation.

Apply a compact pre-use checklist

Before using a row, confirm that the title describes the current destination, the category uses the shared taxonomy, the URL type is known, the first image matches, the relevant variant is identified, and price or measurement values have dates and units. Then read the missing-field and confidence notes. This takes less time than resolving a wrong item after relying on an attractive but ambiguous card.

For editors, the same checklist becomes a maintenance queue. Recheck holds first, then records with missing identity fields, then rows whose verification dates are oldest. Keep every change attributable through an internal ID and short note. A well-designed Superbuy spreadsheet index does not promise that every row is permanently correct. It shows exactly what was checked, what remains uncertain and where the current destination must make the final decision.

• Identity fields agree
• Link type is explicit
• Price and measurements include context
• Variant coverage is not overstated
• Image match has a date
• Gaps and confidence are visible