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

Good to know

• Photo upload sends a reference, not a file. In both apps the claim photo and the pickup bag photo send a reference string. The server has an upload endpoint, but there is no image-picker plugin in the apps. Add one to make photo upload real.
• Forgot-password uses an email code. The customer app resets a password with a one-time code sent by email, because the shared core has no reset route.
• There is no GPS, geocoder or push token. No location, address lookup or push plugin is in either app, so positions are demo coordinates and push is not wired. Add them for real routes and notifications.
• There is no deposit, by design. The customer is charged after the weigh-in. A cash booking is refused when two or more fees are unpaid, and a card customer's open fees are charged first.
• Refund locking uses the cache. Keep a cache store that supports locks (the shipped file store does). The atomic marker on each refund is what prevents a double gateway refund.
• The demo seed is 6,050 orders, not a large operation's volume.
• Payments, SMS and push are simulated by default. The simulated payment 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.
• The apps were not tested on physical devices. They build as debug Android packages and run on the iOS simulator.
• 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: Pegloom 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 customer, business and record in the screenshots is fictional. Install it with the demo data to try every role on your own server.