> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tokensupply.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Delivery and custom domains

> How store pages and buyer delivery pages are hosted, kept isolated from the admin app, and how custom domains fit in.

Your public pages and your admin app live in different places on purpose. This page explains where buyer delivery pages are served, why they stay separate from where you sign in, and how a custom domain fits into the picture.

## Two kinds of address

There is the admin app, where you sign in to run your store, and there is your store's own web address, where the public sees your storefront and where buyers collect their keys.

<CardGroup cols={2}>
  <Card title="The admin app" icon="lock">
    Where you and your team sign in to manage everything. Buyers never go here.
  </Card>

  <Card title="Your store's address" icon="globe">
    Your storefront and buyer delivery pages. This is the only place delivery links work.
  </Card>
</CardGroup>

## Delivery pages stay isolated

A buyer's delivery page is served only on your store's own address, never on the admin app. This separation is deliberate: a private delivery link only opens where it is supposed to, and trying to use it anywhere else simply does not work.

<Steps>
  <Step title="An order is delivered">
    A private delivery link is created for the buyer at the moment of delivery.
  </Step>

  <Step title="The link points to your store's address">
    The link lives on your store's own web address, on the public store surface.
  </Step>

  <Step title="It works only there">
    The same link will not open on the admin app. It is tied to the store surface where buyer pages belong.
  </Step>
</Steps>

<Note>
  The private link is what identifies the buyer's order. There is no login on a delivery page. Whoever holds the link sees that one order, which is why the link is treated as private and shared only with the buyer.
</Note>

## Custom domains fit right in

By default your store lives on the subdomain it was given. If you own a domain already, you can add it as a custom domain and point your store at it. Your storefront and delivery pages then appear on your own domain, while keeping the same isolation from the admin app. Custom domains are on the Growth plan.

You can connect more than one domain, and each verified domain serves your store. One address is your **Primary**, and that is the one your store page uses. New delivery links are built on your primary address too, so once a custom domain is primary, buyers receive links on your own domain. Your default subdomain keeps working either way.

<CardGroup cols={2}>
  <Card title="Add a custom domain" icon="globe" href="/guides/settings/custom-domain">
    Serve your store on a domain you own.
  </Card>

  <Card title="The delivery portal" icon="globe" href="/guides/selling-fulfilment/the-delivery-portal">
    What a buyer sees when they collect keys.
  </Card>

  <Card title="Stores and multi-tenancy" icon="store" href="/how-it-works/stores-and-multi-tenancy">
    How each store gets its own address.
  </Card>

  <Card title="Security and your data" icon="shield" href="/how-it-works/security-and-data">
    Why delivery links stay private.
  </Card>
</CardGroup>