Choose a useful storefront scope.
Start with questions supported by stable public material: how a service works, product care, size guidance, contact routes, or a published returns policy. Review the specific conditions, regions, and dates in those sources.
Do not rely on indexed text as live inventory or an authenticated order lookup. A shopper asking about their own purchase should be directed to your established account or support process.
Prepare a controlled theme change.
Shopify’s code editor is available through Online Store → Themes and the theme’s Edit code action. Its documentation recommends making a backup and limits editing of paid trial themes until purchase.
Have the person maintaining your theme choose the appropriate shared storefront insertion point. In a theme using the standard shared layout, that is commonly near the closing body tag in layout/theme.liquid. Preserve existing Liquid and app code.
Source references
Use the assistant for this store.
Add the public store origin to Sairo, verify ownership, and review the crawl. Copy the generated site-specific installation snippet into the chosen theme location.
Keep the installation out of code-display content or product descriptions. Document the modification so a later theme replacement can deliberately retain or remove it.
<script src="https://sairo.app/widget.js" data-site="YOUR_PUBLIC_SITE_KEY" async></script>Test policies and products carefully.
Use the published storefront to check placement on the homepage, a product page, and a policy page. Test the actual mobile layout with the cart drawer, sticky purchase controls, and consent interface.
Ask about a condition whose answer is present in the indexed source, then ask for an order-specific fact that is not available. The assistant should not invent an order status, a stock count, or an exception to a published policy.
Example review pair
Compare “Where can I read your return conditions?” with “Has my return been approved?” The first can be grounded in public information. The second requires your actual customer-service process.
Plan for content and theme changes.
Refresh and review knowledge after important policy changes. Check saved answers too: changing the public page does not automatically rewrite a separately maintained approved answer.
A script in the storefront theme should not be assumed to appear in every checkout or customer-account surface. Test only the locations where it is actually installed, and confirm any wider integration requirement before promising it.
Common questions
Can Sairo look up a customer’s order?
The standard website embed does not authenticate customers or connect to Shopify order APIs. It uses the website knowledge configured in Sairo.
Is there a Sairo Shopify app required for these steps?
These steps describe a theme-script installation. They do not require or claim a native Sairo app in the Shopify app store.