Chatmart – WhatsApp Orders and Bookings Manager Flutter App | Web

Chatmart turns a WhatsApp Business number into a shop counter and a booking desk. A customer messages the number and, without leaving the chat, browses a catalog, places an order, pays, and books a real appointment slot. They install nothing, open no link, and create no account.

What makes Chatmart different

Native in-chat forms. Chatmart implements WhatsApp Flows, Meta’s official in-chat form system. The customer fills in a structured form inside WhatsApp rather than tapping through to a web page. Payloads are encrypted with RSA-OAEP and AES-GCM exactly as Meta’s specification requires.

Live slot availability. The times offered to a customer are calculated at the moment they open the picker, against existing bookings, the service’s duration, staff capacity and the branch’s opening hours. A slot taken seconds earlier is not shown, so double-booking cannot occur.

One installation, many locations. Each branch has its own WhatsApp number, currency, language, opening hours, catalog and staff. Branch separation is enforced by a database-level query scope rather than per-screen filtering.

The gap this fills

WhatsApp is where a large share of small businesses already take orders, by hand, in an inbox. Tools exist for takeaway-style ordering. What has been missing is appointment capability: a salon, barber, clinic, tutor, garage or studio needs a customer to choose a real time from real availability, and needs that to be correct when two people book at once.

Chatmart handles both. Sell products, take bookings, or run the two together from the same installation and the same number.

Key features

• Guided WhatsApp conversation driven by a state machine, with reset keywords, session timeouts and recovery from failures
• Product catalog with categories, stock, SKUs and images, plus sync to a Meta Commerce Catalog for Multi-Product Messages
• Appointment services with duration and capacity, weekly opening hours and the live availability engine
• Stripe Checkout links sent in the chat, webhook confirmation, and automatic refunds when a paid order is cancelled
• Admin panel: dashboard, orders, appointments, branch comparison, products, categories, services, customers, campaigns, team, settings
• Three roles with server-enforced permissions. Staff never see revenue
• Broadcast campaigns to a filtered customer list using Meta-approved templates
• Loyalty points, awarded on delivery and reversed on cancellation
• Abandoned cart recovery, sent once, inside the 24-hour service window
• Light and dark themes across every screen
• Every customer-facing message in a language file; each branch can speak a different language
• REST API with token authentication for the companion mobile app

Technical highlights

• Laravel 13 on PHP 8.3, Livewire 3, Tailwind CSS
• WhatsApp Cloud API only. No unofficial automation, so business numbers are not put at risk
• Webhook signatures verified on every request, failing closed when no secret is set
• Inbound messages processed on a queue with idempotency, so Meta retries cannot duplicate a reply
• Meta access tokens encrypted at rest
• 237 automated tests covering the conversation engine, payments, tenancy, scheduling and every admin route
• One-command installer: php artisan chatmart:install

Requirements

• PHP 8.3 or newer
• MySQL 8.0+ or MariaDB 10.6+
• Composer 2.x
• Apache or Nginx with the document root pointed at the public folder
• HTTPS in production, required by Meta for webhook delivery
• A Meta WhatsApp Business account, which provides a test number and access token at no cost during setup
• Node.js is not required. Compiled CSS and JavaScript are included

Third-party services and ongoing costs

Chatmart is a one-time purchase with no subscription of its own. It connects to outside services that bill you directly, and those charges are ongoing and are not included in the price of this item.

• Meta WhatsApp Cloud API — required. No WhatsApp message is sent or received without it. Meta bills per conversation, at a rate that depends on the conversation category and your customer’s country. Meta also provides a test number and a development allowance. Pricing is set by Meta and can change.
• Stripe — optional. Only needed to take card payments in the chat. Stripe charges a percentage plus a fixed fee on each successful charge, varying by country. Without Stripe, orders are still taken and confirmed without online payment.
• Firebase Cloud Messaging — optional. Push notifications to the mobile app. No cost at these volumes.
• Web hosting — required, as with any PHP application.

You will need your own accounts with Meta and, if you want payments, Stripe.