Line-haul bookings, without refreshing the portal.
CoreOps Vendor reads your bookings from the logistics portal every 2 minutes. Your team sees new requests, checks the route, and accepts them, without refreshing the portal over and over.
- Synced every 2 minutes
- Indonesian and English
- Light and dark mode
Updated 31 seconds ago
| Route | Vehicle | Standby | Acceptance Status | Action |
|---|---|---|---|---|
| Tamalanrea DC Kalawat DC | 40FCL | 17:41 | Pending | Accept |
| Benowo 3 DC Sunter DC | TRONTON (10WH) | 21:00 | Pending | Accept |
| Cimanggis DC Semarang DC | CDD LONG | 05:30 | Pending | Accept |
| Sunter DC Benowo 3 DC | TRONTON (10WH) | 08:15 | Pending | Accept |
The portal works. Watching it all day is the hard part.
Only the portal
- Refresh the portal again and again to catch new requests.
- Open each booking to see where it goes.
- A booking that leaves the portal is gone from view.
With CoreOps Vendor
- New requests appear on their own every 2 minutes.
- View Address shows the full route right in the table.
- Old bookings stay as history.
Follow each request from confirmation to completion
The dashboard uses the same four tabs as the portal, so nobody on your team has to learn a new flow.
-
1
Waiting for Confirmation
New requests from the portal. Check the route, vehicle, and standby time, then accept from here.
-
2
Waiting for Assignment
Accepted requests that still need a driver and vehicle.
-
3
Ongoing
Trips that are on the road.
-
4
Completed
Finished trips, kept as history.
Synced from the portal every 2 minutes
Only bookings that changed are fetched again. If the portal login expires, the dashboard says so, instead of quietly showing old data.
Accept without opening the portal
The Accept button sends the request straight to the portal.
Full route with addresses
View Address shows every stop with its province and city.
Choose which bookings are synced
Admins pick bookings by name prefix and creation date, and can re-sync everything with one button.
Filters that match the portal
Search by booking, station, vehicle type, driver, and date range, laid out like the portal.
History is kept
Bookings stay in your database after they leave the portal.
Admin and vendor accounts
Admins manage users and settings. Vendors work the bookings.
Indonesian and English, light and dark
Each person picks their own language and theme.
Bring your portal bookings into CoreOps
Create a vendor account. Once an admin connects the portal account, your bookings appear on the next sync.