Standard DTCGuide
Standard DTC Runtime
How the optional consumer storefront is served from canonical platform truth.
On this page
Catalog count versus consumer availability
- The owner's catalog count and consumer-eligible test count can differ. Review the existing test when it is excluded; do not create a duplicate to make a storefront count increase.
- Consumer eligibility requires active, visible, available testing, configured pricing, required mapping, an eligible selected Program, and compatible effective collection methods and service areas. A basic catalog listing predicate alone does not establish orderability.
- Review exclusion reasons in Test menu and correct the authoritative Catalog, Program or Fulfillment setting. Featured/reordered selections only arrange eligible tests; they cannot expand eligibility.
- A test becoming unavailable must stop being consumer-orderable even if an earlier preview or published presentation featured it. Owner-only exclusion details are not consumer or cross-laboratory disclosures.
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 boundary
- Control Plane — owns Experience configuration, consumer deployment state, revisions, publish gating and domain intent, plus the Catalog, Fulfillment, clinical and Results authority the storefront reads.
- Consumer runtime — a separately deployed application that renders the Standard DTC Storefront and Patient Portal. It stores no catalog, pricing, clinical or result data of its own.
Tenant resolution and fail-closed behavior
The published runtime resolves the laboratory from the requested domain and serves only a published revision of a live deployment. An unknown domain, unpublished deployment or missing authority renders nothing for that laboratory rather than a substitute. The reference storefront is isolated to its own demonstration address and is never served for a laboratory domain.
Private preview versus published runtime
- Private preview — opened from Direct-to-Consumer Testing with a short-lived signed grant the platform verifies; it shows the saved draft or authorized derived configuration for one Sandbox workspace and is read-only. The platform serves the current inline and full private preview composition.
- Published runtime — serves the published revision publicly after the publish gate passes.
Catalog projection
The storefront lists only consumer-eligible tests: active, visible and available tests with a storefront address, configured price, required mapping, selected Program membership and effective collection/service-area support. Biomarkers come from the canonical test-to-biomarker relationship. Featured tests are the configured featured set intersected with the current storefront Catalog.
Clinical requirements, cart and checkout
- Ordering eligibility — self-order, provider review required or not available — is resolved by the platform per test and region; the runtime never infers it.
- One cart represents one patient, and each test appears at most once.
- Transactions are submitted only through supported platform interfaces.
Current limitations
- A Production payment-provider contract is not configured, so live consumer payment is not available.
- Each laboratory owns its consumer storefront sales, pricing, orders and its own payment processor; Solia never charges consumers or holds or splits consumer proceeds. No laboratory merchant processor is verified today, so public checkout is not available and a storefront remains a private preview.
- A canonical multi-item order transaction is not available.
- Managed DNS and TLS for laboratory domains are provisioned externally and may be pending for a given laboratory.
- Collection-site listing and provider-fee contracts are not available to the consumer runtime.
Important
These limitations are stated from the current implementation. Architecture existing for a capability does not make it live.