Table · reads shipment
Deliveries
Shipments and status.
Rows and columns, sortable and filterable.
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
Tracks the physical object moving, which is what a customer is asking about.
Inbound and outbound together, because when will it arrive is the same question either way.
Answers where is my order without a person, from the tracking reference on the row.
How it works
- 1
Shipments are recorded outbound and inbound in the same table, because when will it arrive is the same question either way.
- 2
The agent answers where is my order from the reference and status without a person.
- 3
An inbound shipment stuck in customs sits next to the outbound ones and is noticed.
- 4
A shipment with no reference yet is still a row, with the reason it has none.
Best for
Comparing many records across many fields.
Not the right choice for
A phone. A table is the first thing that stops working narrow.
What a row holds
Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.
| Field | Type | Filled from |
|---|---|---|
| Referencerequired | text | The tracking reference, which is what a customer quotes. |
| Contentsrequired | text | What is in it, linked to an order where one exists. |
| Carrierrequired | text | Who has it, including Freight or Awaiting payment as honest states. |
| Statusrequired | text | Where it has got to, in the carrier words rather than a normalised code. |
| Expected | text | When it should arrive, so a late one is visible. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- No carrier integration. Status is what somebody or the carrier page last said.
- No automatic tracking updates.
- No proof of delivery capture.
- Statuses are free text, so two carriers wording cannot be compared.
Before it works
What you have to provide, if anything.
- Nothing.
- Pair with Orders so a shipment is linked to what was sold rather than described again.
In practice
A shop shipping daily and receiving green coffee monthly.
“Where is order 1843?”
What the agent built
A delivery row with the carrier, the reference and the current status.
What changed
The tracking question stopped reaching a person. The inbound shipment stuck in customs was spotted in the same table, four days early.
Better with
These do a different job on the same data. An agent can have all of them.
Things are sold and then have to be prepared, shipped or collected, and several are in flight at once.
Someone travels between several places in one run and the sequence affects how long it takes.
You depend on other businesses to deliver, and their lead times shape your own commitments.
Who uses this page
Logistics company
Answers “where is it” without a phone call, and takes bookings while the phones are busy.
Florist or bakery
Takes custom orders properly — date, size, colours, message — without a queue forming.
Trade show or exhibition organiser
Handles exhibitor logistics and visitor questions without a stand-build inbox.
Questions
What data does the Deliveries page use?
It reads shipment records the agent has collected. Shipments and status. Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a table the wrong choice?
A phone. A table is the first thing that stops working narrow. It is best for: comparing many records across many fields.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in Places & logistics
- Oberkampf — 48 rue Oberkampf, 75011
- Marché des Vosges — Place des Vosges, 75004
- Café Bellevue — 12 rue de Charonne, 75011
Map / locations
Pinned places.
The Long Room
80 standing, 50 seated
Open, pillars
Atelier, 2nd floor
24 seated
Workshop, benches
Courtyard
120 standing
Outdoor, covered half
Meeting room
10 seated
Boardroom, screen
Venues
Candidate locations.
14–16 Oct
Lyon
TGV 06:52 from Gare de Lyon
16–18 Oct
Turin
Train, 4h, change Chambéry
18–20 Oct
Milan
Train, 1h50
20 Oct
Return
Flight MXP–CDG 19:40
Travel plan
Segments of a journey.
09:00
Coffee and briefing
Oberkampf
10:30
Roastery tour
Atelier Nord
12:30
Lunch
Café Bellevue
15:00
Cupping session
Oberkampf
Itinerary
Day-by-day plan.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free