Biashara ERP Enterprise Suite
← All guides

Hospitality suite overview

Hotels, restaurants, and resorts: PMS, KDS, menus, and modular hospitality modules.

Biashara ERP — Hospitality Suite Master Specification

This document preserves the full hospitality suite vision for incremental implementation.
Do not implement everything at once. Follow phased delivery with tests and tenant/branch isolation.

Vision

A unified hospitality operational ecosystem for: hotels, lodges, resorts, restaurants, cafés, bars, clubs, conference centers, safari camps, franchises, institutional kitchens — integrated with existing inventory, manufacturing, POS, finance, CRM, and multi-branch tenancy.

Architecture pillars

Hospitality Suite
├── Accommodation Engine (PMS)
├── Reservation Engine
├── Restaurant Engine
├── Fast Food / Bar / Lounge
├── Kitchen Management + KDS
├── Room Service
├── Housekeeping / Laundry / Minibar
├── Conference & Events
├── Catering / Delivery
├── Guest Billing & Folios
├── Hospitality ↔ Manufacturing
├── Hospitality ↔ Inventory (no duplicate stock logic)
├── Mobile Hospitality Operations (separate from desktop)
└── Dashboards + AI (later phases)

Implementation phases (official)

Phase Deliverable
1 Accommodation — rooms, types, states, reservations, check-in/out, half-day charges
2 Restaurant — modes, tables/floor plan (optional), POS extensions
3 Kitchen + ingredients — recipes, POS deduction, food costing, wastage hooks
4 Manufacturing integration — bakery, semi-finished, production orders
5 Room service + housekeeping
6 Conference & events
7 Mobile hospitality UX (reception, waiter, kitchen)
8 AI insights (occupancy, demand, wastage)
9 Optimization

Critical integration rules

  1. Ingredient deduction on sale — Selling a menu item deducts recipe components without requiring a production order per sale.
  2. Half-day / hourly room charges — African hospitality requirement for flexible stays.
  3. Folio billing — Room service, minibar, restaurant charges post to guest bill.
  4. Manufacturing — Kitchen prep uses existing BOM/MO; POS uses recipe consumption path.
  5. Mobile — Touch-first, bottom nav; not desktop table reuse.

Subscription tiers (target)

  • Starter: small restaurant, simple room booking
  • Professional: hotel ops, kitchen, inventory
  • Enterprise: multi-branch, manufacturing, analytics, events, AI

Engineering standards

  • BelongsToOrganization, branch_id on all transactional data
  • Services under app/Services/Hospitality/{Domain}/
  • Movement types extend InventoryMovementType — never parallel stock tables
  • Commit + push per stable milestone

Source: product architecture brief (May 2026). Update this file when phases complete.

Ready to run your business on one platform?

14-day trial on entry tier · CRM & mass SMS · Industry-specific modules · Your own workspace subdomain