18 · Customers CRM & storefront

How customers sit in the platform

flowchart TB
  CRM[(Customers · tenant main)]
  POS[POS cart · customerId]
  LOY[LoyaltyAccount]
  GC[Gift card optional customerId]
  TIX[Service tickets · portal]
  SF[Storefront order]
  AP[Appointments]
  INV[Invoices]

  CRM --> POS
  CRM --> LOY
  CRM --> GC
  CRM --> TIX
  CRM --> AP
  POS --> INV
  SF --> POS
  SF -.->|optional login| CRM
          

Same person can be staff-CRM customer, loyalty member, ticket requester, and storefront shopper — linkage quality depends on email/phone match and whether POS attaches them at sale time.

Staff CRM

API — /api/customers

Session + tenantResolver. Direct SQL multi-tenant.

Record shape (core)

orgId, name, email, phone, notes, metadata/address — table Customers on tenant main DB.

Also: /api/simple simple-customers (search/list) — lighter path used in some tools.

Customer-facing accounts

API — mounted at /customer

Customer analytics

/api/customer-analytics (session + tenant)

• GET /:customerId — detail analytics
• GET /insights/overview · segments · products

Feeds marketing-style insights; separate from sales reports main DB path (see analytics gaps in audit).

Storefront (online store)

Config (tenant)

Table-ish storefront_settings via /api/storefront:

• enabled, storeName/description, colors, logo, custom CSS/JS
• productsPerPage, currency, taxIncluded, shippingEnabled
• allowGuestCheckout, requireAccount
• shopCatalogId — full catalog when no menu assignment
• Menu items from catalog assignments targeting storefront

Public APIs

Storefront checkout path

flowchart TD
  CFG[Load public config + menu-items]
  CART[pos.createCart / posApi cart ops]
  ADD[addItems · tip · tender card/crypto]
  FIN[posApi.finalize]
  INV[Core Invoicing]

  CFG --> CART --> ADD --> FIN --> INV
          

Gaps & product notes

File anchors

Related DocHub