Custom Software
Meraki Textiles
Buyer orders and export documents on one system.
- Client
- Meraki Textiles (placeholder client)
- Industry
- Textile & Apparel
- Year
- 2025
- Services
- Custom Software, Web Applications, UI/UX Design
Overview
A Faisalabad home-textile exporter tracked buyer orders across WhatsApp, email and a shared drive. We built the order-to-shipment system that replaced all three.
Technology
- Next.js
- TypeScript
- Laravel
- MySQL
- AWS
- REST APIs
01 — Challenge
Challenge
Orders from European and North American buyers moved through sampling, approval, production and export documentation with no single record. Merchandisers rebuilt the same status update for every buyer email, and a missed approval could push an entire shipment past its window.
02 — Strategy
Strategy
We mapped the order lifecycle with the merchandising team first — the sampling loop is where the real complexity sits, not production. Because the buyers themselves were a source of delay, we scoped a buyer-facing portal into the first release rather than treating it as phase two, and designed the whole system to work on a phone from the factory floor.
03 — Solution
Solution
One order record carrying sampling rounds, approvals, production lots and export documents, with a buyer portal for status and approvals and a floor view for lot progress. Export paperwork is generated from the order rather than retyped, and every approval is timestamped against the person who gave it.
What we built
The parts that carry the workload.
- 01
Order lifecycle tracking
Enquiry, sampling, approval, production and shipment as one record, with the delivery window visible at every stage.
- 02
Sampling and approval rounds
Each sample version, buyer comment and approval captured with a timestamp, ending disputes about what was signed off.
- 03
Buyer portal
Buyers check status and approve samples themselves, which removed most of the daily status email traffic.
- 04
Production lot progress
Cutting, stitching and packing progress updated from the floor on a phone, visible to merchandising in real time.
- 05
Export documentation
Invoices, packing lists and shipping documents generated from the order record instead of rebuilt in a spreadsheet.
Screens
A look at the interface.
Order lifecycle board Buyer approval portal Floor progress capture
Results
What changed after launch.
- Buyer status emails
- −71%After the portal launch
- Average sample approval cycle
- 9 → 4 days
- Documents retyped by hand
- 0
- Systems replaced
- 3WhatsApp, email and a shared drive
Figures shown are illustrative placeholders for this sample case study.
“They understood the sampling loop better than the software we had been sold before. Our merchandisers stopped spending their mornings writing status emails.”
Let’s build
Have a project like this?
Tell us where you are now and what needs to be true in six months. We will map an approach and give you a realistic estimate.
Prefer email? info@saftasoft.site
