Cargo Management Demo
A cargo tracking and access interface separating public shipment lookup, customer accounts, and branch terminals.
Reference inspected . Screenshots show the available interface; sample records and figures are not verified operating results.
Project overview
The cargo demonstration offers three distinct entry points: consignment-number tracking, customer access, and branch-terminal access. Public copy explains pre-bookings and delivery tracking for customers and consignment/inventory workflows for branch staff.
Inspected the public consignment-number tracking form, customer sign-in, and branch-terminal entry. React and a Supabase client are present in the delivered frontend. Actual tracking events, branch inventory, and authenticated operations were not tested.
- Services / scope
- Management Systems
- Contributors
- Project-specific contributors not documented
The business problem
Customers looking for a shipment update should not have to enter a staff workspace. Cargo staff need a separate entry for branch inventory and consignment work, while customers need their own account context for bookings and delivery information.
Goals, requirements & constraints
- Keep public shipment lookup separate from staff access.
- Offer distinct customer and branch-terminal entry points.
- Present local language options across the public cargo interface.
Working constraints
- No customer or branch account was used.
- No consignment query was submitted and no shipment record was modified.
- Live tracking, location accuracy, delivery coverage, and shipment volume are not verified.
Discovery & available context
Reviewed the public tracking page and both sign-in panels. The customer entry describes parcel pre-bookings; the branch entry describes inventory, consignments, and status updates. These protected workflows remain publicly described scope.
Solution & documented scope
The interface separates public lookup from customer and branch access through persistent navigation. The tracking page accepts a consignment number; each account entry explains the work available to its intended audience.
Features & functional scope
- Consignment-number tracking form
- Separate customer sign-in and registration entry
- Separate branch-terminal sign-in
- Email or Afghan phone sign-in labels
- English, Dari, and Pashto controls
User experience & interface
The tracking form is the primary public action. Customer and branch access are labeled separately and retain the cargo identity, preventing the public lookup from competing with operational staff controls.
System architecture
Layers below show only the technology information currently documented for this project.
Technical implementation
Frontend
React is identifiable in the public bundle; tracking and account entry panels were inspected.
Integration
A Supabase client is included. Live tracking queries, schemas, and access policies were not tested.
Access boundaries
Customer and branch sign-in fields use distinct explanatory copy. Enforcement behind those forms requires authorized review.
Challenges & solutions
A project-specific challenge log has not been provided. Technical incidents, tradeoffs, and their resolutions can be added here when verified.
Results & outcome
The public deployment provides distinct interfaces for shipment lookup and two account audiences.
Delivery speed, operational volume, and tracking accuracy are not presented as measured outcomes.
Inside the interface
Captured interfaces are labeled with the screen and review context. Select an available screenshot to view it in detail.
Interface preview
Real interface screenshots are not currently available for public review. The cover artwork illustrates this project’s domain.
Technology stack
Frontend & interface
Backend
Project links
Public project and repository links have not been added.
Project status
A demonstration reference. Production use and final delivery are not claimed.
Have a similar business challenge?
Tell us what your business needs. We’ll help define the right next step.


