Delivery tracker

Q: What is the Delivery tracker block made of?

6 parts: order header with a dot status tag and a copy button for the tracking number; grey done discs with an ink check on an ink rail; the current step a flat brand node inside a progress arc; upcoming step dashed; time and place on each; and delivery notes in a sunk card with an inline Edit. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.

Q: Is the Delivery tracker block responsive?

Yes. It is drawn at 520px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.

Q: Is the Delivery tracker block accessible?

It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.

Q: How do I add the Delivery tracker block to my project?

It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Delivery tracker block to this page.”

Delivery tracker is a Timeline block from Orvain UI, built for React and Vue with a matching Figma frame.

Best for

Orders, shipments and any process with done, current and upcoming steps

Anatomy

Order header with a dot status tag and a copy button for the tracking number · grey done discs with an ink check on an ink rail · the current step a flat brand node inside a progress arc · upcoming step dashed · time and place on each · delivery notes in a sunk card with an inline Edit

MCP

Order #20418

3 itemsNorthwind

On the way

Done: PackedThu 5 Nov, 16:05
Northwind studio, Rotterdam
Done: Picked upToday, 08:10
Depot 4, Rotterdam
In progress: On its wayArrives 11:40
Van 12, now on Biltstraat
45% of today’s route, 5 stops before yours
Coming up: Delivery11:20–12:00
Oudegracht 112, Utrecht
Delivery notes
- Signature needed
- If no one is in, leave it with the neighbour at no. 114

In the Orvain Library

Get Delivery tracker for your product

The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.

React
Vue
Figma frame
Orvain MCP

Get all access How the MCP works

About this block

Part of Timeline

What’s inside

06parts

The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.

Order headerwith a dot status tag and a copy button for the tracking number
Grey done discswith an ink check on an ink rail
The current step a flat brand node inside a progress arc
Upcoming step dashed
Time and placeon each
Delivery notesin a sunk card with an inline Edit

Responsive behaviour

520 px

Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.

1440pxDesktop · 12 columns

When to use it

Where Timeline earns its place

Reach for Timeline

An audit trail, where the question is who did what and when.
A discussion whose replies only make sense beside the text they quote.
A day view of work, mixing what has been done with what is still open.
Feeds where automated events sit among human ones and the difference has to be visible.

Reach for something else

A list of things still to do. Those sort by priority and owner rather than by time, which makes them a task list.
Machine logs at volume. A virtualised table with columns and filters beats a rail you have to scroll.
Work with durations and overlap. A rail shows order only; a calendar or a Gantt chart shows length and collision.

Notes for AI

1 line

Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.

Add the Orvain “Delivery tracker” block to this page: order header with a dot status tag and a copy button for the tracking number, grey done discs with an ink check on an ink rail, the current step a flat brand node inside a progress arc, upcoming step dashed, time and place on each, delivery notes in a sunk card with an inline Edit.

Works in

Connect the MCP

Questions about Delivery tracker.

What is the Delivery tracker block?

Delivery tracker is a Timeline block from Orvain UI, built for React and Vue with a matching Figma frame. Best for orders, shipments and any process with done, current and upcoming steps.

What is the Delivery tracker block made of?

Is the Delivery tracker block responsive?

Is the Delivery tracker block accessible?

How do I add the Delivery tracker block to my project?

When should I not use a Timeline block?

Previous← Attachment events NextDelivery ETA →

More Timeline blocks

All Timeline

November 2026 · 0 of 4 done

Friday, 6

10:30 AM

Mia ChenDesign

Token audit before the release

Ran the audit before the release. Every surface, border and content value resolves from one place now; the three that did not are in the write-up below.

12:30 PM

Release prep, four tasks

1:30 PM

Noah ParkEng

What the audit changed

Three values were still written as hex in the block files rather than read from the tokens, so a change to the palette moved most of the system and left those three behind.

Two were exact matches for a token that already existed, which made them a rename with no visual change at all. The third was four points lighter than anything in the scale.

That one goes to the secondary content value, the nearest thing the scale holds. It reads a shade darker on a subtle surface, and it passes at twelve point where the old one did not.

The audit is attached. Nothing in it moves a resting measurement, so the pages that already sign off stay signed off.

token-audit.pdf84 KB

Day checklist

A day of work: what happened when, what is still open, and who did it

November 2026 · 0 of 4 done

Friday, 6

10:30 AM

Mia ChenDesign

Token audit before the release

Ran the audit before the release. Every surface, border and content value resolves from one place now; the three that did not are in the write-up below.

12:30 PM

Release prep, four tasks

1:30 PM

Noah ParkEng

What the audit changed

Three values were still written as hex in the block files rather than read from the tokens, so a change to the palette moved most of the system and left those three behind.

Two were exact matches for a token that already existed, which made them a rename with no visual change at all. The third was four points lighter than anything in the scale.

That one goes to the secondary content value, the nearest thing the scale holds. It reads a shade darker on a subtle surface, and it passes at twelve point where the old one did not.

The audit is attached. Nothing in it moves a resting measurement, so the pages that already sign off stay signed off.

token-audit.pdf84 KB

Now·2:05 PM

4:30 PM

Ava Reid, Noah Park · planned

Release cut

Tag 4.2.0 once the audit is in and the changelog is signed off.

Day so far

A live day: what has happened up to now and what is still planned

November 2026 · 0 of 4 done

Friday, 6

Token audit before the release

Ran the audit before the release. Every surface, border and content value resolves from one place now; the three that did not are in the write-up below.

Mia ChenDesign

What the audit changed

Three values were still written as hex in the block files rather than read from the tokens, so a change to the palette moved most of the system and left those three behind.

Two were exact matches for a token that already existed, which made them a rename with no visual change at all. The third was four points lighter than anything in the scale.

That one goes to the secondary content value, the nearest thing the scale holds. It reads a shade darker on a subtle surface, and it passes at twelve point where the old one did not.

The audit is attached. Nothing in it moves a resting measurement, so the pages that already sign off stay signed off.

token-audit.pdf84 KB

Noah ParkEng

Day by slot

A long day to scroll: the time you are reading stays pinned

Date and mention

Thread history: the day it happened and who was pulled in

File and call

Audit trails: the upload and the booking, each with its actor

Task and reaction

Team activity: assignments, reactions and the system's own notices

Attachment events

File history: an event plus the documents it produced, each one ticked off as reviewed

Delivery ETA

Tracking pages where the first question is how long until it arrives

Delivery day

Same-day deliveries and any journey where the time between steps matters

The Orvain Dispatch

Premium components,
free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.