Workflow
New order · Demo register 1
Checkout
A fast market-day checkout with shared mock inventory.
Catalog concept
Products
Products, variants, pricing, tax status, and stock stay under Careyosity’s business record.
Mock edits affect this browser tab only and reset on refresh. Concept preview — final product may differ.
Shared stock concept
Inventory
See mock stock by event, shop, and online channel, then try a session-only adjustment.
Counts, adjustments, sync messages, and reservations are simulated in memory only.
Unified history concept
Orders
Market, shop, and online examples in one mock history.
Refund, return, exchange, and resend controls are simulations. They never contact a processor or recipient.
Customer view concept
Customers
Optional profiles can bring purchase history, notes, and receipt preferences together.
Every name, email address, phone number, note, and purchase in this area is invented demo data.
Market-day and location workflow
Markets / Locations
Open a selling day, track the location, and preview a closeout summary.
River Market Saturday
Riverfront Pavilion · Booth C12
Event-specific pricing
Saturday market price book
Two body butters for $28 and an optional event-only quick-add can be scoped to this location.
Location concepts
Where this profile sells
Opening, closing, cash counts, pricing, and summaries are simulation-only.
Reporting concept
Reports
Mock performance across in-person and online selling.
Sales pace
Mock sales by interval
Payment mix
How customers paid
Best sellers
Top mock products
Channels
Online vs in-person
All report values and charts are hard-coded examples, not financial or tax records.
Configuration concepts
Settings / Integrations
Explore how replaceable providers and optional selling tools could fit together.
Payment-provider abstraction
Careyosity owns the business workflow—not the processor.
Products, inventory, pricing, orders, customers, taxes, and reports remain in Careyosity’s system of record.
Selling preferences
Demo controls
Accessibility
Display options
Basic food-service scope
Purposefully modest
Concepts include modifiers, notes, dine-in/takeout, tipping, open tabs, split payments, split checks, and a basic kitchen ticket view.
Not represented: complex table maps, seat-by-seat coursing, advanced routing, tip pooling, deep labor tools, or advanced full-service workflows.
All integrations are Concept, Planned, Under evaluation, or Not connected. No SDK or external service is used here.