⌘K

Integration GuidesGuide

Standard DTC preview & publish

Optional consumer configuration, first-visit private preview, saved revisions, publish gating and current limitations.

On this page

First visit, customization and optional launch

  • Open Programs → Direct-to-Consumer Testing in Sandbox to see the laboratory's own private storefront. Opening the page does not create a Program, save a deployment, advance onboarding or publish anything.
  • Before a saved draft exists, the preview derives the laboratory identity and permitted configuration from the current workspace. After customization is saved, preview uses the exact current draft revision. A laboratory with no logo uses its own name rather than the Solia demonstration logo.
  • Use Appearance, Test menu and Launch for everyday tasks. Advanced settings retain domains, navigation, search and portal options. Desktop/mobile preview controls change the preview viewport, not fulfillment eligibility.
  • Unsaved appearance edits are shown in the editor preview and remain distinct from saved changes. Full private preview uses the authorized saved or derived configuration; save intended customizations before reviewing that shared state.
  • A public reference example illustrates the template only. Private previews must retain the selected laboratory's identity and configuration. A lab can finish onboarding and operate other Programs without launching DTC.

Inherited branding and website suggestions

  • Use the laboratory profile and workspace brand as defaults. Deliberately saved storefront overrides take precedence; an inherited field continues to follow its shared source until overridden.
  • A supplied website can produce logo, color and typography suggestions. Review the proposed changes, accept selected settings or keep the current appearance. Unsupported fonts use a supported preset; inaccessible combinations need review.
  • Accepting website branding currently saves storefront-specific overrides. It does not automatically replace shared organization branding, patient communications or other Programs. Reset an override to restore inheritance.
  • Visual suggestions do not import test prices, availability, service areas, clinical claims or consent. Catalog and Fulfillment remain authoritative. Logo-file upload is unavailable where approved asset storage has not been configured.

Revision and capability checks

  • Publishing is an explicit action against the reviewed current revision. A stale revision or changed readiness requires a fresh review; a successful save or button click alone is not a publication receipt.
  • Confirm publication through authoritative readback. Production activation, storefront publication, payment capability and patient access are separate states. None is inferred from the others.
  • Live checkout and native DTC patient sessions remain unavailable until their separate contracts are implemented and verified. A private preview does not submit orders, charge a card or expose patient records.

Ownership

  • Experience owns presentation and deployment configuration only.
  • Catalog, Fulfillment, clinical eligibility and Results remain canonical; the storefront reads them and cannot override them.
  • The published storefront and Patient Portal presentation belong to the consumer runtime. Current inline and full private previews are platform-owned and share the same storefront composition.

Private preview

Preview opens the exact current draft revision when saved, or the authorized derived configuration before a deployment exists, for one Sandbox workspace through a short-lived signed grant verified by the platform. It is read-only and fails closed on an invalid, expired or mismatched grant. Viewing the preview creates no deployment or Program.

Publish gate

Publishing promotes a revision to the published revision and is gated server-side by laboratory Production activation, the commercial plan and publish readiness. Activating the laboratory does not publish a storefront.

Current limitations

  • Real-laboratory patient sign-in and sessions are not yet available.
  • No Production payment-provider contract, so live consumer payment is unavailable.
  • No canonical multi-item order transaction.
  • No patient order history, results trends or governed report download in the Standard DTC Patient Portal.
  • Canonical consumer kit activation is not live; no operational Activate Kit flow is documented.
  • Managed DNS and TLS are provisioned externally and may be pending.
  • Collection-site listing and provider-fee contracts are not available to the consumer runtime.

Limitation

Limitations are stated from the current implementation.

Related resources