# CTC Smart Tech — Travel solution / Flamingo Travel

Version: 09.2026

A solution-design case study built on the Flamingo Travel system: e-commerce, cross-department ERP, an AI assistant and role-based business apps.

Status: The ERP/e-commerce UI has an existing demo; the AI and mobile apps are proposed prototypes.

## Problem
- B2B/B2C intake, quote versions and cross-department handovers must all attach to one tour code.
- Service bookings and supplier payment deadlines (COD) must be reconciled with cash received and approval authority.
- Field staff need itineraries and assigned tasks on mobile; managers need a risk queue instead of the full ERP menu.

## Input data
- Tour catalogue, RFQ/B2C requests, tour codes, itineraries and service requirements.
- Versioned supplier price lists, seasons, norms and COD policy.
- Staff assignments, checklists, forms, budget/receipts/payments and approval rules.

## Deliverables
- Integration map across e-commerce, Sales, Operations and Accounting with an owner for every step.
- ERP/e-commerce screenshot set, case study and AI assistant prototype following sourced scenarios.
- Three sample apps (Sales / Guide / Operations manager); module/permission matrix and ERP integration roadmap.

## Pilot roadmap
- Map the 12-step Sales, 6-step Operations and 5 Accounting task groups to data and owners.
- Run a transport & meals pilot on confirmed price lists/norms; evaluate extraction, pricing and condition errors.
- Connect the ERP and test the flow: Sales handover → guide reports incident → manager approves → Accounting checks.
- Accept persistent data, cross-tour permissions, sync, exceptions and training before scaling.

## Governance
- The current ERP keeps demo data in the browser; production needs a backend, authentication, API-level permissions and multi-user sync.
- The AI and apps are interactive prototypes not calling real ERP APIs or LLMs; data and calculations are illustrative only.
- COD here means the supplier payment deadline. An approved request is not a completed payment; Accounting controls cash in/out.
- Permissions follow role and assigned tour; hiding menus does not replace access control.

## Modules

### E-commerce & Sales
Tour products, B2C requests/orders, RFQ pipeline, quote builder and Form 1 handover.

### Tour operations ERP
Tour files, suppliers, bookings, COD, guide assignments, checklists and cross-department forms.

### Travel AI Copilot
Suggests price checks for transport & meals, reads sources, spots missing conditions, reminds COD and summarises progress.

### Role-based business apps
Sales handle opportunities/handover; guides run tours/report incidents; managers track risk/approve/coordinate.

## Acceptance

### Quote turnaround
Minutes from valid input to a budget ready for review.

### Budget accuracy
Cost lines matching the reference sheet over all lines checked.

### Errors caught
Share of surcharges / missing conditions detected on the test scenario set.

### Valid price coverage
Share of services with a price and conditions still valid on departure date.

## FAQ

### Do the mobile apps replace the ERP?
No. The apps focus on role-based tasks and use the same ERP APIs, tour codes, permissions and logs. The current prototype illustrates UI and flow; it is not a production app.

### Is the AI live?
The UI in this kit simulates the AI Automation documentation and the Flamingo POC. ERP APIs, a document store, an AI model and testing are needed before real use.

### Are payments and cross-device sync implemented?
The reviewed ERP uses sample data / localStorage. Those production capabilities must be built and accepted separately.

## Case study: Flamingo Travel
Process source: 12 Sales steps, 6 Operations steps, 5 Accounting task groups. The existing demo uses fake-db/localStorage; multi-user production is not implied.

### E-commerce & tour sales channel
Customers browse tour products, send requests or start booking; B2C intake is organised for Sales to pick up.
Screen: /tour-packages
![Screenshot](https://solutions.smarttechctc.io/travel/screens/ecommerce.webp)

### Sales: from request to opportunity
A pipeline tracks quoting stages; customer details and needs flow into the tour file.
Screen: /dashboard/sales
![Screenshot](https://solutions.smarttechctc.io/travel/screens/erp-sales.webp)

### Supplier-based quote builder
Prices computed from services, norms and supplier conditions; versioned, with change explanations before sending to the customer.
Screen: /dashboard/sales/quotes
![Screenshot](https://solutions.smarttechctc.io/travel/screens/erp-quote.webp)

### Tour file: the ERP’s connecting point
Tracks Sales–Operations–Accounting per tour; Form 1 handover, service bookings and task progress.
Screen: /dashboard/ops
![Screenshot](https://solutions.smarttechctc.io/travel/screens/erp-operations.webp)

### Supplier payment deadline control
Bookings prioritised by COD deadline; service status and cash in/out linked before payment.
Screen: /dashboard/ops/cod
![Screenshot](https://solutions.smarttechctc.io/travel/screens/erp-cod.webp)

### Guide assignment & schedule
Owners and guides organised per tour; the base for pushing work schedules to the field app.
Screen: /dashboard/ops/assignments
![Screenshot](https://solutions.smarttechctc.io/travel/screens/erp-guides.webp)

### Budget vs settlement
Revenue, cost and incidents reconciled per tour; approvals with owners and variance control.
Screen: /dashboard/ops/finance
![Screenshot](https://solutions.smarttechctc.io/travel/screens/erp-finance.webp)

## AI assistant
Prototype from the transport & meals POC documentation and the AI Automation design. Reads sources, checks conditions, computes by rules, hands to an approver. No real LLM/API call.
![AI](https://solutions.smarttechctc.io/travel/screens/ai-assistant.webp)

## Sales app
- Today’s opportunities and follow-ups.
- Draft quotes with versions and service conditions.
- Closing checklist; Form 1 handover to Operations.

ERP mapping: RFQ pipeline → Quote builder → Form 1 → Tour file
Permissions: Sales view/edit their opportunities and prepare handover; they do not confirm cash received or approve spending.
![Sales app](https://solutions.smarttechctc.io/travel/screens/mobile-sales.webp)
Open sample app: https://solutions.smarttechctc.io/demo/travel/sales/

## Tour guide app
- Assigned tours, daily itinerary and required service details.
- Pick-up, headcount and voucher checklist with completion confirmation.
- Incident reports with descriptions; track Operations’ response.

ERP mapping: Assignments / guide schedule → Tour itinerary → Checklist → Incidents
Permissions: Access only to assigned tours and customer-service data; no margins or company-wide settlements.
![Tour guide app](https://solutions.smarttechctc.io/travel/screens/mobile-guide.webp)
Open sample app: https://solutions.smarttechctc.io/demo/travel/guide/

## Operations manager app
- Overview of running tours, unconfirmed bookings and upcoming COD deadlines.
- Incident approval queue with basis and recorded reasons.
- Assign guides, coordinate resources and track handovers.

ERP mapping: Tour file → COD → Incident approval → Assignments
Permissions: Approves within limits and scope; Accounting still confirms cash in/out and documents.
![Operations manager app](https://solutions.smarttechctc.io/travel/screens/mobile-manager.webp)
Open sample app: https://solutions.smarttechctc.io/demo/travel/manager/

## Production conditions
Needs a shared backend, authentication, per-tour permissions at the API, audit log, multi-device sync and conflict handling. Payments, push, offline and voice chat are outside this prototype.

Case study: https://solutions.smarttechctc.io/case-study/flamingo-travel/
Contact: info@smarttechctc.io · (+84) 032 9119 825