I am building a unified logistics platform that connects four distinct user groups—Customers, Shipping Companies, Farmers and Restaurants/Cafés—to streamline the movement of fresh agricultural products. Each role needs its own dedicated dashboard, secure sign-in and tailored tool-set: • Customers must be able to place orders, track every shipment in real time, review current and historic orders, consult their full payment history and browse available shipping companies before committing to one. • Shipping Companies need tools to accept and manage incoming shipments, update live shipment status, drill into order details and view a constantly updated directory of suppliers (farms, agricultural wholesalers and restaurants/cafés). • Farmers and Restaurant/Café partners will require simplified order-handling screens so they can list produce, confirm fulfilment, print shipping labels and monitor delivery progress once a carrier is assigned. Core expectations – Responsive web app (mobile-first; native apps optional if it speeds up adoption). – Clean REST or GraphQL API so future services—such as route optimisation or IoT cold-chain sensors—can be plugged in with minimal rework. – Real-time status updates via websockets or similar push technology; customers should never have to refresh a page to see progress. – Role-based access control, GDPR-compliant data handling and straightforward onboarding flows. – Source code in a public-facing Git repository, with clear README and deployment scripts. Acceptance criteria 1. A tester creating an account for any role can complete the primary actions above without console errors. 2. Shipment status changes made by a Shipping Company reflect on the Customer side in under five seconds. 3. Order, payment and shipment histories persist after a full database restart. Hand-off materials will include: running demo on a cloud instance, database schema, API documentation (Swagger or similar) and brief user guides for each role.