What are the limitations of DEV3 Mollycot I should know before buying?

Good to know

• The demo data is small. It covers every booking status, cancellation policy, no-show, decline, expiry, missed visit, incident, walk pack and pending vaccine, but it is smaller than the history DEV3 first planned. It is not a large load-test data set, and it takes about 80 seconds to seed on MySQL.
• Payments and push are simulated by default. The simulated gateway works out of the box, so booking and paying need no keys. Stripe, Razorpay and PayPal drivers are included but were not run against real accounts. Real push and the optional realtime server were not exercised.
• Mollycot never charges a saved card. Extra costs such as a late pick-up or a vet bill are payment requests that the owner pays.
• Stripe refunds have no idempotency key yet. A gateway timeout after Stripe accepted a refund can be retried, so retries need buyer review before you go live with real card payments.
• The apps were not tested on physical devices. They build as debug Android packages and run on the iOS simulator. Each app was also run once against a live server through test files.
• Walk traces record only while the app is open. There is no background tracking, and a walk with GPS off shows "No trace recorded".
• Some things live in the apps, not on the web. Meet-and-greets are scheduled in the carer app, and weekly walk schedules and booking a single walk from a pack are in the apps. The apps pick images only, so vaccine PDFs are uploaded on the web. Reports are photos and text, with no video, and handover uses a six-digit code, not a signature.
• Updates refresh within about 15 seconds. The apps poll; there is no push-driven live view.
• A few admin rough edges. The walks-running view is a table, not a map. Suspending a carer does not cancel existing bookings, and review moderation blanks the text but keeps the stars.
• Use MySQL or MariaDB on a live site. The Pest tests run on SQLite, where row locks do nothing; the concurrency checks that prove the locking run on MySQL 8.
• Name: Mollycot is a working name checked by a web search only, not a trademark clearance. Check it before you launch under it.
• No hosted demo. Every owner, carer and pet in the screenshots is fictional. Install it with the demo data to try every role on your own server.