Skip to content

Roadmap ​

Gatherloop POS ships in small, sequential PRs, each backed by a written PRD in the repo's docs/ folder before code lands. This page is mined from those PRDs — what's shipped, what's in flight, and what's been deliberately deferred (and why).

Shipped ​

Sales & Checkout

  • Board-game rental tiered pricing — per-variant (up to N minutes → price) tiers, snapshotted onto the rental at check-in so a later tier change never re-prices an active rental.
  • One combined order slip, grouped by station — Bar and Kitchen see the whole order on a single slip instead of two out-of-sync ones.
  • Per-item rental coupons — a coupon can discount a single line as well as the whole transaction.
  • RFID ticket ↔ printed-name registry — resolves a scanned card to a human-readable ticket number at rental check-in, without ever blocking check-in.
  • Table ordering — QR-code self-service menu and cart — a customer scans a table's QR code, browses the live catalog, and builds a cart that survives a reload, no login required.
  • Order checkout via QRIS — turns a table-ordering cart into a real, paid Transaction: DOKU-generated QR, save-and-pay-from-gallery, a guest-facing order-status screen, and a "Order App" source badge on the resulting POS transaction.
  • Cash payment at the cashier — a second checkout method alongside QRIS: the guest picks "Bayar dengan Cash di Kasir", walks to the till showing their daily transaction number, and the cashier's existing Pay flow settles it — no separate "confirm this app order" screen, and an order nobody pays for expires on its own.

Catalog

  • Product draft status — research a new menu item without it showing up at checkout until it's published.

Inventory

Finance

Operations

This site

  • The public documentation site you're reading now — scaffolded, deployed to GitHub Pages, and filled in section by section, PR by PR.

In Progress ​

Nothing is actively in flight right now. Gatherloop POS is built in short-lived branches that ship as soon as a PRD's phases are done, rather than long-running feature branches — so "in progress" is usually measured in hours, not weeks.

Planned ​

Pulled from the "Out of Scope" and "Future Work" sections of shipped PRDs — considered, intentionally deferred, and still on the table:

  • Ticket availability tracking — know which RFID tickets are currently out on an active rental, not just what a scanned code resolves to.
  • Budget variance alerts — a push/email nudge when a spending category crosses its target, instead of only a pull-based report.
  • Automated savings transfers — turn the manual twice-monthly savings sweep into a scheduled wallet transfer.
  • Product sales & material spend widgets — two more dashboard panels alongside the existing sales and expense charts.
  • Recurring checklist sessions — auto-create the daily opening/closing session instead of starting it by hand every morning.
  • Barcode/QR jump-to-row on stock checks — scan a shelf label to jump straight to that material's count row.
  • Supplier reverse-view — see every material a given supplier provides from the supplier's own detail page.
  • Role-based access control — today every account can do everything (create templates, publish products, flip wallet flags); scoped permissions are a natural next step once the team using the product grows past one till.
  • Notifying kitchen/bar when an order-app transaction appears — today it shows up in the existing POS list and order-slip print like any other transaction; nothing pushes to a kitchen display.
  • Notifying the customer when their order is ready — the order-status screen ends at "sedang disiapkan"; there's no ready-for-pickup ping back to the guest.
  • More payment methods — virtual account, e-wallet, through the same gateway port order checkout already has for QRIS.
  • Refunds and cancellation — a POS-side flow needs to exist before an order-app payment can be refunded through the gateway.
  • Cart merging by table — one table of four building a single bill in table ordering, instead of one cart per phone.

Have a feature request or found a gap? The project is open on GitHub — issues and PRs are welcome.

Built with VitePress. Content lives in docs-site/ — see the README for how to run it locally.