Platform Overview

Sophosic has two primary operator-facing products:

• The console app is the authenticated control plane for workspace owners and teams.
• The sites app is the tenant-branded customer experience for browsing, booking, buying, reading, and self-service.

The relationship is simple: configure in console, experience on sites.

Console Responsibilities

The console is where a workspace team manages:

• Workspace profile, business hours, address, timezone, currency, and site status.
• Team access, selected workspace context, and admin authentication.
• Branding, theme, logo, navigation, footer, pages, and media.
• Products, collections, variants, modifiers, inventory, orders, invoices, payments, revenue, and shipping.
• Services, tiers, add-ons, waivers, staff, availability, bookings, deposits, invoices, calendar sync, and lifecycle status.
• Customers, consent documents, communications history, inbox events, forms, and support work.
• Integrations such as Stripe Connect, GA4, Google Ads, Google Business Profile, calendars, domain/email, and shipping providers.
• Growth surfaces such as Stories, Discovery, reviews, short links, SEO, GEO, and email campaigns.

Sites Responsibilities

The sites app renders:

• Public homepage and custom pages.
• Shop, product detail, cart, checkout, coupons, payment returns, saved items, and order tracking.
• Booking service list, service detail, scheduler, add-ons, waivers, deposits, confirmations, pay links, and rescheduling.
• Forms, contact, help trees, knowledge base, stories, policies, reviews, search, and intake.
• Customer account portal for profile, notifications, orders, billing, tickets, saved items, and booking history.
• Public technical routes such as sitemap, robots, llms.txt, Open Graph images, IndexNow, and domain verification.

How Data Moves

Most operator changes are saved in console service methods, then read by sites through tenant-scoped loaders, APIs, cache tags, or webhook invalidation. The practical result:

1. Console stores the canonical workspace configuration.
2. Sites resolves the public tenant from host or path.
3. Sites renders the customer experience from the resolved workspace.
4. Webhooks and revalidation keep public content fresh after console changes.

Workspace Model

Console URLs are workspace-cookie based. The active workspace is selected once, then admin paths stay flat.

Sites URLs are tenant scoped. Local development usually uses a path like /{site-slug}/shop; production usually uses a workspace domain or subdomain.

This model prevents operators from copying public URLs into console diagnostics without checking tenant context. For console issues, record the selected workspace and operator account. For sites issues, record the host, path, resolved workspace, customer session state, and whether the site is published or protected.

Operator Mental Model

Next Steps

Choose the next guide based on the state of the workspace, not the reader’s role. A brand-new workspace should start with setup, an incomplete public site should move to publishing, and an already-live workspace with a specific failure should jump directly to the relevant workflow or troubleshooting path.

• Operator Quickstart
• Workflow Map
• Product Areas Overview
• Launch Checklist