Help me prepare a complete Shopify product page using my own AI tools and verified Randmar inventory. Work on one exact product and its real variants at a time. Produce a reviewable draft. Do not publish, modify my store, replace media, spend money or transmit private supplier data to another service without the required approval. My inputs Randmar SKU: [ ]. Manufacturer and MPN: [ ]. Barcode: [ ]. Exact variant or variants: [ ]. Authorized catalog export or connection: [ ]. Manufacturer sources and approved photos: [ ]. Store name and audience: [ ]. Language, tone, market and currency: [ ]. Existing product URL or IDs: [ ]. New listing or update: [ ]. Approved policies: [ ]. Desired output: admin-entry worksheet, HTML, CSV proposal or API handoff [ ]. 1 Establish identity and evidence State which sources and tools you can access. Match the exact product using identifiers, not a similar name. Create a fact sheet with a source and retrieval date for each material claim. Separate verified facts, merchant decisions and unknowns. Resolve conflicting identifiers before writing. Use Randmar data for the catalog relationship and manufacturer evidence for product claims. Keep customer-specific prices, cost and private account data out of public content. 2 Draft the customer content Write the title, a clear description, supported benefits, specifications, compatibility, included items and useful buyer questions. Match my store voice. Use original wording without changing the facts. Do not invent reviews, ratings, certifications, medical claims, warranty terms or shipping promises. Include only enough detail to answer real questions; do not pad the page to satisfy a word count. 3 Return a complete field worksheet Include presentation, organization, identifiers, variants, SEO, metafields, media, pricing, inventory, shipping, tax and visibility. For each field show: current value when available, proposed value, source, confidence or unresolved question, owner and requested action. Distinguish product-level from variant-level values. Keep unknowns in a separate questions list, never as guessed import values. 4 Keep changing data separate Use the approved integration for ongoing stock and prices. Do not put transient quantities or discounts into descriptive copy. Identify which system owns each commerce field and whether a later sync could overwrite my change. Preserve existing identifiers, integration tags, locations, fulfillment settings and unrelated fields unless I approve a specific change. 5 Plan and inspect the media Propose only the useful views for this product: hero, alternate angle, detail, scale, in use, box contents, feature explanation and compatibility or selection. Fewer views are acceptable when evidence is limited. Explain why each view helps and what exact reference it needs. Prefer real photos for product identity. Do not infer unseen surfaces or make up accessories, variants, labels or measurements. Before any generation, show the proposed prompt, references, intended service and any costs or data sharing requiring approval. After generation, compare every asset with the references for geometry, branding, controls, text, color, proportions, included parts and scale. Reject uncertain assets. Supply the asset manifest and factual alt text. Preserve existing originals unless replacement is specifically approved. 6 Prepare the chosen delivery format For manual entry, group values by their Shopify destination. For HTML, provide semantic, theme-safe markup without scripts or global styling. For a CSV or API handoff, inspect the current Shopify template or selected API version and preserve variant dependencies. Use a minimal proposed change set for existing products. Do not claim the result is import-ready until actual required values and mappings have been validated. 7 Present the review package Return these sections in order: (A) identity and evidence sheet; (B) customer-facing copy; (C) complete field worksheet; (D) variant mapping; (E) image briefs and asset manifest; (F) proposed import or entry plan; (G) missing inputs and conflicts; (H) exact changes needing approval. Include a claim-to-source check. Give character counts for SEO text. Show any before-and-after comparison and identify overwrite risks. 8 Wait and verify Ask me to approve the exact changes. After an authorized update, read the saved fields back and compare them with the approved values. Inspect desktop and mobile presentation, media, variant selection and visibility. Check commerce data only within the approved scope. Report failed or unverified items honestly. Do not run a live purchase to test the page without separate permission.