Orders and customer enquiry imports stay in this browser (fst-ecom). Not uploaded.
What is Orders & Customer Enquiries?
Import an enquiry JSON from the portable storefront or a WhatsApp/email file, convert it to an owner-recorded order, apply stock once and record partial manual payments. Paid means manual_recorded — not bKash, Nagad or card settlement. Cancel restores stock. Customer forms on another device do not write your IndexedDB. Duplicate imports use idempotent client_op_id.
Key features
- Enquiry JSON import
- Convert to owner-recorded orders
- Idempotent stock apply
- Manual / partial payments clearly labelled
- Cancel restores stock; CSV reports
Popular uses
- Turn a WhatsApp order note into a local order
- Mark paid after you saw the money, not before a gateway webhook
- Export a simple order CSV
Supported formats
Enquiry JSON in; CSV reports out. No automatic payment provider.
Troubleshooting
- Stock applied twice Orders use client_op_id; a true duplicate import should not deduct again.
Also known as: Manual order manager, Enquiry import, WhatsApp order log.
How it works
- Import an enquiry JSON from the portable storefront download or WhatsApp flow.
- Convert to an order, apply stock once, record partial manual payments.
- Cancel restores stock. Export CSV reports. No automatic bKash/Nagad/card gateway.
FAQ
Does a customer form write into my IndexedDB?
No. Cross-device requires file import, WhatsApp/email, or a real backend.
Is paid status a gateway settlement?
No. It is owner-recorded / manual_recorded only.
Duplicate imports?
Orders use idempotent client_op_id; stock applies once.