Concept demo prepared for LumeCare by AtlasDev · Sample data · No real orders or payments
You raised six concerns about the first proposal. Each one below links to a part of this demo you can try yourself.
“The stack and approach should fit current and future requirements.”
This demo is built with Next.js and TypeScript. Each payment gateway and each courier is a separate module behind one shared interface, so adding one later means adding a module, not rebuilding the store.
“TCS, Leopards and PostEx integration is important for daily operations.”
Staff book the courier from the order. The tracking number comes back on its own and the status follows the parcel. A rejected booking never loses the order, and a returned parcel puts the stock back.
“Bundle offers need component-level inventory management.”
A set has no stock of its own. Selling one set reduces every product inside it, the set stops selling when any product runs out, and a cancelled order returns each quantity.
“One payment gateway is not enough. Flexibility is needed for the future.”
Checkout offers Cash on Delivery, JazzCash, Easypaisa and cards. An online order is marked paid only after the gateway confirms it, and a failed payment creates no order.
“Analytics, Meta Pixel, customer accounts and loyalty should be included.”
The store sends view, add to bag, checkout and purchase events with the order value in PKR. Customers can see their orders and earn points when an order is delivered. Guest checkout stays available.
“Important features outside the scope may lead to extra costs later.”
Everything shown in this demo is listed inside the scope of the revised proposal. Add-ons you may want later, such as another courier or gateway, get a fixed price in writing before you sign.