LogisticsWindows app
Shipment Exception Inspector
Load the daily shipment export. Four rules flag stuck, failed, returned parcels. Hand the list to CS. Complaints drop by half.
The problem
Logistics teams watch thousands of parcels daily. Stuck 48+ hours, failed delivery three times, returned to sender — if nobody catches them, complaints and refunds pile up.
The solution approach
A desktop tool. Drop in the daily export. Four rules flag exceptions. One click exports a severity-ranked list for customer service.
What you will end up with
- Home with three panes: Import / Exception list / Rule settings.
- After import: totals of all / exceptions / normal.
- Four built-in toggleable rules: stuck >= 48h, attempts >= 3, returned, keyword match.
- Exception list sorted by severity; phone masked (138****1234).
- One-click Excel export for CS.
- Time windows: today / 3 days / 7 days.
Ready-to-use prompt
You are a senior engineer experienced with Windows desktop apps. Build a local Windows tool for an e-commerce logistics / customer service team. Non-developer user.
[Goal]
Surface exception shipments in minutes, not hours. Hand them to customer service before customers complain.
[Platform & Stack]
- Windows 10/11 desktop app
- Electron + React + TypeScript
- SheetJS for Excel/CSV
- Local SQLite rolling 30-day history
- Offline; ship Windows .exe installer
[Column Mapping]
Handle common headers (Chinese + English): order id, carrier, tracking id, recipient name, recipient phone, current status, last update time, delivery attempts, exception tag. Remember mappings.
[Core Features]
1. Home: Import / Exception list / Rule settings.
2. Import: multi-file drop; auto-detect encoding (UTF-8/GBK). Show totals.
3. Rules (toggleable + tunable):
- A: last update >= N hours (default 48) AND status not delivered/returned.
- B: delivery attempts >= N (default 3) AND not delivered.
- C: status contains return/reject/exception keywords.
- D: user-defined keywords.
4. Exception list sorted by severity; fields: order id, carrier, masked phone, reason, hours stuck, recommended action.
5. Time windows: today / 3 days / 7 days with historical compare.
6. Export to Excel as "exceptions-YYYY-MM-DD.xlsx".
[Privacy]
- Fully offline.
- Phone masked by default; "reveal" behind a button, lightly logged.
- On quit, ask whether to clear today.
[Visual Style]
- Dashboard clarity with soft dividers.
- Severity red/yellow/blue.
- Follows system dark mode; bilingual.
[Robustness]
- Manual guidance on mapping failures.
- Batch processing for > 50k rows with progress.
- Preserve parsed data on error.
[Delivery]
1. Structure + wireframes for list / exceptions / rules.
2. Phase 1: import + detection + list. Phase 2: rule customization + time windows. Phase 3: export + history compare.
3. Package .exe; 500-word user guide.
Start with structure and wireframe.After copying
1
Open Codex Desktop and create a new project
2
Paste the prompt and send
3
Wait for Codex to finish; tweak company names, column names, button text as needed