Randmar / Prompts

Write Shopify product pages with your own AI

Turn verified Randmar product information into a complete Shopify page draft, with copy, product fields, useful images and a review plan.

Build a product page customers can trust

Your AI assistant can turn verified product information into a clear Shopify listing. Start with one exact product from Randmar inventory, give the assistant your store context, and ask for a complete review package rather than a description alone.

Randmar community members working together at a computer in the coworking space
Learning and working together at Randmar.

Begin with a matched catalog item

Provide the Randmar SKU, manufacturer, model or MPN, barcode and exact variant. Use an authorized Randmar connection or a recent merchant-provided export. Record when the data was retrieved. Check that the identifiers agree with the manufacturer datasheet and reference photos. If they disagree, stop and resolve the identity before drafting.

Keep identifiers distinct. Randmar SKU identifies the catalog record. A Shopify SKU follows the merchant's integration mapping; it is not automatically the Randmar SKU. A barcode has its own field. Do not silently replace identifiers on an existing listing. [1, 6]

Tell the assistant who you sell to

Supply your store name, audience, language, tone, market and currency. Add approved warranty, returns and shipping policies when relevant. Explain whether the task is a new listing or an update. Give existing copy and media if you want a comparison. Access to Randmar does not by itself authorize access to Shopify or any paid generation service.

Ask for facts before persuasion

Have the assistant list supported specifications, compatibility, dimensions, included accessories and limitations with a source beside each. Product benefits should follow from those facts. Do not turn a possible use into a performance promise. Do not invent certifications, reviews, warranties or delivery dates. Shopify recommends descriptions that explain features, benefits, specifications and uses. [7]

Keep the page maintainable

Ask for a concise opening, useful benefits, scannable specifications, included items and supported answers to buyer questions. Use the store's own voice. Put volatile prices and stock in their proper commerce fields instead of hard-coding them into descriptive prose. Review the whole page on mobile before publishing.

Prepare the product presentation fields

For every proposed field, return the value, evidence, owner and action: keep, add, change, not applicable or needs input. The checklist is a review contract, not a claim that Shopify requires every field. [4]

Product title

Identify the manufacturer, product type and exact model where useful. Add only a supported distinguishing feature. Avoid a list of keywords.

Description

Supply readable plain text and an optional clean HTML version. Include the purpose, supported benefits, specifications with units, compatibility, box contents and important limitations. Avoid repeating the product title as another H1. [7, 8]

Organization

Propose the vendor, a verified Shopify standard product category, the merchant's custom product type, relevant tags and intended collections. Manufacturer, distributor and store brand may be different. Confirm the desired vendor convention. Preserve integration tags. [4, 9]

Options and variants

List only real combinations such as color, size or capacity. Give one record per sellable variant and match its identifiers and imagery. Do not create a variant from a photograph alone. [10]

Search listing

Provide a proposed URL handle, SEO title, meta description and character counts. Use a concise SEO title, normally no more than 60 characters, and a meta description around 160 characters as writing guidance. Review existing URLs before changing them. No ranking outcome is promised. [8]

Metafields

List each proposed field's purpose, namespace, key, type and value. Use existing definitions where supplied. Keep unsupported definitions as proposals. Four feature highlights can suit a theme, but they are not a Shopify requirement. [1]

Media

Return the asset manifest described in the media plan below, including order, featured image, variant association, alt text, source and approval state.

Product template and visibility

Record the intended theme template, draft or active status, channels and markets. Flag app-specific or channel-specific fields that still need checking. A finished description is not permission to publish.

HTML should fit the theme

Prefer semantic headings, paragraphs and lists. If custom styling is necessary, scope it to a unique wrapper. No scripts, tracking, embedded forms, global CSS or imitation buy buttons. Keep the theme's actual product form and variant selector intact. Test the result instead of assuming arbitrary HTML is safe.

Keep commerce data under merchant control

These fields need authoritative values or explicit merchant decisions. AI should organize and validate them, not make them up. Leave a review placeholder outside the import file when information is missing.

Identifiers

Record Randmar SKU, manufacturer MPN, Shopify product and variant IDs if existing, Shopify SKU and UPC or other barcode. Preserve leading zeros. Verify the identifier mapping used by the store integration. [1, 6]

Pricing

Record currency, selling price, compare-at price if applicable, cost per item and any unit-price information. Document the approved strategy and current inputs separately. Do not expose cost or reseller-specific terms in customer copy. A compare-at value is not proof of a lawful discount claim. [11]

Randmar pricing boundary

The inspected synchronization code uses store strategy and catalog report fields, including MSRP, MAP and opportunity discount. Report Price is assigned as inventory cost. Product-writing copy does not determine those numbers. Confirm current deployed behavior and merchant policy before applying a formula. [1]

Inventory

Record the exact variant, quantity source, retrieval time, Shopify location, tracking setting, fulfillment service and out-of-stock selling policy. Decide who owns ongoing updates. Avoid competing manual imports and automated sync. Randmar availability alone does not prove storefront sellability or a delivery date. [1, 12]

Shipping and customs

Ask whether the item requires shipping, its verified product weight and unit, shipping profile and any applicable country of origin and HS code. Distinguish product, package and shipping weights. Do not infer customs data from brand headquarters or a similar product.

Tax and selling markets

Collect the merchant-approved tax treatment, category and market eligibility. Flag jurisdiction-specific questions rather than guessing. Do not treat a category suggestion as tax advice.

