Japan's coverage on Customsdatas runs three layers deep — shipping, statistics and a directory layer — with a documented import window that lists exporters, HS code and quantity. The record set is in English; the listed coverage carries neither air freight nor a refresh schedule. Scale in that window is quantity only: neither weight nor value appears in the documented fields.
A window like this is easy to rank and hard to rank well. Names and a count invite sorting by count immediately — and in a market where trade tends to move through layered middlemen, that sort misleads: the same quantity band will mean different things for a trading house, a manufacturer taking inputs, and a distributor stocking shelves. The method below puts classification ahead of ranking, and shows why the directory layer is the instrument that does it.
Why quantity alone cannot classify
Quantity says how much moved, not who moved it or why. Two accounts with identical counts can be a producer restocking a line and a middleman assembling a mixed order — businesses with different needs, different lead habits and different reasons to answer a supplier. Sorted by count alone, they land on one scale; classified first, they land in different conversations.
There is a practical cost to skipping the step. A shortlist sorted by count will be headed by the largest mover in the category, which in a layered market is often the party with the least interest in a new supply conversation — it buys in volumes that already have homes. The role read is what surfaces the second tier, where an offer usually fits.
Classification starts in the directory
The company directory layer is where role context lives: a quantity-only record cannot say what a business is, and the directory is where that missing dimension gets filled in. The classification question is one sentence per account — what is this business, in the trade sense — and the directory answers it with context rather than inference. One sentence is enough; the goal is not a dossier but a category label that keeps the ranking honest.
Buyer tip: classify in one sentence per account before you score any of them — a trading house moving goods onward reads differently from a factory taking inputs. A missing sentence is how incomparable accounts end up on one scale.
Testing the role against movement
The shipping layer describes the physical movement behind trade, and it serves the classification as a test rather than a starting point. If a party's role is uncertain, its movement pattern is evidence: steady inbound flows and outbound flows of related goods suggest a processing or trading role, while one-directional movement fits a different profile. Read shipping entries against the role hypothesis, not before it.
The test works in both directions. A role label with no movement behind it demotes quietly to a hypothesis; a movement pattern that contradicts the label sends the account back for a second look. Either way the file gets more honest with each pass, and each line stays inside what the evidence underneath supports.
One role, one pace band
Inside a single role, quantity becomes comparable and worth reading carefully — but read it as pace rather than size. Since the documented fields carry no weight or value, treating counts as money or mass means doing arithmetic the record never asked for. What quantity supports honestly is ordinal comparison inside one role and one category: who moves more, who moves less, and how stable each one looks.
Four jobs, one order
The statistics layer frames the field of play before any of this begins — whether the category deserves the session at all. The shipping layer, as above, closes the loop with movement evidence. The working sequence is short: statistics to choose the category, the import window for the names, the directory for roles, shipping for the test.
A list grouped by role
The output is a shortlist with a role label on every line: accounts grouped by what they are, quantity read as pace inside each group, movement evidence noted where it exists. Grouped this way, the file answers a question a flat ranking cannot — where, in this category, would an offer like mine actually land?
The grouping also makes the list easier to defend. When a colleague asks why one account outranks another, the answer is a role and a pace band rather than a raw count — and if the role turns out wrong after the first call, only one line needs rewriting, not the whole sheet.
The AI Buyer Discovery Suite takes the role-classified list from there: identification, activity and opportunity value, market recommendation, similar-buyer discovery, outreach lists with emails and WhatsApp contacts, and competitor buyer detection, applied to accounts that are already comparable.
Details settled on a live run
The coverage table does not break out the export window's fields, and each layer's finer record details — what searches return, how parties are recorded, how fresh the window runs — are settled by a live sample run. Under a no-refresh, no-air coverage, that check is also where the planning constraints land: a dated snapshot discipline and a surface-freight frame.
Frequently Asked Questions
What does the import window list?
Exporters, HS code and quantity. The records arrive in English, with no air component and no regular update inside the listed coverage. Weight and value are not part of the documented import fields, and the export window's list is settled on a sample run.
Why classify before ranking?
Because a quantity band means different things for different business roles. Classification makes accounts comparable; ranking without it quietly mixes incomparable ones onto a single scale.
How do I start a role-first read on Japan?
Send a sample request via the inquiry form or WhatsApp; the team answers inside 24 hours (Mon-Sat, GMT+8), and Japanese records matched to your product line follow.
Want each role in your category mapped before you rank it? Request a free sample from Customsdatas — the classification pass begins within 24 hours.