Open examples · No account needed

Inspect the decision.

Three small product families. Three different outcomes. Download the files and see what a considered repair should preserve, change, or leave unresolved.

All products and records below are fictional. Expected results are checked against Specstead’s deterministic reconciliation engine using manually supplied observations. They are not customer results or measurements of AI extraction accuracy.

One shared fact, supported for both variants.

A product material can change when exact-item records support the same replacement for every supplied sibling.

Expected review: One shared material proposal: Steel → Aluminum. Accepting it changes the populated product field; sibling blank cells remain blank. SKU, options, price and status stay unchanged.

Read the decision guide →

Two sources disagree about the same item.

Two exact-SKU material statements remain alternatives. There is no automatic winner.

Expected review: One unresolved material change with Oak and Maple as alternatives. A customer must choose a supported option or keep Pine; the system does not resolve it by file order.

Read the decision guide →

A variant fact does not belong in a shared field.

Different sibling widths cannot safely become one product-level specification.

Expected review: Hold the shared width field. Keep the original snapshot unchanged. Native Shopify product CSV cannot import variant metafields; use an appropriate variant-level workflow after confirming the facts.

Read the decision guide →

Check your actual task.

The examples illustrate review rules. Your own file needs a separate eligibility check, and your source records must support the proposed changes.

Check the fit first Agent workflow