Repair incomplete store product information

Why use this

1. A merchant may find products missing descriptions, image alternatives or prices but need different evidence to repair each field. Filling every blank automatically can introduce unsupported features, misleading image text or an invented selling price.

2. This job could produce a field-level correction queue with the source and approval need attached. Treating descriptive edits differently from commercial values helps the owner complete the catalogue while preserving control over customer-facing claims and pricing.

Why an agent / simpler alternative

Useful judgment

Identify missing fields, derive bounded descriptions from verified facts and distinguish values that require merchant decisions.

Simpler alternative

Use a bulk editor when authoritative replacement values already exist for every selected field.

Unsuitable when

The workflow would guess prices, invent product claims or update live listings without approved scope.

Proposed inputs

1. Name

   Product extract

   Owner

   Merchant

   Minimum scope

   Selected product/variant IDs and missing fields

   Quality check

   Check live/draft status and existing content

2. Name

   Approved product evidence

   Owner

   Owner

   Minimum scope

   Specifications, actual images and authoritative price values

   Quality check

   Match evidence to the exact variant

Access and setup — proposed or unknown

Proposed minimum

1. Read supplied copies and draft corrections; no store connection, price change or live publishing.

Compatibility unknowns

1. Current catalogue schema, field permissions, bulk-update behavior and runtime compatibility are unknown.

External actions requiring approval

1. Live record updates, pricing changes, image uploads and external sharing require explicit authorization.

Expected deliverable and review checks

Proposed artifact

Correction proposal with product ID, field, old/new value, evidence and unresolved merchant questions.

Critical checks

1. Preserve correct existing fields; keep alt text tied to visible content; never invent absent prices or unsupported specifications.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   Evidence describes another variant

   Why it matters

   A complete record becomes factually wrong

   Proposed response

   Verify variant identity or hold the correction.

2. Signal

   A blank price is treated as zero

   Why it matters

   The repair creates an unintended offer

   Proposed response

   Leave it unresolved and request the authoritative value.

Effort and cost — unknown

Setup work

1. Define eligible fields and authoritative evidence sources.

Ongoing review

1. Merchant reviews claims, prices and any approved update results.

Unknowns

1. Source quality, catalogue volume, validation rules and service costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent three product rows with a missing description, missing image text and missing price; provide evidence for only the first two.

Acceptance checks

1. Draft supported fields; keep price unresolved; retain variant IDs; write nothing live.

Stop conditions

1. Stop if a commercial or factual value lacks evidence or update approval.

Limits

1. More complete records cannot establish product accuracy, accessibility or the correctness of a selling price without review.