Module Reference

Capabilities

Which Modules to switch on for booking, payments, staff pay, a register, online ordering, discounts and customer accounts, and the platform services each one uses.

A business asks for a capability ("take bookings", "pay my staff"), not a Module. This page maps each capability to the Modules that provide it and the platform services those Modules call. Switch Modules on in Settings → Modules; switching one on also switches on the Modules it uses. See Modules for the switches and Build on a Module for adding your own features.

Booking

Customers pick a service, a time and, where the business wants it, the person who serves them. Two customers can't take the same slot, and a therapist or room can't be booked twice at once. Staff reschedule a booking, including to another Location, and the customer gets an email about it. A service can take a deposit at booking and the balance later, and customers get confirmations and reminders by email or LINE.

  • Switch on Booking.
  • Add Staff so bookings follow each person's working hours, and Queue to take walk-ins and hand them over to a booking.
  • Add Customers for customer profiles, Membership for packages and points, and Account so customers see and cancel their own bookings.
  • Booking takes payment through the platform's payments service, sends messages through Outbox (platform email and LINE), and runs its reminders and payment checks as scheduled tasks.

Payments

Payments isn't a Module. Each place that sells runs its own checkout: the online shop in Storefront, bookings in Booking, and the register in POS. All three call the same platform payments service, which charges through Beam or Stripe Connect.

  • Online. The shop and the booking page take Beam card and PromptPay on their own pages, or Stripe. Both can also take a bank transfer, where the customer uploads a slip and staff verify it.
  • At the counter. The register shows a Beam PromptPay QR or sends the charge to a paired Beam card terminal, and takes cash.
  • Duplicates and failures. A payment webhook that arrives twice pays the order once, and two pay requests at the same moment create one charge.
  • Refunds. Each checkout records its own refunds. A cancelled shop order is queued as a refund owed until staff refund or waive it.
  • Settings. Branches holds Settings → Payments: which online methods are offered, the bank accounts shown for transfers, and which company's merchant account each Location's sales are charged to.
  • Reporting. Add Finance for revenue reports, reconciliation and period close across all three.

Staff pay & commissions

Staff clock in and out at the register on their own PIN. Each shift is paid at the person's own hourly rate, or the business default, and a rate change doesn't rewrite shifts already worked. When commissions are on and a booking is completed, the people who delivered it share a commission on what the booking took after any discount, at each person's rate in force that day. Tips are entered against a booking, at the register or in admin. A manager closes a pay period into a pay run, which locks every shift and earning inside it, and exports it as a spreadsheet.

  • Switch on Staff for the staff directory, rosters, hourly pay and pay runs.
  • Add POS for the time clock at the register.
  • Add Booking for commissions and tips.
  • Stardeck doesn't send the money. A pay run is exported for the business to pay through its bank or payroll provider.

Point of sale

Staff sign in at the register with a PIN, ring up orders, seat tables, split a bill, apply discounts and take payment. Sales and happy hours ring up by themselves, and cashiers enter customers' codes and staff discounts. Orders go to the kitchen as printed station tickets or on a kitchen screen. Receipts print on the counter printer. A cashier who loses the connection keeps selling, and every line lands once when it comes back. At the end of the day, the cash session closes against a Z report.

  • Switch on POS. It brings in Inventory for stock and Staff for the people at the register.
  • Add Catalog to sell the shop's products at the register, Guest ordering so diners order from their phone by scanning a QR code on their table, Supply chain for suppliers and purchasing, and Customers or Membership to attach a customer or redeem points.
  • Printers and cash drawers connect through Stardeck Edge. Card and QR payments use the platform payments service through Beam.

Online ordering

Customers browse the shop, add to a cart and pay online, then get an email when the order is confirmed. An order is shipped, or picked up at a Location and held from that Location's stock. When two shoppers race for the last items, only one gets them, and a shopper who asks for more than the shop has is told it's sold out before anything is held. A product can be set to keep selling when it's out of stock, so the unit is owed. Discount codes, sale prices, free gifts and gift cards work at checkout.

  • Switch on Storefront. It brings in Catalog for products and Inventory for stock.
  • Diners ordering at a restaurant table use Guest ordering instead, under Point of sale. Their orders go to the table's ticket in POS, and they pay staff, not online.
  • Add Account for order history and Website for the business's public site.
  • Storefront takes payment through the platform payments service and sends order email through Outbox.

Discounts

The business sets up a sale, a code, a buy X get Y offer, a free gift, a member price or a happy hour once, and it works in the online shop, at the register, for food ordering and for bookings. Discounts combine only when the business allows it, and a code's usage limit counts every channel.

Customer accounts

Customers sign in to the app and see one account page with whatever the business uses: their bookings, orders, visits and receipts from the register, queue tickets, points and packages, and their profile. A customer is one platform identity, so the same person is recognised across bookings, the shop and the register.

  • Switch on Account. Its tabs come from the other Modules that are on: Booking adds bookings, Storefront adds orders, POS adds visits, Queue adds queue tickets, Membership adds points and packages, and Customers adds the profile and contact details.
  • Sign-in is the platform's app sign-in: email and password, Google, phone code or LINE, whichever the app turns on.
  • Messages to customers go through Outbox by email or LINE.
  • The account page doesn't store payment cards.

Summary

CapabilityModulesPlatform services
BookingBooking; add Staff, Queue, Customers, Membership, AccountPayments (Beam, Stripe), email and LINE, scheduled tasks
PaymentsStorefront, Booking and POS checkouts; settings in Branches; reports in FinancePayments (Beam card, PromptPay and card terminals; Stripe Connect online)
Staff pay & commissionsStaff; POS for the time clock; Booking for commissions and tipsNone
Point of salePOS (with Inventory, Staff); add Catalog, Guest ordering, Supply chain, Customers, MembershipStardeck Edge, Payments (Beam)
Online orderingStorefront (with Catalog, Inventory); add Account, WebsitePayments (Beam, Stripe), email
DiscountsDiscounts (with Storefront, POS or Booking); add Membership, Guest orderingNone
Customer accountsAccount; tabs from Booking, Storefront, POS, Queue, Membership, CustomersApp sign-in, platform identities, email and LINE

Next

Build on a Module

Add your own features next to these Modules without breaking their updates