Uzbekistan holds a single trade layer on Customsdatas, and an unusually complete one: exporters, product description, HS code, quantity, weight, value and brand — all seven fields, carried on both sides. Records are in Russian, air freight is covered, and the file is refreshed regularly.
Completeness plus symmetry plus refresh is a lot of capability in one file, and the failure mode it invites is trying to use all of it at once. The method here is sequential instead: three passes, each answering one question, and each one small enough to finish. A pass that finishes is worth more than three that blur together.
One question per pass
The passes run in a fixed order because each one feeds the next. Pass one builds the two-sided roster — who trades the category on each side. Pass two reads texture — the weight, value, quantity and brand columns that give each account its commercial shape. Pass three reads motion — what the refresh changed since your last pull.
Buyer tip: finish pass one before touching pass two. Texture read too early drowns the roster in detail, and a roster built after skimming texture tends to memorize the loudest rows instead of the complete set.
Pass one: the two-sided roster
Because both directions carry the same fields, the roster builds the same way on each side, and the two outputs merge cleanly. List the parties visible on the buying side, list the parties visible on the selling side, and mark the ones that appear on both — that overlap is your first structural finding, before any number is read.
Keep pass one purely nominal. No rankings, no filtering — a complete list of names, each tagged with its side. The discipline pays later: passes two and three can be re-run against the same roster without rebuilding it.
Pass two: texture from four columns
Pass two reads each roster name through the columns unique to a complete field set. Weight says how heavy the movements are; value says what they are worth; quantity bridges the two; and brand says whether the trade runs on labels or on specification. Four readings, one account, no arithmetic beyond what the columns support.
Buyer tip: write the four readings as a sentence per account, not a score. Sentences carry judgment into the next conversation; scores that no one can trace back to a column tend to collapse under the first question.
Pass three: the refresh delta
The file's regular refresh makes pass three possible and worthwhile: pull the same queries later and read only the difference. Names that entered, accounts whose bands moved, parties whose brand pattern changed — the delta is where a static read turns into intelligence.
Keep the delta small on purpose. You are not re-reading the market each cycle; you are asking one question against a roster that already exists — what changed — and recording the answer next to the old one.
The delta habit also builds the account's history faster than any single deep read. Three small deltas, stacked, describe a trajectory; one exhaustive read describes a moment. For accounts you intend to approach, the trajectory is what a first letter can honestly reference.
Working a bilingual term list
The file's Russian-language records change which words you search with, not how you search. Use both vocabularies in your term list: Russian commercial wording for product descriptions, and the untranslated HS codes and brand names that carry across languages. Codes are the stable spine; words are the flexible skin.
Worth noting for pass one especially: party names transliterate inconsistently, so match on codes before words when you merge the two sides of the roster. A same-code pair with slightly different spellings is usually one party whose name travelled twice — verify before counting it as two.
Disagreement as a classification signal
A name can pass one test and fail another — a busy roster presence whose texture reads thin, or a quiet account carrying one dense branded line. Disagreement is not a data problem; it is a classification signal. Write the two readings side by side and let the pattern decide which conversation each account deserves.
The air coverage adds one more layer to that pattern: for lighter, higher-value categories, some names appear mainly in the air lanes, and reading them as a separate cadence keeps the comparison fair against sea-only accounts in the same category.
Three passes, one sheet
After three passes an account carries a complete, re-checkable file: roster membership from pass one, a four-column texture sentence from pass two, and a delta note from pass three. That is the cleanest possible input to a scoring engine — every entry traceable to a specific column and a dated pull.
The three-pass sheet then moves into the AI Buyer Discovery Suite: its scoring and contact work begins with identification, activity and opportunity value, market recommendation, similar-buyer discovery, outreach lists with emails and WhatsApp contacts, and competitor buyer detection. The ranking it returns stays on evidence you can check — each line backed by a column and a dated pull.
Frequently Asked Questions
What does Uzbekistan's coverage include?
A trade layer with seven fields on each side: exporters, product description, HS code, quantity, weight, value and brand. Both directions carry these fields, in Russian, with air freight coverage and a regular refresh.
Why three passes instead of one big read?
Because a complete file invites overload. Each pass answers a single question and ends — roster, texture, delta — and the three outputs stack into one qualification sheet that stays readable.
How do I start the three-pass read?
Open the inquiry form or WhatsApp and name your product line; Uzbekistan records are delivered inside 24 hours (Mon-Sat, GMT+8).
Try all three passes on a category you sell? Ask Customsdatas for a free sample, and the roster work begins within 24 hours.