PharmaFlow is a full-stack online pharmacy platform: a production-ready Next.js web storefront and operations suite, plus matching Flutter apps for customers and delivery riders. Sell medicines and healthcare categories, run admin & support workflows, assign deliveries, and take payments — all against a unified MongoDB data layer and REST-style APIs.
PharmaFlow includes a built-in AI Order Agent — a conversational ordering channel on web and mobile that helps customers find products, build an order list, and place orders with minimal steps. Pair it with Live Support when customers prefer a human agent.
AI Order Agent
Customers describe what they need in plain language. The agent searches your catalog, answers questions, and adds items to a running order list inside the chat. When they are ready, they review the list and tap Confirm order — delivery details, payment method, and guest or logged-in checkout are handled in the same flow. No separate cart page required for agent-led orders.
- Natural-language ordering — symptoms, product names, or general requests; the agent finds relevant medicines and presents selectable options
- Order list in chat — items accumulate as the conversation progresses; customers open the order summary, adjust quantities, and confirm when ready
- One-step confirmation — confirm delivery address, payment (COD supported), and guest or account checkout without leaving the agent chat
- Prescription upload — Rx photos can be attached in the conversation for applicable products
- Product suggestions — inline product cards with add-to-order actions directly in the thread
- Live Support — separate human chat for order-related help alongside the AI channel
- Web and mobile — full-page agent chat on the storefront; dedicated tab and launcher in the Flutter customer app with persistent conversation
- Admin-configurable — connect your LLM provider API key (DeepSeek-compatible) from AI Assist settings; no separate knowledge-base setup required to start
Perfect for
- Independent pharmacies and chains launching
- Agencies delivering a branded medicine & OTC ordering experience with rider logistics
- Teams that want web + mobile apps from one codebase-shaped monorepo
- Pharmacies that want a differentiated, conversational ordering channel alongside traditional browse-and-cart
Try it now
Pharmaflow Web + Admin
Pharmaflow Customer App
Pharmaflow Delivery App
Demo accounts
Sign in on web or mobile (phone / password)
- Admin — 01700000001 / admin123
- Support — 01700000002 / support123
- Rider — 01700000003 / rider123
- Customer — 01700000004 / customer
Rotate or remove these credentials on your own deployment before going live.
What you get
- Customer web — catalog, categories, search, cart, checkout, prescriptions upload, account area, AI Order Agent & live support chat
- Admin panel — products, orders, users, finance/dashboard-style views, rider tooling, notifications
- Support & rider web surfaces — role-based access aligned with operations (see included routes)
- Flutter customer app — shopping flows against the same APIs as the web store, plus AI Order Agent tab, order popup checkout & persistent chat
- Flutter rider app — deliveries, COD / cash-in-hand style flows, maps-friendly UX patterns
- Checkout — cash on delivery for customers; environment template still documents optional gateway keys if you extend payments
- Maps & location — Google Maps integration where configured; geocoding helpers for addresses
- Auth — NextAuth-based sessions for web; mobile login API for apps
- Seed script — optional demo data (npm run seed) for local evaluation
Feature highlights — customer web
- Browse & merchandising — categories, searchable catalog, hero / promo slides (admin-configurable), product grids and specials (e.g. flash-style offers)
- Ordering — cart, authenticated checkout, COD-only payment path, delivery charge logic, saved addresses
- Location-aware checkout — address capture with map / pin and geocode-style helpers where API keys are set
- Prescriptions — dedicated upload journey for Rx-style orders tied into the same order flow
- Omnichannel entry points — WhatsApp and call-to-order tiles driven from store settings
- Account hub — order history, order detail, ongoing delivery visibility
- In-app support — floating chat experience linked to orders, threads for support vs delivery contexts
- AI Order Agent — conversational ordering: catalog search, in-chat order list, confirm order, prescription upload, and guest checkout; powered by your LLM API key
Feature highlights — admin & back office
- Operational dashboard — KPI-style snapshots, COD collection awareness, workload-oriented views
- Catalog control — medicines/products, imagery, pricing, discounts, categorization
- Orders — pipeline statuses, fulfillment hooks, rider assignment, map views where coordinates exist
- Customers & staff — user roster, roles (admin, support, rider, customer), access separation
- Finance & reporting touchpoints — dashboards and aggregates aligned with storefront orders
- Warehouse / inventory concepts — settings for stock behavior, thresholds, and operational flags
- Site configuration — branding-friendly store info, delivery fees, notification preferences, hero content, AI Assist settings (API key & chat readiness)
- Support from the desk — staff can engage customers with the same order-linked chat model
Feature highlights — support & rider (web)
- Role-scoped panels — support and rider web areas tailored to day-to-day dispatch and customer help
- Delivery coordination — status progression, handoff between operations and riders
- COD discipline — tooling to track cash collection against delivered COD orders
- Chat by context — separate support vs delivery chat threads per order where the product provides both
Feature highlights — Flutter customer app
- Phone-first shopping that hits the same APIs as the website — consistent catalogue and cart
- AI Order Agent — dedicated chat tab; the agent builds the order list from conversation; view order summary and confirm in-app; persistent chat history
- Authentication, profile, and token-based session patterns for mobile clients
- Checkout with cash on delivery, address capture, and optional map / location patterns
- Order tracking and account-level order history
- Prescription-friendly flows aligned with the web experience
- Configurable API base URL for staging, production, or emulator networking
Feature highlights — Flutter rider app
- Assignment-oriented UI for active deliveries and handoffs
- COD / cash-in-hand workflows and deposit-style reporting hooks (where implemented in API)
- Directions / maps integration patterns for last-mile navigation
- Delivery-side chat with customers for the handoff experience
- Theme and branding hooks suitable for white-label polish
- Unified backend — Next.js route handlers and shared Mongoose models for web + mobile
- Sessions & security — NextAuth on web; structured roles across surfaces
- Notifications & comms hooks — plumbing for SMS / WhatsApp-style alerts (provider keys are yours)
- Demo & staging comfort — seed script, demo mode flag, static documentation handbook in the download
- Future-facing toggles — optional HL7 / ASTM / FHIR-related environment switches for lab or interoperability experiments (see .env.example)
Tech stack
- Web: Next.js (App Router), React, Tailwind CSS
- API & server: Next.js API routes, MongoDB + Mongoose
- Mobile: Flutter (separate customer & rider projects in the repo)
- Optional / dev: HL7, ASTM, FHIR-related env toggles for interoperability experiments (see .env.example)
Hosting & requirements
- Node.js compatible with the bundled Next.js version — run npm install & npm run dev
- MongoDB connection string (MONGODB_URI) — Atlas or self-hosted
- Set NEXTAUTH_SECRET, NEXTAUTH_URL, and payment/provider keys as documented
- Flutter SDK current enough for the bundled app projects; set API_BASE_URL for device / emulator
Documentation & support
The download includes a static handbook at public/documentation.html (surface guides for Web / Customer app / Rider app + developer reference). Use the item comments or your support channel after purchase for setup questions.
Important notes
- Review .env.example before production; disable demo mode and lock down secrets.
- Drug / trade license, compliance, and payment provider approval are your responsibility.
Third-party services and additional costs
Important: this purchase covers the PharmaFlow source code only. Any third-party services the script can integrate with — including, but not limited to, Google Maps (Maps JavaScript API, Geocoding, Places), SMS providers, and payment gateways (e.g. SSLCommerz and any future gateway integrations) — require your own accounts, API keys, and paid plans. Their usage fees, subscription costs, transaction fees, and any compliance / KYC requirements are not included in the item price and are billed directly by those providers to you.