Development criteria
It turns the relationships and states of shipments, hubs, and statuses, key user flows, recovery paths, and completion conditions into an implementable specification.
LOGISTICS PROMPTS
Logistics and delivery website prompts
How should a Logistics and delivery site be designed? Model the relationships and states of shipments, hubs, and statuses first, then treat status clarity and exception handling as a primary risk. Each service guide below combines an implementation specification with design standards.
- Primary goal
- shipment and delivery tracking
- Core entities
- shipments, hubs, and statuses
- Design risk
- status clarity and exception handling
10 REAL SERVICES
Logistics and delivery · 10 real services
Development prompts and DESIGN.MD for 10 real services designed around shipment and delivery tracking.
ANSWER GUIDE
Logistics and delivery How to choose a prompt
Choose the service whose core screen and repeated behavior most closely match the product you are building. Apply only information priority and state design, never the reference brand assets.
Design criteria
Start from A tracking interface for Logistics and delivery, centered on shipments, hubs, and statuses, with a [reference] brand impression led by [color], while avoiding the original logo, proprietary copy, images, and pixel-level layout.
Risk to validate
Treat status clarity and exception handling as a primary design risk and define loading, empty, error, partial-data, and success states.