The right detail. The wrong sibling.
Match facts to explicit SKU references. A shared family name is not enough.
Product-family repair
Similar products. Different details.
Get your catalog and supplier files to agree, one variant at a time.
Review first. $299 to export.
One family, up to 25 SKUs. No subscription.
A source for the change.
A decision for the doubt.
360 mm
240 mm
The wider sibling’s dimension was copied into this variant.
Illustrative data · three separate product records · not a customer result.
The family resemblance is the problem.
A width from the next size up. A shipping weight in the product field. A finish that changed between two documents.
Small errors travel through a catalog quickly. Specstead compares the facts for each exact SKU and keeps the evidence beside the proposed repair.
Match facts to explicit SKU references. A shared family name is not enough.
Distinguish product measurements from packaging, units from quantities, and blank fields from facts.
See both statements and choose what to keep. Unresolved information stays visible.
One family. A finished job.
Upload your current catalog CSV and up to five supplier files. See whether the fields and files fit before analysis.
Compare the current value, proposed value and exact source. Choose between conflicting statements or keep the field unchanged.
Pay once for the reviewed export and its evidence. Follow the import instructions, then upload a fresh export for a recheck.
Self-serve from the first file to the final check. No call to book.
The work leaves with you.
Keep the changes, their sources, and the decisions you made. You control the import into your store.
An export for the supported fields you approved.
A record of each proposed change and its source.
Unsupported or skipped facts stay in the handoff.
Compare a fresh export with the approved repairs.
A useful boundary
AI helps read and compare your supplied files. Evidence checks constrain what becomes a proposed repair. You decide where the sources disagree.
Specstead does not log into your store or publish changes. The post-import check compares your exported data; it does not certify your whole storefront.
Before the first file
A bounded group of related products or variants with explicit SKU identifiers. A family may share some features while differing in size, finish, weight or other attributes. The first offer supports up to 25 distinct SKUs in one submitted batch.
Bring a current Shopify-style product CSV and supplier information as text-based PDF, TXT, CSV or XLSX. The workspace checks exact limits and supported fields. Scanned PDFs without readable text need a text version before they can be compared.
You need identifiable SKUs, readable source files and an existing supported field to repair. Preflight checks the structure. During review, facts without sufficient support stay unresolved rather than being filled in.
When sources conflict, you see the alternatives and their evidence. You can choose a supported value or keep the current value. There is no silent tie-break based only on which document looks newer.
No. You review and purchase an export, then control the import. Keep a fresh backup and follow the supplied import instructions. Upload an export after import to compare the supported fields again.
It is a one-time purchase for one bounded repair. It does not continuously synchronize suppliers, manage inventory, or replace a product information management system.
Start with the actual problem
Small examples make the limits visible before you bring your own files.
The details are worth getting right.
Start with the catalog you already have.