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

# Introduction

> Layout Mobile gives local and multi-location coffee shops a branded mobile app built on Square — with mobile ordering, loyalty, gift cards, push notifications, and kitchen display.

<CardGroup cols={2}>
  <Card title="For coffee shop owners" icon="store" href="/overview">
    A branded app for your locations, menu, and loyalty — without rebuilding your stack.
  </Card>

  <Card title="For technical teams" icon="shield-check" href="/architecture/overview">
    Architecture, integrations, and operations built for reliability and security.
  </Card>
</CardGroup>

## What is Layout Mobile?

Layout Mobile is a **white-label mobile ordering platform** for local and multi-location merchants who already run on **Square**. You keep your existing point-of-sale and kitchen display; we add a customer-facing iOS app that stays in sync with your catalog, locations, loyalty, and payments.

* **Branded experience** — Your name, logo, and colors in a native iOS app published to the App Store under your brand.
* **Square-native** — Connect once via Square OAuth; catalog, locations, payments, and loyalty flow through your existing Square account.
* **Multi-location** — One app, all locations. Customers choose a store; orders and status remain location-aware.
* **Kitchen-ready** — Works with Layout KDS, Square KDS, or Square Expeditor. Orders appear where your team already works.
* **Loyalty, gift cards & promotions** — Surface Square Loyalty balance and enrollment, sell and reload Square gift cards, and run in-app promotions and welcome offers directly from the app.
* **Push notifications & announcements** — Send unlimited push notifications and in-app announcement cards to keep customers engaged.

This documentation is for **owners**, **technical evaluators**, and **partners** who want a clear picture of how the system works, how it integrates with Square, and how we think about reliability and security.

## Who this is for

| Audience                              | What you'll find here                                                                                    |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| **Multi-location coffee shop owners** | How Layout fits with Square, what each plan includes, and how locations and branding work.               |
| **Technical evaluators**              | High-level architecture, integration flow, reliability and security principles, and multi-tenant design. |
| **Investors & partners**              | Platform scope, integration strategy, pricing model, and how we position reliability and security.       |

## What you get

* **Customer app** — Branded iOS app: menu, locations, cart, checkout (Square), loyalty, gift cards, promotions, order status, and push notifications.
* **Merchant dashboard** — Branding, Square connection, locations (synced from Square), order settings, loyalty config, promotions, analytics, and featured items.
* **Kitchen panel** — Location-based order display and status flow (accepted → making → ready → completed), with support for Layout KDS, Square KDS, and Square Expeditor.

Payments and catalog stay in Square; Layout orchestrates the app experience, order flow, engagement features, and kitchen display so everything stays consistent across locations.

## Next steps

<CardGroup cols={2}>
  <Card title="Overview" icon="book-open" href="/overview">
    Product scope, key concepts, and how the pieces fit together.
  </Card>

  <Card title="Pricing" icon="tag" href="/pricing">
    Starter, Pro, and Plus plans with per-feature breakdown.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/getting-started/quickstart">
    How merchants get started: connect Square, configure the app, and go live.
  </Card>

  <Card title="Square integration" icon="plug" href="/integrations/square">
    What we sync, how OAuth works, and how webhooks stay in sync.
  </Card>
</CardGroup>