# Preparing Territory Stores, pages, brands and domains

Availability: Planned API.
Last reviewed: 2026-08-28.

Prepare a market-specific commerce experience with an exact, reviewable revision. The planned Territory Store outcome connects territory, audience, assortment, brand, pages and domain decisions.

## Assemble the inputs

Choose an owned territory and Store identity, intended audience, conversion journey, catalog/assortment revision, approved brand assets and page content. Default and secondary/ICP Stores remain distinct identities.

Archetypes have different prerequisites. A lead-generation or service-request Store should not inherit every cart, payment and shipping requirement of a physical-goods checkout.

## Review the exact preview

Retain immutable revisions and the precise preview identity. A private preview may truthfully be a draft. Its text, product/media references, navigation and readiness issues should match the saved revision.

For example, a product image can be hosted yet not approved for a Store; the preview must not hide that distinction or substitute unreviewed media.

## Treat launch as a separate decision

Domain research and selection do not purchase a domain or change DNS. Brand discovery does not grant asset rights. Preview acceptance does not authorize public publication, transactions or a provider deployment.

## Availability

Business APIs are planned. Launch needs its own evidence and approval for the selected archetype. [Commerce channels and fulfillment](/docs/guides/commerce-channels) covers the downstream sale and delivery contract, not a prerequisite automatically satisfied by preview generation.