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

# Shop and Dispensary Lifecycle

> Current lifecycle for saved shops, order links, Gmail readiness, editing, and deletion.

## Source of truth

The cross-feature shop lifecycle is maintained in
[Order Activation](/help/user-flows/order-upload#dispensary-lifecycle-and-gmail-readiness).
This page is a compact user-flow index.

## Current lifecycle

```mermaid theme={null}
flowchart TD
    A{Create path} -->|Full Add form| B[Name plus optional shop details and receipt domains]
    A -->|Text order| C[Choose saved shop or create name-only shop]
    A -->|Reviewed Gmail order| D[Create or link by confirmed shop]
    A -->|Gmail inline setup| E[Create or enrich with confirmed receipt domain]
    A -->|Onboarding today| F[Mock choice only]

    B --> G[Saved Convex shop]
    C --> G
    D --> G
    E --> G
    F -. Target: persist real shop .-> G

    G --> H[View detail]
    H --> I[Edit supported fields]
    H --> J[Favorite or unfavorite]
    H --> K[Open location, website, or menu]
    H --> L[View linked order history]
    H --> M[Delete shop]

    G --> N{Has emailDomains?}
    N -->|Yes| O[Quick Sync-ready]
    N -->|No| P[Needs domain]

    D --> O
    B --> O
```

## Important distinctions

* Contact email and website can suggest a receipt domain for confirmation.
* Quick Sync requires the separate `emailDomains` array.
* The main Add/Edit form directly manages normalized, deduplicated
  `emailDomains`.
* Finalizing a reviewed Gmail order attaches its validated sender domain.
* Changing a saved order's shop label detaches a stale link when the normalized
  identity genuinely changes.
* A durable post-save effect records one visit for an idempotent order save.

## Deletion impact

Deleting a shop removes that saved record. Existing orders keep their display
name and are atomically detached from the removed shop ID, so no stale detail
or order-history destination remains. Duplicate-shop merging is a target feature.

<CardGroup cols={2}>
  <Card title="Managing Shops" icon="store" href="/help/features/dispensaries">
    Field-by-field behavior and Gmail readiness.
  </Card>

  <Card title="Order Activation" icon="receipt" href="/help/user-flows/order-upload">
    Complete implemented flow.
  </Card>
</CardGroup>