Loading the page. Nothing has gone wrong.
Portals
Customers and carriers, self-serve
Two portals on their own login, each showing exactly what belongs to it — and nothing they submit touches your records until your staff apply it.
- “Where is my container?”
- “Send me the POD.”
- “What do I owe you?”
All three have exact answers already sitting in the load record. All three currently cost somebody twenty minutes and a search of their sent items.
Two sides
What each side gets, and nothing beyond it
Scope is applied where the query runs, so it is not a filter a crafted URL can step around.
Customer portal
Their containers, and only theirs.
- ShipmentsEvery container of theirs, its status, dates and stops.
- SearchBy container, booking, or their own internal reference.
- TrackingThe same milestones your desk works off.
- Wire detailsRemit-to and bank details from your company profile.
- Payment viewInvoiced, paid, open.
- StatementsAny date range, as a PDF on your letterhead.
- DocumentsPODs, invoices, delivery orders, the arrival notice.
Carrier portal
The loads you gave them — with the remit-to that actually applies.
- Assigned loadsThe loads assigned to them. Not the board.
- SearchTheir own loads, by container or load number.
- Tracking updatesPosted onto the same feed your desk reads.
- POD uploadFrom the phone at the dock, on the right load first time.
- Invoice submissionAgainst a completed load, into the approval queue.
- Payment statusTheir terms, and the factoring redirect if there is one.
- ConfirmationsRate cons, carrier confirmations, delivery orders.
- AppointmentsPickup and delivery windows, acknowledged in one tap.
MSMU 461 5308IN TRANSIT
AR-0431 · Houston → San Antonio · ETA 13-SEP
TCLU 772 9140AT PICKUP
AR-0433 · LFD 14-SEP · chassis assigned
MSDU 318 4472SSL HOLD
AR-0434 · advance outstanding · not released
Open balance$ 26,741.25
60 + days$ 2,105.75
STATEMENT · ANY DATE RANGE
Downloads on your letterhead, with your MC docket and bank details.
AR-0431ASSIGNED
MSMU 461 5308 · pickup 12-SEP 06:00 · acknowledged
AR-0422AT DELIVERY
TGHU 550 9012 · POD upload available
Rate confirmationRC-0417 · SIGNED
Payment statusREMIT TO FACTOR
SEABOARD FUNDING LLC · net 30 · due 09-OCT-26
UPLOAD POD · SUBMIT INVOICE
Both arrive as submissions. Neither changes a record on its own.
An appointment edited after the carrier last acknowledged it goes back to unacknowledged — so a time changed at four in the afternoon does not look agreed just because it once was.
The approval queue
Nothing goes live until your staff apply it.
A portal that writes straight into production data is a way of letting two hundred people outside your company edit your records.
- 07:52Awaiting decision
POD uploaded
Carrier side
AR-0420 · 2 pages
- 08:14Awaiting decision
Tracking update
Carrier side
AR-0422 · At delivery
- 08:31Awaiting decision
Document request
Customer side
MSMU 461 5308 · invoice copy
- 09:03Awaiting decision
Appointment acknowledged
Carrier side
AR-0431 · 12-SEP 06:00
- 09:20Awaiting decision
Contact details changed
Carrier side
MC 884120 · phone
A POD, an invoice, a tracking update, an acknowledgement, a change of contact details — each becomes a submission attached to the record it concerns, with who sent it and when. Staff apply it or reject it with a note, and the decision is audited.
It is the same queue that holds new customers, new carriers, credit requests and payable requests. One place where everything waiting on a human decision waits.
Portal control
Every switch, per side, in your hands
Turning one off removes the capability on the server, so a bookmarked page gets nothing rather than a hidden button.
Customer side
On
- View shipments
- Search
- Wire & remit-to
- Payment status
- Statement of account
- Documents
Off
- Rate confirmations
Carrier side
On
- Assigned loads
- Search
- Tracking updates
- POD upload
- Payment status
- Statement of account
- Rate & load confirmations
- Appointments
Off
- Invoice submission
Boundaries
Two portals, one set of records.
A separate sign-in surface
Portal users are not staff with fewer menu items. They are their own accounts, tied to one customer or one carrier.
Their records only
Scope is applied where the query runs, so a guessed URL returns nothing rather than somebody else’s container.
Proposals, never mutations
There is no path from a portal into a production record that does not pass a member of your staff.
One brokerage’s data, always
Every record carries its organisation, enforced by the database as well as the application.
Elsewhere in the platform
Book a demo
See it against your own containers.
Forty minutes, no slides. Bring one live container and one messy invoice.
What happens on the call
- You send one container number and one invoice before the call.
- We load them in live — your lane, your customer, your accessorials.
- We run the gates against a carrier you choose, and show you what refuses.
- You keep the generated paperwork, whether or not you buy.