Commerce OS guide

Set Up Liva 7 Safely

Guide status: Setup guidance. Last reviewed 14 August 2026. Installed labels, permissions and Shopify theme steps must be checked against the current application before this guide is published.

Purpose

This guide provides a safe order for bringing Liva 7 into a Shopify store: connect, verify, place, observe and expand. It prevents a saved configuration from being mistaken for a live or measured experience and gives the team clear points at which to stop if a prerequisite is missing.

Prepare

  • Identify the store owner and the people responsible for Shopify administration, merchandising, privacy and measurement.
  • Record the store, active theme, markets and initial commercial objective.
  • Agree which data and storefront surfaces are in scope.
  • Begin with the lowest permissions and authority level that support the initial use.
  • Plan an approved default experience before enabling adaptive behaviour.

Safe setup sequence

  1. Connect: complete the current Shopify installation or connection flow and review requested access.
  2. Verify sources: check connection, freshness, coverage and eligibility states. Unknown values should remain unknown.
  3. Review the operating brief: inspect Home and Store Intelligence before acting on opportunities.
  4. Prepare one bounded use case: choose a reversible placement or workflow with clear ownership and measurement.
  5. Configure the storefront: add the required app block, embed or placement to the intended theme and template using Shopify's current controls.
  6. Verify live behaviour: test the correct market, customer state, device widths, fallback and purchase path.
  7. Observe: allow valid exposure and measurement data to accumulate.
  8. Expand deliberately: add further use cases or authority only after the first operating loop is understood.

State checks

At every step distinguish prepared, configured, published, verified, exposed and measured. If a state cannot be verified, stop at the last known safe state. Do not compensate for an unavailable source by inventing data or widening access without a specific need.

Authority during setup

Use Observe while confirming sources and Store Health. Use Recommend while the team learns how Liva 7 frames decisions. Introduce Ask First for a well-defined action only after approval ownership and fallback are clear. Auto-execute should be a later, domain-specific policy decision, not a default installation choice.

Safe fallback

If setup is incomplete, the Shopify storefront should continue to provide a coherent default experience. Avoid making the customer's ability to browse or buy depend on an unverified Liva 7 placement. Keep credentials and access tokens out of documentation and support messages.

You are finished when

  • the correct store and expected sources are verified;
  • one bounded use case is published and checked on the live storefront;
  • fallback, measurement and authority are documented; and
  • the team knows how to pause, investigate and request support.