Skip to content

Recording where a shipment has got to

Six milestones, appended as they happen — the timeline your customer reads instead of phoning you.

2 min read

On this page

The six milestones

A shipment moves through a fixed sequence, and Shipina keeps it short enough that recording one is not a chore:

Booked → Picked up → In transit → Customs → Out for delivery → Delivered

The journey sits at the top of a booking, because "where is it" is the question a booking gets opened with.

The journey is the first thing on a booking, because "where is it" is the question people open a booking to answer.

Adding one

Pick the milestone, give it the date it actually happened — not the date you are typing it — and add a note if there is something worth saying. A vessel delay, a customs hold, a container number: the note is where the story goes.

Each milestone takes a date and an optional note.

Fixing one you got wrong

Staff can edit a recorded milestone's date and note, or remove it outright, from the timeline itself. Partners cannot: recording what they saw is the job you gave them a login for, and correcting the record is yours.

Changing the milestone's type is a remove followed by a fresh entry. That is deliberate — the type is what your customer was already told, so swapping it silently would leave their inbox saying one thing and the booking another.

Removing one really removes it, and the shipment falls back to whatever it had reached before. This matters more than it sounds: the timeline reads from the furthest step recorded, so a "Delivered" entered by mistake makes the booking say Delivered in the portal and in your bookings list until somebody takes it out. Adding a later, earlier-stage milestone will not undo it.

Nothing about a correction reaches your customer. They were told about the original, and they are not told it changed — the booking simply shows the truth next time they open it. Every edit and removal is recorded in the activity log under Settings, with who did it and when.

Dates do not have to go in order either. Recording "customs" on Tuesday for something that cleared last Friday is normal, and the timeline sorts by when things happened rather than when you typed them.

Who can record one

Staff with update permission on bookings, and your partners — a partner holding one of the three slots on a booking can record milestones on it from their own portal. That is the point of giving an agent a login: the person who watched the container clear customs is the person who should be writing it down.

Customers can read the timeline but never add to it.

What your customer sees

Every milestone you record shows up in the customer portal immediately, and as a notification there for the customer and for any partner holding a slot on the booking. Shipina does not email them about it — their portal is where the news lives, and that is the trade: you record it once, and the call asking where the cargo is does not come.