Reference deployments showing how TikTrake handles photo-based parcel intake, shipping-mark matching, container consolidation, transshipment routing and multi-tenant warehouse isolation.
These are reference deployments: documented operating profiles and the exact TikTrake workflow each one uses. They describe platform behaviour, not named customer accounts.
Cloud warehouse in Guangzhou serving Gulf and North African importers
Photo-based intake replaces manual parcel logging
The problem
A cloud warehouse receiving several hundred Chinese domestic parcels a day identified each box by reading its label by hand and typing the shipping mark, phone number and weight into a spreadsheet. Mistyped marks produced parcels nobody could claim.
What TikTrake does
Warehouse workers photograph every incoming label in TikTrake. OCR extracts the shipping mark, recipient phone, courier tracking number and weight, then matches the parcel to the customer that owns that mark. Anything it cannot match is filed in an 'unknown parcels' queue for review instead of being lost.
Outcome
Intake becomes one photo per box, and every parcel is either attached to a customer or visible in a review queue — no silent losses and no shared spreadsheet.
- One photo per parcel instead of manual data entry
- Unmatched boxes queue for review rather than disappearing
- Customers see their own parcels the moment intake completes
Consolidator in Yiwu shipping LCL and FCL to East and West Africa
From loose cartons to a container with one manifest
The problem
Consolidating dozens of customers' cartons into a single container meant rebuilding the manifest by hand each time, and customers kept asking which container their boxes ended up in.
What TikTrake does
Matched parcels are packed into an LCL or FCL container inside TikTrake. The container carries its own number, seal, port pair and manifest, and every parcel inside inherits the container's ocean status automatically.
Outcome
The manifest is a by-product of packing, and each customer's dashboard shows their carton, its container and the vessel carrying it.
- Container manifest generated from the packing step
- Parcel status inherits container status automatically
- Customers self-serve container answers instead of messaging the office
Forwarder moving South China to Red Sea and East African ports
Transshipment legs drawn individually, never as one straight line
The problem
Routes with a transshipment call were shown by most trackers as a single line between load port and discharge port, so a box waiting at a hub looked like it was mid-ocean and progress percentages were wrong.
What TikTrake does
Every ocean route in TikTrake is an ordered sequence of legs — origin port, each transshipment port, destination port. Completed, active and pending legs are drawn separately with a stopover marker at each hub, and progress is calculated per leg.
Outcome
A shipment sitting at a transshipment hub is visibly at that hub, and the arrival estimate reflects the leg actually in progress.
- Per-leg progress instead of one great-circle arc
- Stopover marker at every transshipment port
- Carrier detected from the container number prefix
Operator running several warehouse branches under one account
Every warehouse is its own isolated tenant
The problem
Running more than one branch on shared spreadsheets meant any staff member could see, and edit, another branch's customers and parcels.
What TikTrake does
Each warehouse is a tenant keyed by warehouse code. Managers see only their own warehouse, workers only their assigned warehouse, and customers only their own parcels — enforced at the database level rather than in the interface.
Outcome
Branches operate independently under one operator, with role-scoped dashboards for manager, worker and customer.
- Database-level tenant isolation by warehouse code
- Three role surfaces: manager, worker, customer
- Workers and customers included at no extra cost
