Nijin Contact

Trackwise Where Is My Parcel?

Web · Prototype

Parcel tracking for a shop and its customers. Paste a tracking number from any of 14 carriers and get one timeline back, even when the parcel changed hands halfway.

A prototype build: a running React app, designed inside Razorpay’s Blade design system rather than a house style of my own.

The Trackwise workspace home: parcels needing attention, arriving today, in transit, and the latest activity
The workspace home.

It opens on what needs a person, not on a list of everything.

The part a shopper sees

The landing page has one job. The marketing that used to sit under the hero moved to the tracking page, after the answer, where it is finally persuasive.

The Trackwise landing page: a hero and a single tracking field
Landing.

Status first. What you can share is deliberately less than what you can see.

The public tracking page showing status, then share options
The public tracking page.

The part a merchant lives in

The counts are the point. Needs attention: 29 is a to-do list, not a filter label.

The parcels list with scope tabs, filters, quick filters and pagination
All parcels.
The needs-attention scope, filtered to parcels with exceptions and predicted delays
The same table, scoped to trouble.

Eleven scans across two carriers, told once. The handover is a fact on the page rather than a gap in the story.

A parcel detail page with a merged cross-carrier timeline, route rail and shipment facts
One parcel.

Deflection, carrier performance, prediction accuracy, and the lanes worth fixing.

The analytics screen: WISMO deflection, carrier performance, prediction accuracy and lanes worth fixing
Analytics.

Paste a block of tracking numbers and watch the carriers resolve as you go.

The add-parcels screen with single, bulk paste and automatic options
Adding parcels.

The plumbing

Every alert shows the channel it went out on, because did the customer actually hear about this is the only question that matters here.

The alerts screen, grouped by day, showing which channel each alert went out on
Alerts.

The failed attempt, and why it failed, is the whole reason this screen exists.

The webhooks screen with endpoints and delivery attempts
Webhooks.

A connected integration and a broken one look genuinely different.

The integrations screen showing inbox, store, channel and developer connections with real states
Integrations.

Money, and making it theirs

Every limit on one page, so the awkward questions get answered here rather than in a support thread later.

The pricing page with a full comparison table and every limit stated
Pricing.
The billing settings screen with plan, quota meters and invoices
Billing, with the quota meter.

A merchant’s own palette and domain, previewed live. One of the few places the design system needed something new.

The branded-page builder with a live preview of the merchant’s tracking page
The branded-page builder.

The parts that came from Blade switched themselves. The parts I built are where the work was.

The workspace home in dark mode
Dark.