Serverless Event Engine & Database for Pourz Platform

Target Stack: Make.com + Airtable + LINE OA (Messaging API) + External Accounting API (Xero / Zoho Books) + LINE Notify API Executive Summary & System Flow Pourz operates phygital luxury daybed vaults (B.O.B.™) inside 5-star resorts. Guests scan on-device QR codes using LINE OA to order tasting flights or bottle upgrades. The backend operates on a 0.5-second webhook event loop: Guest Scanning: Triggers a Make.com webhook. Dynamic Validation: Make.com verifies device/resort status and regional pricing configuration in Airtable. Execution & Dispatch: Renders LINE OA Flex Messages to the guest and pushes real-time smartwatch notifications to resort staff via LINE Notify. Audit & Ledger: Captures QA/QC reset photos and syncs financial ledger entries to an external accounting API (Xero/Zoho Books) for automated billing. Reply to potential hires, regarding the 0.5 requirement: Great feedback on the execution chain! To clarify: the accounting module is decoupled asynchronously from the core unlock scenario. The real-time loop less than 0.5s only handles Airtable validation, LINE Flex Message rendering, and LINE Notify staff dispatch. The dual-ledger accounting sync (Xero/Zoho) runs out-of-band via background webhooks/triggers with Make.com error-handling/retry directives (Break modules). An API latency spike or error in Xero will never block the guest's session or delay the staff notification. Does this asynchronous decoupling fit your build approach for the pipeline?