Catalogue Check Desk

Pre-import review · Original demonstration · 7 October 2026

Fictional product data. This demonstrates a report format; it is not a customer order, an import-ready file, or a full Shopify schema validation.

Four rows reviewed; three findings

Checks agreed for this example: unique SKU, plain decimal prices, and changes to vendor against the prior export. Repeated product handles may be valid variant rows.

Input excerpt

rowskuhandletitlepricevendor
2MUG-001stone-mugStoneware mug12.00Demo Studio
3MUG-001stone-mugStoneware mug12.00Demo Studio
4BOWL-002blue-bowlBlue bowltwelve
5PLATE-003small-plateSmall plate8.50Demo Studio

Findings and decisions

RowSeverityFieldEvidenceNext action
3reviewskuSKU also occurs on row 2; determine duplicate versus intentional reuse.Confirm intended variant identity; do not delete automatically.
4errorpriceNot a plain non-negative decimal price: 'twelve'Obtain the correct price from the source; do not infer it.
4reviewvendorPreviously populated vendor is now blank.Confirm intent; included blank fields can overwrite saved values during an update.

Before importing

Resolve the duplicate SKU, confirm the actual bowl price and decide whether its vendor should be cleared. The previous bowl vendor was Demo Studio. Preserve an untouched export and inspect the import preview. No rows were deleted, missing values invented, or live store data modified.

Shopify official import guidance explains how included blank fields can overwrite stored data.

£29 proposed review: up to 100 rows, an issue report and one in-scope revision. Availability and due date must be confirmed before an order. Business is currently pre-launch; this sample has no live ordering or payment facility.