Sep 24, 2026Country Guides
Iran Customs Data (2026): Qualifying Long-Cycle Buyers in a Two-Layer Market
Iran runs trade and shipping layers under a NEW flag. A qualification sheet for categories that trade on contract cadence rather than monthly rhythm.
Iran carries trade declarations and shipping movements on Customsdatas, coverage newly added and carrying the NEW flag, with two layers running together. The usual dual-layer method is cross-verification: trade proves the relationship, shipping proves it is live. This guide is for a harder case: qualifying buyers when your category does not trade on a monthly rhythm.
The cadence problem, stated plainly
The standard qualification playbook ranks buyers by recurrence — how often a party appears under your code. That works when buying is routine. It misleads when a category sells in contracts, projects or production runs, because a real, large relationship can look irregular in a record built from event dates.
Buyer tip: before distrusting a cadence-based read, match your own sales cycle to the data rhythm. Monthly, quarterly and annual buyers need monthly, quarterly and annual lenses — before any ranking means anything.
Two layers, one liveness rule
The two-layer structure supplies the workaround. Trade declarations establish the commercial relationship — who buys, under which classification, at what scale. Shipping movements establish liveness — whether goods are moving on that relationship now rather than having moved once and stopped.
The liveness rule is absolute: never qualify a long-cycle account on declarations alone. One declaration plus active movement is a live relationship; declarations without recent movement are history, however large they look.
Reading scale bands instead of counts
When counts mislead, scale takes over. Read every candidate's declared scale as a band — under, within or above your production window — rather than as a ranking number. An account declaring once a year at your exact scale is a better prospect than a monthly buyer whose orders you cannot serve.
Buyer tip: write your band boundaries down before the search. Post-hoc banding bends to whatever comes back; pre-committed bands keep the read honest and comparable across accounts.
Multi-period presence: the slow signal
Counts ask how often a party appears; presence asks whether it appears across the periods that matter to your cycle — each quarter for quarterly buyers, each year for annual ones. A buyer present in three successive annual windows is a durable relationship, even when the monthly view shows only three data points.
This method needs patience by design. Long cycles produce few events, so each event carries more weight — and misreading one distorts the whole year. A slow record does not forgive a quick pass.
The liveness check, done properly
On the shipping side you are looking for movement on the relationship: flows involving the parties and lanes your trade read identified. Because routing and granularity vary by lane and category, what the shipping layer exposes is best confirmed on a sample run.
Buyer tip: record the date of the last observed movement for every account on your sheet. In slow markets, recency is the single field that tells you whether outreach lands on a live desk or an archive.
Replacing frequency with recency and depth
Frequency answers a monthly question. Two other measures answer slow ones: recency, meaning how recently a relationship moved at all, and depth, meaning how much of a party's trade sits in your category versus around it. A narrow, recurring industrial buyer and a broad trading house can share a frequency count while deserving opposite approaches — depth separates them before you write anything.
Buyer tip: build the read from the party's whole declaration history rather than the single line your search returned. On contract-scale flows, one line in isolation shows almost nothing; the pattern across lines shows everything.
Assembling the qualification sheet
Three readings per candidate, one row each: scale band, multi-period presence, last-movement recency. Clear all three and the account enters the working list; clear two and it enters nurture; the rest stay in the archive until the next refresh.
The sheet replaces the frequency league table a cadence-based guide would build. It fills slowly and reads accurately for contract-style categories — and because both input layers sit in the same dataset, each refresh rebuilds it without leaving the platform.
First contact, written from the sheet
The sheet's observations write the first message: the band tells you which configuration to lead, the presence line tells you whether to speak in terms of continuity or first trial, and the recency line picks the week.
Past first contact, the AI Buyer Discovery Suite continues the same discipline at scale — identification, activity and opportunity-value scoring, market recommendation, similar-buyer discovery, outreach lists with emails and WhatsApp contacts, and competitor buyer detection — which lets the list grow without the read getting shallower.
A liveness judgment ages. Movement observed in one period says nothing about the next, so an account that has gone quiet belongs back in nurture rather than on the working list — and the sheet should be rebuilt, not merely appended to, after every refresh.
Keep the sheet dated and versioned as you go. In a market where each event carries weight, the comparison between two dated sheets is the closest thing to a trend line the cadence will ever give you.
Frequently Asked Questions
What does Iran's coverage include on Customsdatas?
Trade declarations plus shipping movements, under a NEW flag that marks recently added coverage. The two layers support the long-cycle qualification method in this guide.
My target account shows only one or two declarations — is that enough?
It can be, in contract-style categories. Read the declaration's scale band and check the shipping layer for movement; one declaration plus active movement is a workable signal. Confirm what is observable for your product line on a sample run.
How do I request sample records?
Send your product name or HS code through the inquiry form or WhatsApp. The team replies within 24 hours (Mon-Sat, GMT+8) with records matched to your product line.
Working a contract-cadence category into a two-layer market? Request a free sample from Customsdatas and run the long-cycle sheet on your own product within 24 hours.
