weapp-booking
Connect bookings, registration, and the visit itself.
weapp-booking is built for businesses that manage time, resources, and capacity. From choosing an experience to handling orders and check-in, each step of the visit has a clear record.
Follow the whole journey of a visit
For photography studios, craft workshops, businesses that offer timed services, and in-person events that need ticket types, capacity limits, and check-in.
Book or register
Choose a location, service resource, and available time, or select a ticket type and enter details for multiple attendees.
Confirm the order
Create an order with server-controlled pricing and capacity, hold unpaid places temporarily, and record the payment outcome.
Check in
Each attendee has a separate credential. Staff check visitors in and correct mistakes within their location permissions.
Handle follow-up
Manage rescheduling, cancellation, and refund requests, with order history and basic customer records.
Delivery covers a complete application
Customer interfaces, the management console, and the API share one order system. The delivery version, modules, and acceptance checklist are agreed in writing after assessment.
- Customer mini-program and H5
- Services and events, sign-in, configurable forms, bookings and group registration, order details, rescheduling, refund requests, and check-in credentials. The WeChat app uses Wevu, weapp-vite, and weapp-tailwindcss.
- Business management
- Manage locations, resources, services, events, tickets, orders, refunds, check-in, staff roles, and location permissions. Browse all customer, audit, notification, and historical refund records. Find refunds by location, handling status, or order keywords, and keep the browsing context after retrying the original refund task; settlement still needs verification. Export every order matching the current filters. Owners, administrators, and authorized managers can reschedule appointments that have not started, with a recorded reason.
- Payments awaiting verification
- Owners, administrators, authorized location managers, and finance staff can review payments awaiting verification within their location permissions and request another check with a required reason. Acceptance confirms receipt of the request, not receipt of funds. Missing payment configuration or channel results that still need verification, including refunds or reversals, leave records for manual review without marking payment as successful.
- Temporary unavailability
- Set a period of unavailability within a day for one staff member or venue when someone is away or a space needs maintenance. Owners, administrators, and authorized managers create or revoke these periods within their location permissions. Existing confirmed and unpaid bookings stay in place and can be reviewed for manual follow-up.
- Copy services and events as drafts
- Within the same location, copy a service or event into an unpublished draft, reusing its description, image, form, and business settings. For events, enter new start, end, and registration deadline times; all ticket configurations are copied too. Review and publish the draft before customers can book.
- Configuration templates for new instances
- Owners and administrators can export saved branding, business rules, and selected catalog entries for a new independent instance. Add images in the target instance and set new event times in its timezone. Review changes before importing; locations and resources remain disabled, and services and events remain drafts. Customer transactions, staff accounts, and provider secrets are excluded. Review retained public contact details and text before sharing.
- API and persistent data
- Capacity, temporary holds, idempotent orders, payment and refund states, background jobs, audit records, and persistent storage. The server validates amounts and permissions.
- Brand and form settings
- Configure the brand name, color, introduction, contact details, services, events, and registration fields. When settings are edited concurrently, stale saves are rejected and the local draft is kept for review before an explicit reload. Basic membership covers customer profiles and order history.
Agree the delivery model with your team
- Source licensing
- For teams with development capacity. Agree the modules, source scope, modification rights, and version maintenance, then use the product under the written license.
- Private deployment
- For businesses that need an independent environment. Review the server, domain, database, backups, and provider configuration, then agree deployment, integration, and handover.
- Brand and workflow customization
- Assess branding, forms, business rules, and integrations against the existing booking and registration flow. Ordinary settings saves preserve existing top-level brand extension fields and extensions on form fields whose identifiers stay unchanged. Custom structures that cannot be merged safely are rejected. Delivery documentation defines extension and upgrade boundaries; additional capabilities need their own scope, cost, and acceptance criteria.
Prepare the environment before deployment
- Your runtime environment
- Prepare an independent server, HTTPS domain, database, and backup strategy, with a named operations owner. Availability and recovery requirements belong in the deployment agreement.
- Your WeChat and payment accounts
- The mini-program AppID, permitted domains, privacy disclosures, and merchant payment capabilities must match the business. SMS and subscription messages use the customer’s provider configuration.
- Joint integration acceptance
- Verify real sign-in, payment cancellation and reconciliation, refund settlement, QR check-in, and message delivery in the customer environment before accepting the launch checklist.
Clarify licensing and service scope first
- An independent commercial product
- The weapp-booking source is maintained in a separate private repository. This website describes the product; source and deployment materials are delivered under a written agreement.
- Defined rights of use
- The operating entity, instance count, client-project delivery, modifications, redistribution, resale rights, and update or maintenance period must be confirmed in the license and service agreement.
- Costs agreed separately
- There is no public standard price yet. Source licensing, deployment, customization, and ongoing maintenance are scoped individually. Server, domain, SMS, payment, and other provider costs are confirmed separately.
Independent deployment first; hosted services later
The current focus is independent deployment with a guided handover. Multi-tenant SaaS, self-service subscriptions, and automatic provisioning are future directions. They are not available, and no launch date is promised.
Start with a concrete discussion of your business
Share your business type, location and staff count, booking or registration workflow, required mini-program/H5 interfaces, and existing accounts and infrastructure. These help us arrange a demo and agree the next step.
Arrange a demo and consultation