bangkok / hospitality tech
booking, inventory and ai customer service for bangkok f and b, venue and hotel operators.
a bangkok hospitality operator runs four venues across thonglor, ekkamai and phrom phong on duct-tape systems. a thai pos (loyverse, storehub or ocha) on ipads. flowaccount on the office laptop. paper payroll plus excel. four separate facebook pages with no unified booking. a six-year-old shopify shop selling sauces that loses to lazada on every commodity item. we build the one unified booking system, the one inventory layer that talks to the catering arm and the ecommerce shop, and the one ai customer service workflow on line oa that handles the majority of routine guest queries, you set the threshold per category. fixed phases, fixed price, you own the code.
scope a hospitality build01 . why bangkok hospitality
bangkok hospitality is fragmented across stacks. an expat-founded f and b group with four venues across thonglor, ekkamai and phrom phong typically runs a thai pos (loyverse, storehub or ocha per restaurant scale) on ipads at every venue, flowaccount on the accountant's laptop, four separate facebook pages with no unified booking, paper payroll plus excel for the kitchen and floor staff, and a six-year-old shopify shop selling jars of house-made chilli paste or curry mix. the local thai partner runs line oa for customer messaging because that is where thai guests actually live. the owner runs everything else from a phone screen at 6am saturday between morning service prep and lunch rush.
the problem is not the tools. each tool is fine in isolation. the problem is the seam between them. a booking that comes in on a facebook page does not post to the right venue's google calendar. an inventory order placed by the kitchen at thonglor does not show on the catering arm's purchase log. a line oa message asking about table availability gets read at 11pm by an owner who is too tired to reply. a shopify order for chilli paste does not deduct stock from the catering arm's reserve. the gaps cost hours per week and revenue per month in lost bookings and miscounted inventory.
we build the integration seam. one unified booking system that ingests from facebook, google business profile, line oa and the venue's own website, posts to the venue-specific google calendar, sends the table confirmation in thai to the guest and in english to the owner. one inventory dashboard that pulls from your thai pos (loyverse, storehub or ocha), the catering arm's ledger and the shopify shop, flags low stock per sku, and writes purchase orders to suppliers. one ai customer service workflow on line oa that handles availability questions, menu queries, dietary restrictions, parking and table preferences in thai and english, with a human handoff to staff when the question lands outside the bounds.
the stack stays light. your thai pos stays. flowaccount stays. line oa stays. shopify stays. we add a thin next.js layer that talks to each of those systems via their documented api, plus a claude api layer for the ai customer service workflow. we integrate with the dominant thai pos systems (loyverse, storehub, ocha) per restaurant scale and operations. no proprietary tool the operator cannot replace. no plugin sprawl. owner accesses everything from one dashboard on the phone. staff accesses the booking and inventory pieces on a tablet at the host stand. the build ships in fixed phases with a fixed delivery date, not a quarter of vendor management.
02 . what we build for bangkok hospitality
01
unified booking system. one booking layer that ingests from facebook, google business profile, line oa and the venue website. posts to the venue-specific google calendar. confirmations in thai to the guest, english to the owner. covers up to ten venues per build. see custom apps→
02
inventory dashboard. pulls stock from your thai pos (loyverse, storehub or ocha), the catering ledger and shopify. low-stock flags per sku, supplier purchase order automation, end-of-day inventory snapshot. we target a meaningful daily-stock-check time saving for the head chef. see custom apps→
03
line oa ai customer service. claude on line oa handling availability, menu, dietary restrictions, parking, table preferences in thai and english. human handoff to staff for questions outside the bounds. handles the majority of routine guest queries automatically, you set the threshold per category. see ai integration→
04
owner dashboard. one phone screen view for the owner. daily revenue per venue, table fill rate, top selling items, inventory alerts, staff hours. updates in real time from your thai pos plus flowaccount. saves the daily reconciliation pull from each venue manager. see custom apps→
05
ecommerce + catering bridge. shopify shop selling sauces, spice mixes or catering packages talks to the catering arm's inventory and to a delivery partner (lalamove or grab express). orders deduct from the right stock pool. no manual reconciliation at month end. see custom apps→
03 . case anchor
04 . the studio method
phase 0
1 to 2 weeks
walk-through of every venue and the catering arm. inventory of every system (loyverse, flowaccount, facebook, line oa, shopify, google calendar). hour baseline per role. prioritised list of the workflows to ship first. pdpa data flow mapping for guest data. refundable on no-fit.
phase 1
weeks 1 to 3
booking layer wired to all sources. venue calendars synced. line oa ai workflow in first version. owner dashboard at mvp. one venue used as the pilot before the full rollout.
phase 2
weeks 3 to 5
remaining venues onboarded. inventory dashboard live across loyverse, catering and shopify. staff training (on-site at each venue, in english plus thai for the host stand crews). guest-facing communication in thai live.
phase 3
weeks 5 to 6 plus 90 days care
production monitoring on every venue. line oa workflow tuning based on real guest queries. revenue and table fill rate measured against the phase 0 baseline. ninety-day care window included.
05 . questions from bangkok operators
01
do we have to replace our pos?
no. your thai pos (loyverse, storehub or ocha) stays. flowaccount stays. line oa stays. shopify stays. we add a thin integration layer that talks to each of those systems via their api. we integrate with the dominant thai pos systems (loyverse, storehub, ocha) per restaurant scale and operations. no proprietary tool you cannot replace. you stay in control of the underlying stack.
02
how do you handle thai guests on line oa?
claude on line oa handles thai-language guest queries natively. availability, menu, dietary restrictions, parking, table preferences. the ai writes in the same warmth the venue's actual host crew uses, not a generic ai register. when a query lands outside the bounds (a complaint, a media request, a vip question), the workflow hands off to a named staff member with the conversation context attached.
03
what about pdpa for guest data?
guest booking and customer service data is personal data under pdpa b.e. 2562, sections 19, 23 to 29, 37 (cross-border per section 28). data flow mapping is locked in phase 0. retention rules are set per use case (bookings kept for the period the venue operationally needs, marketing consent tracked separately, no consent no marketing comms). cross-border data transfer to claude api is documented under the same framework. delivered as part of phase 0 so your local thai counsel can sign off.
04
we have one venue today and three more in the pipeline. how does the build scale?
the build is sized to support up to ten venues from day one. you start with one or two and onboard the next venues as they come online. the per-venue onboarding is two to three days of configuration, not a full rebuild. the booking, inventory and line oa workflows are venue-agnostic at the data layer.
05
do we need a thai accountant to use flowaccount?
the build does not replace your accountant. flowaccount stays. your existing thai accountant continues to handle vat, withholding tax and corporate income tax filings. the inventory dashboard pulls from flowaccount data so you and your accountant see the same numbers. saves the monthly reconciliation pull at the owner level.
06
how long until i see results?
phase 0 is one to two weeks. phase 1 ships a working pilot at one venue in three weeks. the full rollout across multiple venues lands in five to six weeks. the line oa ai workflow saves operator hours from day one of phase 2. revenue impact through better booking capture and inventory tightness shows in the first full month after rollout.
07
what about staff training?
two training sessions per venue. on-site at the host stand, the kitchen and the office. in english plus thai for the floor crews. operating handbook in both languages. recorded video walkthrough stored in your google drive. one-page emergency restart guide laminated at every host stand.
06 . go further
ready for phase 0?
book a phase 0 walk-through of your venues. one to two weeks after the kickoff, a twelve-page scoping document, refundable if the workflow inventory shows no material time or revenue saving.