Commerce OS guide

Smart Content

Guide status: Operating-system guidance. Last reviewed 14 August 2026. Available content types, audience controls and publication routes must be verified in the installed version.

Purpose

Smart Content prepares adaptive storefront content using store and audience context while preserving brand, evidence and merchant control. Its role in the operating system is broader than writing: it connects the reason for a message, the people or context for which it is appropriate, the placement where it may appear, the fallback experience and the result that will be observed.

Personalisation should improve relevance without pretending to know more about a customer than the evidence supports. Content must remain accurate, accessible and useful when no personalised decision can be made.

Before you begin

  • Define the customer or commercial question the content is intended to address.
  • Confirm the permitted data, consent state and audience eligibility.
  • Identify the placement, market, language and fallback content.
  • Record brand, legal, promotional and accessibility requirements.

Build the content contract

Every adaptive content item should have a reason, scope and stopping condition. State the evidence that supports the content, the audience or context rule, the message, the intended placement, and what customers see when the rule cannot be evaluated.

Separate observed behaviour from inferred interest. An audience label is an operating classification, not a statement about identity or motivation. Avoid sensitive inferences and claims that cannot be substantiated.

Prepare and review

  1. Frame: state the problem and the intended customer benefit.
  2. Draft: create concise content that remains truthful in its actual placement.
  3. Apply rules: define eligible contexts and exclusions.
  4. Set fallback: retain approved default content for unknown, ineligible or unavailable states.
  5. Review: check brand, accuracy, links, accessibility, privacy and mobile presentation.
  6. Approve and publish: follow the current authority and Shopify publication flow.
  7. Verify and learn: check the live state, then measure using an appropriate evidence standard.

Safe use and fallback

Default content is part of the product, not an error message. It should be complete enough to stand on its own. If audience eligibility, content data or the decision service is unavailable, show the approved fallback without exposing internal states to the customer.

Never allow generated or adaptive text to invent price, availability, urgency, savings, reviews or product claims. Any unsupported field should be removed, left unknown internally or replaced with approved factual content.

You are finished when

  • the evidence, eligible context and customer benefit are explicit;
  • the content and fallback have passed merchant review;
  • the live placement is verified across relevant devices and states; and
  • measurement does not overstate what the design can prove.