Is there anything DEV3 Shopnest does not do?

Good to know

• Payments: the default gateway is a simulated one. Stripe, PayPal and Razorpay drivers are included but were never tested against live accounts; test each in its sandbox before you take real money.
• SMS and push: one-time codes and SMS go to the log until you configure Twilio or Vonage, and push is simulated until you add FCM or APNs keys. Neither was tested with a live account.
• Mobile apps: the apps have not been tested on physical devices. The card web view, tel: links and PDF or download links were not exercised inside the apps, and the real-backend checks cover the main shopping flow rather than every edge case (COD refunds, late-payment refunds, order expiry and download locks are covered by the Laravel tests, not by the app smoke test). Guest flows in the app are covered by widget tests against the built-in mock only.
• Delivery map: the live courier map uses simulated GPS. There is no courier integration.
• Languages and currency: Arabic covers the interface only; catalogue text stays in the language you entered it. There is one store currency and no currency display switcher.
• No exchanges: a return can be refunded to the original payment or to store credit; exchanges are not built, so the customer reorders.
• Cron is required: without the scheduler, unpaid card orders are not cancelled and keep their stock reserved, and cart recovery messages are not sent.
• Demo mode wipes data: never leave DEMO_MODE=true on a live store; it reloads the demo data nightly.
• Performance: the Lighthouse figures above hold with gzip or brotli turned on in your web server; without compression the home page scored 69 in our run.
• Single store only: one merchant, one currency, no vendor accounts. Demo product images are flat tinted glyphs on a soft backdrop; uploaded photos replace them in live mode.
• Flutter apps need the Flutter SDK to build; the download contains source, not store-ready binaries.