Telente Logistics
A logistics platform with public package tracking, careers and applications, newsletter capture, and an admin dashboard behind OTP-secured authentication.
- 13
- Public pages
- 6
- Data models
- OTP
- Admin second factor
- 3
- Password flows
- Role
- Author
- Year
- 2026
- Status
- Private
- Type
- Logistics platform
01Overview
Telente Logistics is a full-stack platform covering the public side of a logistics business — marketing pages, package tracking, contact and newsletter capture, careers and job applications — and the admin dashboard that operates it.
Package tracking is the piece customers actually use, and it is the one that has to work without an account: a tracking number typed into a public page, resolving to a status without exposing anything about the shipment beyond what the person holding the number should see.
Admin access is protected by OTP alongside a full credential lifecycle: forgot, reset and change password.
02The problem
Public tracking endpoints are enumeration targets. Sequential tracking numbers plus an unauthenticated lookup is a way to walk every shipment a company has ever handled, including names and addresses.
Careers pages are the other overlooked surface — they accept file uploads from anonymous users, which is the same threat model as an upload form with none of the attention.
And a logistics admin dashboard controls where things go. Password-only access on a panel that can redirect a shipment is not proportionate to what it can do.
03Architecture
- 01
Public tracking
Tracking resolves a number to a status for an unauthenticated caller, kept deliberately narrow in what it returns.
- 02
OTP-secured admin
Admin authentication requires a second factor, with forgot, reset and change password flows built as first-class paths rather than as an afterthought.
- 03
Careers and applications
Job listings with an application pipeline, so submissions land in the system where they can be reviewed rather than in an inbox.
- 04
Capture surfaces
Contact and newsletter capture persisted alongside the rest of the operational data.
04Key decisions
Second factor on the operations panel
The dashboard can change where a package goes. That is a physical-world consequence, and it justifies friction that a content admin would not need.
Explicitly proprietary
The repository states in the README, the licence and the security policy that it is not free to use. Client work with an ambiguous licence is a problem deferred, not avoided.
Password lifecycle built up front
Forgot, reset and change are the flows that get retrofitted badly under pressure after someone is locked out. Building all three at once means one consistent token model instead of three improvised ones.
05Stack
- React
- Vite
- TypeScript
- Node.js
- Express
- MySQL