← Compare
INNA TESIS
← All work
01
eezyimport · Importer Security Filing (ISF)

A broker's job, done by a first-time importer

A legal US customs filing that used to need a broker, redesigned so any importer can get it right, for $10.

My roleSole product designer, with one PM
UsersImporters, first-time and regular
Period2020 · eezyimport's first product
Status● Live
ISF flow, step 1 of 4: Receiving party. The importer's details are filled in from the company profile. 1 2 3
four steps, one party at a time ↑
Step 1 of the ISF flow: one side of the shipment at a time. The pins match the decisions below.
01Context

Ten details, and a different form every time.

Since 9/11, every ocean shipment to the US needs an Importer Security Filing: ten details about who sold, made, bought and packed the goods, sent before the cargo is loaded abroad. The law defines the data, not the form, so every broker and forwarder made their own, with different names, order and even deadlines. Most importers simply paid a broker to deal with it.

The goal

Make the filing clear enough that an importer doesn't need an expert to get it right, for $10, a fraction of what a broker typically charged.

Why it mattered

ISF was the first thing we built, in 2020. It was the test for the whole company: can a customs filing work without a broker at all? If it did, everything else could follow.

same 10 details, three names each ↓ (the paper forms go here)
02The problem

With no expert in the loop, the product had to know what the expert knows.

An ISF is a legal filing, and the importer carries the responsibility, and the fine, for every mistake.

So the product had to know which data is really needed, tell people where to find it in a pile of shipping documents, keep them from typing the same company again and again, and make sure the filing goes out on time.

"As a first time filer of ISF, I did not know what to do."— First-time ISF filer, via Trustpilot

03Key decisions

Three decisions that made it clear.

Shipping party step: each card explains the party in plain words, and two cards can be skipped until 24 hours before arrival. 12
each card says what it is and where to look ↑
Decision 1

Fewer fields, in the order of the shipment

  • 1
    What changedI mapped which data is truly required and which document each detail comes from, then grouped it the way the shipment moves: who receives it, who ships it, what's inside.
  • 2
    WhyPeople had the answers, just scattered across invoices and bills of lading. Each card says what it is and where to look.

Before: one form with ten fields, in whatever order the forwarder chose.

Receiving party step: the importer comes from the company profile, and the consignee card offers Use importer details. 12
one tap instead of retyping ↑
Decision 2

Never type the same company twice

  • 1
    What changedThe importer's details come from their profile. Consignee and buyer are usually the same company, so one tap, "Use importer details", fills them.
  • 2
    WhyThe same company plays several legal roles. Retyping it is slow, and every retype is another chance for a mistake.
Review screen: a red block stops the filing, a yellow block can be completed later. 12
red stops you, yellow just reminds ↑
Decision 3

Block only what has to block

  • 1
    What changedThe review shows all the data in short blocks by side. Red marks what stops the filing. Yellow marks what can be sent now and completed later.
  • 2
    WhyThe user is responsible for every detail. And the law lets two details arrive up to 24 hours before the ship reaches the US, so I let people skip exactly those two, and no others.
04The flow

From documents to an approved filing.

1 · FillFour steps, one side of the shipment at a time
2 · ReviewRed stops you, yellow reminds you
3 · Pay and send$10, right from the review
4 · TrackSent, pending CBP, then approved or what to fix

Timing is critical, so after sending, the user always sees where the filing stands and where it got stuck.

05Scaling up

From one filing to fifty at once.

Bigger importers file many ISFs a week. Batch upload turns their ERP report into a list of filings. They confirm, review or fix each one on the side, without losing the list. Nothing is filed until they confirm it.

Batch upload: a list of filings to confirm before sending, with a counter of confirmed filings. 12
nothing is filed until you confirm it ↑
Batch upload panel for the ERP report
1 · Upload the ERP reportOne spreadsheet, many filings
One filing opened for review on the side
2 · Review one filingOpens on the side, the list stays in view
Editing a party inside the batch
3 · Fix in placeEdit a party without leaving the batch
06What came next

One entry, used twice. Then, documents first.

One entry, used twice

ISF data flows into the Entry Summary, the next customs filing, so the customer doesn't fill the same details again.

Documents first

Later, ISF changed. The user uploads the shipping documents at the start, the system pulls out the needed data, and the user approves each detail or fixes it by hand. The flow stayed. The typing mostly went away.

Document upload and extractionscreens to come
07The language

A language that started with ISF, and grew with the product.

The logo and core brand colors came from an external agency, chosen together with the team. I took them into the product and built the working palette around them: status colors, UI tints, components, icons and illustrations. Here it is, organized.

Colors, type, icons and componentspage to design
08Outcome

The test worked.

ResultThe model worked

ISF proved customs data could be filed without a broker. eezyimport grew from it into a full customs, freight and insurance service.

ResultA base to build on

The patterns and visual language set here carried into every product after it.

StillLive

Years later, on the same core flow, now a low-cost add-on to the rest.

"I particularly appreciated being able to file my Importer Security Filing (ISF)…"— Importer, via Trustpilot

eezyimport overall today: 4.8 / 5 on Trustpilot (683 reviews) · 40,000+ shipments

09Shipped → Now

What went live, and how I'd do it today.

Be open about it: the release cycle was slow, so parts of the product still run on the first version. Show what shipped, then one or two screens redesigned with today's eye. Label them clearly, so no one mistakes a redesign for the live product.

Shipped · 2022
The live list of filings
Live product
Redesign · not shipped
How I'd do it todayscreen to come
My next iteration
10What I learned

When there's no expert in the loop, the interface has to be the expert. Most of the work wasn't drawing screens. It was deciding what not to ask.

Let's talk.

Open to senior product design roles.

in1177@gmail.com