Nusantech · Product datasheet
Booking System
Reservations that don't collapse at scale.
Printed
21 May 2026
Overview
A reservation and scheduling platform for service businesses, hospitality, and public-sector citizen services. Handles rooms, staff, equipment, queues, and citizen appointments. Payment-aware, calendar-aware, language-aware, and multi-branch by design.
Capabilities
Scheduling & resources
- Resource scheduling
- Rooms, staff, equipment, vehicles, queue slots - any bookable resource modelled with capacity, working hours, and conflict rules.
- Multi-branch
- Branch is a first-class scoping dimension. Each branch runs its own schedule, roster, cash float, and inventory; HQ gets consolidated views in real time.
- Calendar integrations
- Two-way sync with Google Calendar, Outlook, Apple Calendar. ICS feeds for downstream systems. Per-staff availability respected.
- Aggregator sync
- Sync inventory and bookings with ClassPass and other third-party marketplaces. One calendar of truth across channels.
Operations
- Operator dashboard
- Counter view, day view, week grid, kanban, ad-hoc bookings, walk-in handling, cancellation flows with refund policy enforcement.
- QR check-in
- Members scan a QR at the door, kiosk, or studio entrance to mark attendance. Auto-decrements credits, flags no-shows, feeds occupancy live.
- Staff payroll & commissions
- Per-booking commission, hourly tracked-time, tips, tiered service rates roll up into payable periods. Export to payroll or integrate with accounting.
- Smart notifications
- Confirmations, reminders, change alerts via email, SMS, WhatsApp, push. Time-zone and language aware.
Customer-facing
- Payment capture
- Stripe, Xendit, Midtrans, DOKU, hold + release patterns. Deposit, full-pay, or pay-at-venue flows.
- White-label customer UI
- Embeddable widget or branded standalone site. Custom domain, theming, your language and brand voice.
Technical specifications
Deployment & hosting
- Managed cloud
- Operated by Nusantech on AWS, GCP, or other cloud providers per customer preference.
- Self-hosted
- On customer VPC or on-premises infrastructure. Ships with source code, deployment runbook, and an update cadence agreed during contracting.
- Data residency
- Singapore default controller seat for regional deployments. Per-jurisdiction hosting where regulations require (Indonesia public-scope on Indonesian territory under PP 71/2019, Vietnam impact-assessed transfers under PDPD 13/2023). Transfer logs and named DPO contacts provided per region.
- Identity & SSO
- SAML 2.0, OIDC, SCIM 2.0 user provisioning.
- Audit trail
- Full state-transition logging: identity, timestamp, version, environment, client, network, override flag, before-and-after state.
- Data export
- Schema-preserving export of all customer data, delivered within an agreed window at no additional charge. Source code transferable for custom-engineered deployments.
Integrations
- Payment
- Stripe, Xendit, Midtrans, DOKU; bank-direct gateways scoped per engagement.
- Calendar
- Google Calendar, Outlook, Apple Calendar (iCal), ICS feeds
- Messaging
- WhatsApp Business, SMS providers, transactional email (SendGrid, SES, custom)
- POS
- Native counter and kiosk UI included. External POS (Toast, Square, in-house) scoped per deployment.
- Aggregators
- ClassPass and other discovery marketplaces
- Payroll & accounting
- Export to payroll, integrate with accounting platforms
- Developer API
- REST + webhooks for downstream integration
- BI / analytics
- Exports to Snowflake, BigQuery, custom data warehouses
Industries served
- Fitness & Wellness
- Hospitality
- Public Sector
- Financial Services
- Healthcare
Typical implementation phases
| Phase | Duration | Description |
|---|---|---|
| Discovery | 2-4 weeks | Process mapping, target operating model, written build plan with milestones. Output: scoped quote and acceptance criteria. |
| Foundation sprint | 2-3 weeks | Auth, tenancy, core domain model, deployment pipelines. The boring parts done right before any feature work. |
| Feature sprints | Per engagement | Two-week cadence. Written changelog and Friday demos. Cadence and feature priority agreed with the project lead. |
| Pilot | 4-8 weeks | Rollout to one branch / cohort / pilot market first. Daily standup with the operator team. Stabilisation hotfix cycles included. |
| Rollout | Per scope | Phased rollout, training delivered per cohort, previous system decommissioned only after a week of parallel running per site. |
Pricing
Pricing is intentionally not published. Every deployment is scoped per engagement - factors like user volume, deployment model (managed vs self-hosted), data residency requirements, and integration depth all shape the quote. The next step is a 30-minute discovery call.
Further reading
- An operations platform for a boutique fitness studio chain - nusantech.com/blog/case-study/boutique-fitness-multi-branch-platform
Next steps
Schedule a 30-min call
calendly.com/nicolasruslim1/30min
WhatsApp the team
+65 8515 3618
General enquiries
hello@nusantech.com