Indopaket Web Platform Redesign
UX Engineer · Product Team Lead
A closer look at finding a store, sending a parcel, and tracking it home. I redesigned nine flows across the Indopaket website.

A little context
Indopaket Web is the core customer web product within Indomaret Group. I carried the redesign from UX analysis through production implementation across nine core flows.
My part: UX analysis, information architecture, interaction design, and Laravel Blade/Tailwind CSS implementation as UX Engineer and Product Team Lead.
Collaboration: I worked with backend engineers and business stakeholders to keep the redesign compatible with existing shipping requirements.
Product Challenge
Primary shipping actions were buried in unlabeled fields, store details obscured the map, and empty states offered no next step. Hotjar data from September 2023 and heuristic evaluation informed the changes shown in the 2026 iteration.
Core Shipping Journey
- Choose shipping task
- Find a store or service
- Send package
- Track progress
Key UX Decisions
Recognition
Clear tracking and rate-check labels
Label tracking and rate-check actions clearly on the homepage.
Status visibility
Map context
Use a compact selected-store card that keeps the map and result list visible.
Recovery
Help when users get stuck
Provide useful empty states, app-store links, and support fallbacks.
Information hierarchy
Focused account flows
Separate Login and Register and make verification feedback understandable.
A Small Card, a Little More Breathing Room
Selecting a store used to open a large popup over the map. The information was there, but it covered the very thing you were trying to look at. A slightly awkward introduction to your nearest drop-off point.
I replaced it with a compact store card and highlighted the matching result in the list. That way, the details and the location could stay in view together.
A smaller card also means choosing what gets the space. I prioritized status, distance, and contact information, with the result list keeping the surrounding search context available.
The screenshots below show the change. Whether it helps someone choose a store faster is something I still need to test.
Selected Interface Screens
Store and shipping discovery
How sellers find a drop-off store and track a shipment.
Beranda (Homepage)
Made tracking and rate checks easier to find on the homepage.
Hotjar showed the heaviest interaction concentrated on the “Lacak Paket” (track) and “Cek Ongkir” (check rate) widgets, both of which buried their primary action in plain, unlabeled fields — and the promo slider had no visible pagination. (Heuristic reference: Recognition Rather Than Recall.)
| Existing experience · Sep 2023 | Current iteration · 2026 |
|---|---|
![]() |
![]() |
What changed
- Slider — added visible pagination dots and breathing room from the content below, instead of one static banner butting straight into the page
- Lacak Paket — added a “Pindai Resi” (scan) shortcut, a dedicated “Lacak Paket” button, and a note on what happens after submitting (captcha verification)
- Cek Ongkir — split the combined “Asal/Tujuan” field into two clearly labeled fields with a swap shortcut, and marked Dimensi as explicitly optional
Cari Toko (Store Locator)
Shifted store details from a map-blocking popup to a compact card that keeps the map and result list in view.
Both versions kept a results list alongside the map. The problem was the selected-store popup: it was large enough to cover a significant part of the map, and closing it to check a different result meant losing sight of where the selected pin sat relative to the rest. (Heuristic reference: Visibility of System Status.)
| Existing experience · Sep 2023 | Current iteration · 2026 |
|---|---|
![]() |
![]() |
What changed
- Selected store card — reduced in size and given a clear structure (status, distance, “Terdekat” badge, contact) so it obscures less of the map and surrounding results
- Result list — the selected store is highlighted in the list, keeping map pin and list entry connected instead of relying on the popup alone
- No-results feedback — a plain “0 Toko ditemukan” became an inline, actionable “Lokasi tidak ditemukan. Coba kata kunci lain.”
| No results — Existing experience · Sep 2023 | No results — Current iteration · 2026 |
|---|---|
![]() |
![]() |
Kirim Sekarang (Ship Package)
Gave users stuck at the app-handoff screen an actual way forward, instead of a dead end.
For “Jemput & Antar ke Alamat” deliveries, handing off to the mobile app used to be a bare card — one paragraph and a single button, with no fallback for users who didn’t have the app installed yet.
| Existing experience · Sep 2023 | Current iteration · 2026 |
|---|---|
![]() |
![]() |
What changed
- Added Google Play / App Store / AppGallery badges for users who don’t have the app yet, instead of dead-ending on a single “open the app” button
- Added a “Butuh bantuan? Hubungi CS” fallback card for users who get stuck mid-handoff
- Replaced the bare text card with an illustration consistent with the rest of the site’s redesigned states
Riwayat & Tracking
Added search tips and a next step when no history was found.
The old “not found” state on Riwayat (History) was a bare “Tidak ditemukan” message with a broken image and no guidance. (Heuristic reference: Help Users Recognize, Diagnose, and Recover from Errors.) The old multi-resi tracking input also drew scattered heatmap clicks with no clear pattern. This suggested the distinction between single and multiple shipment tracking needed a closer look.
| Existing experience · Sep 2023 | Current iteration · 2026 |
|---|---|
![]() |
![]() |
What changed
- Riwayat’s broken-image dead end became an illustration + headline + self-diagnosis checklist — the same pattern now backs the Tracking page’s resi-not-found result too, so error states feel consistent instead of one-off
- Tracking input got a visual refresh, though the underlying single vs. multi-resi ambiguity is still an open item for a follow-up iteration, not solved here (see Future Exploration)
Account and authentication
How a new user registers and verifies their account.
Login and Register
Split a screen where two flows competed for attention into two focused, single-purpose ones.
| Daftar (Register) — Existing experience · Sep 2023 | Daftar (Register) — Current iteration · 2026 |
|---|---|
![]() |
![]() |
The registration form and the “Sudah Terdaftar? Login” panel used to compete on one screen — heatmap data showed clicks scattered across both. Login and Register are now distinct, focused pages instead of one competing screen. (Heuristic reference: Aesthetic and Minimalist Design.)
OTP Verification
Replaced a bare countdown with confirmation of what’s happening and what to do if it doesn’t.
| Kode Verifikasi (OTP) — Existing experience · Sep 2023 | Kode Verifikasi (OTP) — Current iteration · 2026 |
|---|---|
![]() |
![]() |
The old screen only showed a countdown and a bare set of input boxes — no confirmation of which number the code went to, no reassurance about what to do if it didn’t arrive. The redesign shows the masked destination number (“nomor HP 0812******010”), how long the code is valid, what to do if it hasn’t arrived, and a reminder not to share the code with anyone, including Indopaket staff. (Heuristic reference: Recognition Rather Than Recall.)
Architecture and Implementation
Existing production stack
Delivered the redesign in Laravel Blade with Tailwind CSS while preserving business requirements.
Reusable interface patterns
Shared empty states, store-selection cards, and form layouts support consistent future changes.
Before vs After
Earlier interface
Before
Competing actions, map-blocking store details, and dead-end feedback made core tasks harder to follow.
Delivered iteration
After
Nine redesigned flows introduce labeled actions, compact store cards, useful recovery states, and focused account pages.
What changed, and what I still want to learn
The redesign covers nine flows across six customer journeys, from finding a store to verifying an account. The before/after screens show the work: clearer labels, smaller store cards, and somewhere useful to go when a search comes back empty.
The Hotjar data came from September 2023. It helped me understand the earlier interface, alongside the heuristic review, but it doesn’t tell me how well the 2026 version works.
I haven’t measured changes in conversion or task completion yet. I’d like to watch people find a store, recover from an empty result, and verify an account. Where do they pause? What do they try twice? That’s where I’d look for the next round of changes.
What I’d explore next
The distinction between single and multi-shipment tracking remains unresolved. A planned React/Next.js rewrite offers an opportunity to consolidate the interaction patterns; it is not part of the delivered redesign.
Related Skills:
Tools I worked with
UX Analysis
Frontend Implementation
Product & Collaboration
Portfolio of

Riani BM
UX Engineer
from Indonesia












