Shopify Product Listing
Own the product-record build, field mapping, copy assembly, draft creation, listing QA, and approved publication for one or more defined products.
Operating contract
- Start read-only or draft-only. Do not create, overwrite, activate, publish, archive, or delete a product without explicit authorization.
- Use an approved product source sheet or authoritative system. Never invent specifications, category, variants, identifiers, prices, costs, inventory, weight, claims, policies, or availability.
- Confirm market, currency, tax, inventory location, sales channel, template, and handle consequences.
- Preserve existing handles, links, variants, inventory, channel availability, and identifiers unless the change explicitly includes them.
- Treat product creation, save, active status, channel publication, storefront visibility, and feed acceptance as separate states.
Required inputs
Collect target store, create or update mode, product source, title, description, media, category and attributes, product type, vendor, collections, tags, metafields, options, variants, SKU, barcode or other identifiers, price, compare-at price, cost, tax, inventory, locations, shipping, weight, purchase options, template, SEO fields, status, channels, markets, claims, policies, approver, and rollback.
Workflow
- Build a source-to-field map and flag missing or conflicting inputs.
- Check for duplicate products, handles, SKUs, barcodes, media, and variants.
- Draft truthful customer-facing content without changing approved facts.
- Map taxonomy, attributes, organization, variants, pricing, inventory, shipping, SEO, template, and publication settings.
- Create or update only the authorized state, preferably draft before active publication.
- Reopen the saved record and compare each decision-critical field with the source.
- After approved publication, verify the correct channels, markets, product page, variants, price, availability, structured output, and feed state where in scope.
Read references/listing-fields.md for the field contract. Use references/qa-checklist.md before save, activation, publication, and handoff.
Worked example
Read references/worked-example.md for a complete synthetic case, supplied inputs, expected outcome, and acceptance checks. Treat its facts and thresholds as example-specific, not merchant evidence or default policy.
Output contract
Provide the field map, evidence gaps, listing draft or exact changes, source for each claim and commercial field, state transition, QA result, exceptions, authorization, rollback, and saved or live verification. Do not call a listing complete when required fields, channels, or variants remain unverified.
1---2name: shopify-product-listing3description: Creates, updates, and quality-checks Shopify product listings from approved product data. Use for titles, media, taxonomy, variants, pricing, inventory, SEO, and publishing.4license: MIT5---67# Shopify Product Listing89Own the product-record build, field mapping, copy assembly, draft creation, listing QA, and approved publication for one or more defined products.1011## Operating contract1213- Start read-only or draft-only. Do not create, overwrite, activate, publish, archive, or delete a product without explicit authorization.14- Use an approved product source sheet or authoritative system. Never invent specifications, category, variants, identifiers, prices, costs, inventory, weight, claims, policies, or availability.15- Confirm market, currency, tax, inventory location, sales channel, template, and handle consequences.16- Preserve existing handles, links, variants, inventory, channel availability, and identifiers unless the change explicitly includes them.17- Treat product creation, save, active status, channel publication, storefront visibility, and feed acceptance as separate states.1819## Required inputs2021Collect target store, create or update mode, product source, title, description, media, category and attributes, product type, vendor, collections, tags, metafields, options, variants, SKU, barcode or other identifiers, price, compare-at price, cost, tax, inventory, locations, shipping, weight, purchase options, template, SEO fields, status, channels, markets, claims, policies, approver, and rollback.2223## Workflow24251. Build a source-to-field map and flag missing or conflicting inputs.262. Check for duplicate products, handles, SKUs, barcodes, media, and variants.273. Draft truthful customer-facing content without changing approved facts.284. Map taxonomy, attributes, organization, variants, pricing, inventory, shipping, SEO, template, and publication settings.295. Create or update only the authorized state, preferably draft before active publication.306. Reopen the saved record and compare each decision-critical field with the source.317. After approved publication, verify the correct channels, markets, product page, variants, price, availability, structured output, and feed state where in scope.3233Read [references/listing-fields.md](references/listing-fields.md) for the field contract. Use [references/qa-checklist.md](references/qa-checklist.md) before save, activation, publication, and handoff.3435## Worked example3637Read [references/worked-example.md](references/worked-example.md) for a complete synthetic case, supplied inputs, expected outcome, and acceptance checks. Treat its facts and thresholds as example-specific, not merchant evidence or default policy.3839## Output contract4041Provide the field map, evidence gaps, listing draft or exact changes, source for each claim and commercial field, state transition, QA result, exceptions, authorization, rollback, and saved or live verification. Do not call a listing complete when required fields, channels, or variants remain unverified.
vinceservidad