ProductStack test bench

Members Play · connect · belong

• Web VercelApplications, membership, billing, and events for members on the web.
• Mobile ExpoThe member app: events, concierge, and finding a game—in the room or online.

Operations Manage · run · grow

• Web VercelThe staff console: membership, inventory, marketing, and finance reconciliation.
• Mobile ExpoThe host terminal on the floor: check-in, tables, coat check, concierge, and Tap to Pay for new memberships.

Verified connections · 8

• Members web →to Client BackendMember data and billing
• Members mobile →to Client BackendMember data
• Members →to Member AuthSign-in and sessions
• Operations →to Member AuthStaff sign-in and passkeys
• Operations web →to Client BackendMembership, host, and finance
• Operations web →to Operations BackendInventory and marketing
• Operations mobile →to Client BackendHost terminal, concierge, Tap to Pay
• Operations mobile →to Operations BackendInventory tasks

Member Auth Sign-in · passkeys · sessions

Hosted on Vercel

One identity service for members and staff: password exchange, email links, passkeys, and session minting.

Verified connections · 4

• Members →to Member AuthSign-in and sessions
• Operations →to Member AuthStaff sign-in and passkeys
• Member Auth ↔and Client BackendAccount admin; invite validation
• Operations Backend →to Member AuthStaff user admin

Client Backend Membership · billing · finance · host

Hosted on Render · Job worker · 6 scheduled jobs

The system of record for members and money: applications, billing, host operations, and finance reconciliation. A queue worker and scheduled jobs handle billing activation, notifications, and hourly finance syncs.

Operations Backend Inventory · purchasing · marketing

Hosted on Render · 3 scheduled jobs

Inventory, vendors, purchasing, and marketing. Serves the finance console, reading reconciled figures from the shared database and passing changes to the Client Backend.

Verified connections · 17

• Members web →to Client BackendMember data and billing
• Members mobile →to Client BackendMember data
• Operations web →to Client BackendMembership, host, and finance
• Operations web →to Operations BackendInventory and marketing
• Operations mobile →to Client BackendHost terminal, concierge, Tap to Pay
• Operations mobile →to Operations BackendInventory tasks
• Member Auth ↔and Client BackendAccount admin; invite validation
• Operations Backend →to Member AuthStaff user admin
• Operations Backend →to Client BackendFinance proxy; marketing publish
• Client Backend ↔and StripeBilling, Terminal; webhooks back
• Client Backend →to ToastOrders and labor
• Client Backend →to PlaidBank transactions
• QuickBooks →to Client BackendStatement import · file import
• ADP →to Client BackendPayroll upload · file import
• Client Backend →to SquareCafé orders and payouts
• Operations Backend →to SquareCatalog publish; sales ingest
• Operations Backend →to ShopifyInventory publish; order ingest

Payments & finance Reconciled in one place · Client Backend

Four live feeds and two file imports reconcile inside the Client Backend: payments, café and bar sales, bank transactions, payroll, and accounting statements.

• Stripe API · webhooksCard setup, initiation fees, annual memberships, and Stripe Terminal for Tap to Pay on the host terminal. Invoices, renewals, refunds, and disputes return by webhook.
• Toast APIBar orders and labor, pulled hourly into finance reconciliation.
• Plaid APIBank connections made from the staff console; transactions sync hourly into finance reconciliation.
• QuickBooks File importAccounting statements imported as files. There is no live QuickBooks API connection.
• ADP File importPayroll detail uploaded as spreadsheet exports for labor-cost reconciliation. There is no live ADP API connection.
• Square APICafé orders, payouts, and staff flow into finance every hour. Separately, the Operations Backend is built to publish the retail catalog to Square; each channel is switched on independently.

Retail channels One catalog, per-channel sync · Operations Backend

The Operations Backend owns the retail catalog and is built to publish it to Square in the room and Shopify online, with each channel switched on separately.

• Square APICafé orders, payouts, and staff flow into finance every hour. Separately, the Operations Backend is built to publish the retail catalog to Square; each channel is switched on independently.
• Shopify APIThe online shop. The Operations Backend is built to publish retail inventory and read orders back; it is not yet switched on in production.

Verified connections · 8

• Client Backend ↔and StripeBilling, Terminal; webhooks back
• Client Backend →to ToastOrders and labor
• Client Backend →to PlaidBank transactions
• QuickBooks →to Client BackendStatement import · file import
• ADP →to Client BackendPayroll upload · file import
• Client Backend →to SquareCafé orders and payouts
• Operations Backend →to SquareCatalog publish; sales ingest
• Operations Backend →to ShopifyInventory publish; order ingest