fteg-reservation package-reservation P0 done G0–G3 + B6 live

FTEG Reservation — Product Plan

Standalone booking product. Venues subscribe via fteg-erp. CMS sites, golf, salons, and client ERPs consume the public API — they do not install reservation code.

Decision (Jul 2026)
Product UX reference: tempahgo.my.
fteg-reservation is standalone (public + BO + API) and a CMS plugin for Ichiwa via API.
Corporate CMS sites never install reservation — they simply don’t subscribe.

Hosts (live)

RoleURL
Publicreservation-48291037.fteg.dev — landing + /book
Backofficereservation-bo-28492103.fteg.dev
APIreservation-apis-58393821.fteg.dev — CMS embed + demo

Contents

  1. Three layers
  2. Architecture
  3. What stays in CMS vs product
  4. Current status
  5. Rollout (Track G)
  6. References

1. Three layers

LayerPathRole
Product /srv/www/fteg-products/reservation (live) Multi-tenant app — venues, public API, venue BO, Fiuu deposit + wallet
Commercial /srv/www/hubs/fteg-erp Product catalog, RM59/mo plan (package-subscription), Fiuu pay → venue + API key
Engine /srv/www/package-reservation Composer library — availability, models, BO screens, API routes

2. Architecture

fteg-erp
  ├── Product: "FTEG Reservation Basic / Pro"
  └── Client subscribes → API key + venue tenant provisioned

fteg-reservation (product app)
  ├── Venue: Ichiwa (#1)
  ├── Venue: Permaipura Golf (future)
  └── Public API + venue BO

Consumers (subscribe + integrate)
  ├── fteg-cms-ichiwa-dev   → /reservation page calls API
  ├── fteg-officialweb      → skip (no subscription)
  └── permaipura-golf         → tee times API only

3. What stays in CMS vs product

CMS tenant keepsReservation product owns
Menu, events, omakase pages
Brand Blade / CSS
/reservation page shell + JS
Page copy / T&C in package-cms 		Slot rules, capacity pools
Booking records, approvals
Availability API
Fiuu guest deposit
Venue wallet / fee contra
Email / WhatsApp notify
G2 done — Ichiwa reservation wizard calls the product API with a venue API key. Bookings land in fteg-reservation (not the CMS local DB).

4. Current status

ItemStatus
package-reservation P0 in Ichiwa CMS done
Ichiwa reservation (product API) live
fteg-reservation product shell — reservation-48291037.fteg.dev G0 live
fteg-erp subscription catalog (B6) — RM59/mo Fiuu done
Ichiwa → product API + venue key (G2) done
Fiuu guest deposit + venue wallet contra (G3) done

5. Rollout (Track G — complete)

  1. G0 — Product shell (bo-starter) + subscribe gate via fteg-erp ✅
  2. G1 — Multi-tenant venues + API keys + scoped booking API ✅
  3. G2 — Ichiwa venue #1 — CMS wizard → product API + venue key ✅
  4. G3 — Fiuu guest deposit + venue wallet contra ✅
  5. B6 — fteg-erp catalog + RM59/mo Fiuu subscribe + venue provision ✅

6. References