Publication

For a new listing, recommend a draft for review. For an existing live product, prepare a before-and-after patch that preserves status and unrelated fields. Treat publication, inventory changes, price changes and media replacement as separate decisions.

When data is incomplete

Name the missing field, why it matters, who can provide it and whether it blocks drafting, importing or publishing. Drafting can often continue without a price; a ready-to-import file must not substitute a fabricated price or stock count.

Choose images that answer buyer questions

Use approved exact-product photography first. Add generated scenes only when the product can be preserved faithfully and usage rights are clear. Select useful views rather than filling a fixed quota. This proposed eight-brief menu is adaptable; it is not a Shopify requirement.

1 Hero

Show the exact variant cleanly, fully visible and accurately colored. Use a neutral background if appropriate. Prefer a real product photograph for the featured image.

2 Alternate angle

Show a verified side, rear or three-quarter view. Request a reference for unseen surfaces; do not invent ports, controls or markings.

3 Detail

Show a meaningful physical feature, connector, material or control. Preserve its actual shape and placement. Use a crop of a real photo when possible.

4 Size and scale

Use documented dimensions and units. Add a size comparison only when scale is verifiable. Do not use a generated person or room as measurement evidence.

5 In use

Show a realistic use supported by manufacturer guidance. Avoid unsafe operation or implied capabilities. Mark decorative props as not included where ambiguity remains.

6 Box contents

Show only verified included items. Keep optional accessories separate and clearly identified. Never imply a bundle because items look good together.

7 Feature explanation

Explain one supported feature visually with brief, legible text. Keep evidence for the claim. Avoid invented certification badges or numeric performance claims.

8 Compatibility or selection

Show verified fit, connections or real variant choices. If compatibility is not established, substitute another evidenced detail rather than creating a diagram.

Asset manifest:

filename, source or reference, rights confirmation, exact variant, purpose, proposed position, featured flag, alt text, dimensions, format, file size and approval state. Alt text should describe the visible content, not add marketing claims. [8]

Shopify specifications:

product images can be up to 5000 × 5000 pixels / 25 MP and must be under 20 MB. Shopify recommends 2048 × 2048 for square images; use a consistent featured-image ratio. Up to 250 media items are allowed, with plan-dependent video and 3D hosting limits. [2, 3]

Copy the full prompt below to prepare a reviewable product-page package in your own AI assistant. Your agent can read the full instructions on this page or the plain-text agent version.

Start the conversation

Help me prepare a complete Shopify product page using my own AI tools and verified Randmar inventory.

Read and follow this Randmar prompt:
https://randmar.io/prompts/write-shopify-product-pages

Start by establishing the exact product identity and available evidence. Prepare the full review package before any store change.

Instructions for AI agents

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.

How to use the result

Start with the worksheet and resolve the blocking questions. Approve content separately from a store write. The assistant can help prepare a package even without Shopify access; it should say which checks remain for you. This prompt does not grant credentials, API access or access to Randmar data that your account does not already permit.

Move the approved draft into Shopify safely

Choose the smallest suitable method

Manual entry. For one listing, use the field worksheet to enter approved values in the admin. Upload approved media, check its order and variant associations, then preview. Keep a new listing in draft until its release is approved.

CSV

Start from a fresh Shopify export or current sample. Preserve exact headers, identifiers and variant dependencies. Explicitly control status and online-store publication instead of relying on defaults. Product CSV quantity is for single-location stores; use the inventory workflow for multiple locations. Review overwrite behavior and back up first. CSV does not carry every kind of content; product and variant metafields have different support. [5]

API or connector

Use a supported, explicitly selected version and an authenticated merchant connection. Validate the schema, permissions, product and variant IDs, and intended field ownership. Do not assume the internal Randmar worker exposes a customer endpoint. Read mutation errors and saved values rather than treating an HTTP success as proof of completion.

Before the write

Save existing text and a media manifest. Preserve source assets. Compare the exact changes with the approval. Confirm that the product and all affected variants are the intended ones. Recheck volatile stock and pricing when they are part of the approved operation. Make sure no unknown placeholders will reach customer fields.

After the write

Re-read title, description, SEO, tags, metafields and variant mappings. Confirm the approved media actually uploaded and that alt text and ordering are correct. Check links and HTML rendering at desktop and phone widths. Inspect the featured image on the product and collection views.

Verify that price, currency, availability and channel visibility match the approved settings. Confirm no unrelated variants or location quantities changed. If an external integration owns a field, check its next ordinary update when authorized to ensure the values remain consistent. Do not promise checkout availability from an aggregate catalog quantity.

If something fails

Stop the affected step, retain the approved package and report what changed, what failed and what is unknown. Avoid blindly rerunning imports or deleting media. Use the saved baseline to propose a targeted repair. Mark the work complete only when required checks pass or the merchant accepts named outstanding checks.

Resources and further reading

  1. Randmar product-writing SOP
  2. Shopify product media types
  3. Shopify adding product media
  4. Shopify product details
  5. Shopify product CSV guidance
  6. Shopify using SKUs
  7. Shopify product descriptions
  8. Shopify SEO titles, descriptions and alt text
  9. Shopify standard product taxonomy
  10. Shopify variants
  11. Shopify product prices
  12. Shopify managing inventory quantities

Related FAQ: What Randmar’s product-writing job changes in Shopify.

Updated . Adapted from the Randmar Shopify Product Writing Guide.