Stack and code access
Confirm the framework, language, backend, database, runtime, and required accounts. Check that the package actually delivers source code rather than only a hosted account or a front-end mockup. Ask whether the release includes the migrations and configuration needed to run it.
Data and access control
Understand where customer and appointment data will live, who controls the database, and how staff, admins, and customers are authorized. Review server-side validation and database access policies in the source; don't infer security from a login screen or a product description.
Scheduling completeness
Inspect service and staff configuration, availability, time-zone handling, calendar, appointment status, and conflict prevention. Determine whether the source supports the required appointment duration, buffers, cancellation, rescheduling, and capacity rules. Verify every must-have in the actual demo or docs.
Deployment and operation
Check documentation, migration instructions, required environment variables, hosting assumptions, email/notification dependencies, backups, and maintenance expectations. Identify every account or integration the buyer must supply. A deployment configuration is not managed hosting or an installation service.
Responsiveness, license, and exclusions
Use the live demo on desktop and mobile. Read the marketplace license before client delivery, multiple projects, resale, or redistribution. Confirm whether custom integrations, migration, support, updates, and setup services are included rather than relying on assumptions.
How BDS fits this checklist
BDS v1.0.3 is a downloadable Next.js appointment-booking source package using React, TypeScript, Tailwind CSS, Supabase, and PostgreSQL. The current Codester listing is $104 USD Regular License ($312 USD Extended License); other marketplaces may differ in price and license. It includes a customer booking experience, services, staff, customers, appointments, availability, calendar, enquiries, admin screens, migrations, and documentation. Buyers supply their own hosting, domain, and Supabase project, configure the source, and deploy it. The ZENO demo is not transferred. Marketplace terms govern permitted use.