Demo Mode

Demo Mode · Fictional data · Morning Mobile-Order Surge

Change experience

Interactive Product Demo

Morning Mobile-Order Surge

Common Ground Hospitality · Common Ground Café

← Back to Connection Studio

POS

POS CSV

Import path

Signals VeraTable can useOrders · Sales · Source health · Historical import

Unlocks Operational Memory, demand outlook, and Portfolio exceptions from historical POS exports operators already own.

Third-party names and marks belong to their respective owners. No partnership or endorsement is implied.

Connection status

Not connected

Environment
Demo data
Access model
Read-only access

Import POS history

Upload a merchant-owned sales export for Common Ground Café — daily totals or ticket lines. VeraTable normalizes it into the same demand path as Square/Clover — without a live POS API.

Daily totals: service_date, order_count, and service_period or time_window. Or ticket lines: service_date (or timestamp), menu_item, quantity — include order_id when tickets have multiple items. Optional: channel, catalog ids, variation, modifiers, gross_cents.

Understanding

What this helps VeraTable understand

  • Demand patterns
  • Expected busy periods
  • Location comparison
  • Operational Memory

Signals

What VeraTable receives

  • Orders
  • Sales
  • Source health
  • Historical import
  1. POS CSV
  2. Normalized signals
  3. Today’s Service

VeraTable does not receive payment card numbers or bank credentials from this connection.

Connection Health

Demo only

Last successful sync
Simulated — no live sync
Latest attempt
Simulated — no live sync

Demo Mode uses fictional data. No live provider sync occurred.

Connection path

Current stage: Discover — Understand value and what VeraTable can access.

  1. Discover (current)
  2. Authorize (upcoming)
  3. Import (upcoming)
  4. Learn (upcoming)
  5. Insights (upcoming)
Full lifecycle stages
  1. DiscoverUnderstand what the provider can add. (current)
  2. Review valueConfirm the operational value of connecting. (upcoming)
  3. Review data accessReview what VeraTable can and cannot access. (upcoming)
  4. AuthorizeApprove read-only access with the provider. (upcoming)
  5. ValidateConfirm the connection and location mapping. (upcoming)
  6. Initial syncVeraTable begins receiving approved signals. (upcoming)
  7. Start learningVeraTable looks for repeatable patterns over time. (upcoming)

Demo Mode uses a simulated lifecycle. Authorization and sync do not run against a live merchant account.

Availability and notes

Availability

Import historical sales for the active location. No live POS connection required.

  • Import path — merchant CSV/report only; not Square/Clover/Toast OAuth.
  • Adapter: createPosCsvAdapter → OperationalSignal kind order → Operational Memory.
  • Provenance stays labeled as pos-csv-import so Ready never pretends the feed is live API.
  • Primary onboarding wedge when gated POS APIs are unavailable.