Understand offline checkout safety | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/ecommerce-pos-understand-offline-checkout-safety Publisher: Pixie Technologies LLC SEO, sitemaps, PWA and public routes Understand offline checkout safety Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. This guide explains that an offline browser cannot commit an order. Audience: Store administrators, SEO teams and developers; Permission: Public access when store enabled; Manage settings/catalogue for content; Module v1.0.0 · code-inspected; Where to go/shop and public route endpoints What this guide helps you do Know an offline browser cannot commit an order. This section documents canonical URLs, metadata, XML sitemaps, web app manifest, service worker and offline fallback. Follow these steps - Go to /shop and public route endpoints and open the workflow that matches “Understand offline checkout safety”. Confirm the page or record context before making a change. - Set store/category/product SEO fields. - Go to canonical shop, category and product URLs. - Check title, description, canonical and structured data. - Go to the sitemap index and child sitemaps. - Check manifest and service worker over HTTPS. - Test the offline fallback without allowing checkout to appear successful offline. Fields and options - Guide focus: Know an offline browser cannot commit an order. - Store, category and product metadata - Canonical links - Robots noindex controls - Sitemap index/categories/products pages - manifest.webmanifest - service-worker.js - /shop/offline Rules and limits - Search-result pages use noindex,follow. - Product seo_noindex can prevent product indexing. - Product sitemap pages are segmented by numeric page. - The service worker is scoped to the shop and provides an offline-safe page. - Checkout/order commits require live server validation; offline mode does not create orders. Check it worked - The specific outcome described by this guide is visible and remains tenant-scoped. - Search engines can discover eligible canonical catalogue URLs. - Installable PWA metadata is served from the tenant store. - Offline browsing fails safely without pretending to submit commerce transactions. Safety checks and troubleshooting - Keep only public-safe metadata in pages/sitemaps. - Test canonical host/protocol in production. - Do not cache personalised checkout/order/API responses. Stay within the supported module flow Use the supplied UI, host module lifecycle and documented endpoints. Do not bypass tenant filters, permissions, CSRF, idempotency, rate limits, audit evidence or transaction checks. A stored table or field does not imply that version 1.0.0 exposes a management screen for it. Related guides eCommerce & POS Module overview (https://pixiecrm.com/help-centre/ecommerce-pos-module-overview)Understand service-worker scope and caching (https://pixiecrm.com/help-centre/ecommerce-pos-understand-service-worker-scope-and-caching)Open the offline fallback page (https://pixiecrm.com/help-centre/ecommerce-pos-open-the-offline-fallback-page)Understand public security headers (https://pixiecrm.com/help-centre/ecommerce-pos-understand-public-security-headers)Troubleshoot PWA installation (https://pixiecrm.com/help-centre/ecommerce-pos-troubleshoot-pwa-installation)Create a signed POS webhook (https://pixiecrm.com/help-centre/ecommerce-pos-create-a-signed-pos-webhook)Understand the POS controller architecture (https://pixiecrm.com/help-centre/ecommerce-pos-understand-the-pos-controller-architecture)Browse the connected SEO, sitemaps, PWA and public routes topic (https://pixiecrm.com/help-centre/topic/ecommerce-pos-seo-pwa)Browse all eCommerce & POS Module guides (https://pixiecrm.com/help-centre/category/ecommerce-pos)Open the related Help Centre category (https://pixiecrm.com/help-centre/category/system-customisation)