Skip to content
Turkey Import Data
Turkey Import Data Research

Turkey Import Data

Define the product or HS code, import direction, period and partner market. Review the exact source, field definitions, units and limitations before using any result.

Describe your scopeReview the method
Research scope
Record the product or HS code, period, partner market and measures that define the question.
Evidence check
Identify the exact source and verify how its fields, dates and units are defined.
Limitations
Keep unavailable fields, coverage gaps and interpretation limits explicit.
Scope checklistData schema
Product or HS code
Import period
Partner market
Required measures
No dataset, company-field, report-format or API availability is asserted until the exact source and scope are reviewed.
Turkey import field guide

Read the fields behind a Turkey import report

The reviewed TR HS field contract distinguishes product, declaration, recorded parties, country roles, quantities and values. This guide explains those distinctions; column names do not establish populated fields, complete import coverage or current delivery availability.

  1. 01 · Import direction and declaration date

    Use direction to select imports and declaration_date for the requested period. declaration_number and item_number describe different levels of a record. A file name or upload date is not a substitute for the declaration date; missing declaration or item details remain a limitation.

  2. 02 · HS code and recorded product description

    hs_code identifies the recorded classification, while product_description preserves the source product text. Confirm the required code level before comparing products. A file name is not authoritative when it disagrees with the recorded HS code, and a generic HS label must not replace the source description.

  3. 03 · Recorded sender and receiver

    sender_name and receiver_name are separate recorded roles, with sender_id and receiver_id as separate identifier fields. Their presence in a contract does not certify legal importer or exporter status, independently verified tax identity, or a purchasing contact. Confirm role meaning for the source before building a company list.

  4. 04 · Origin, destination and trading-country roles

    Keep origin_country_name, destination_country_name, sender_country_name and trade_country_name distinct. Select the role that answers the question instead of combining them into one partner-country field. A recorded customs office is also not automatically a port or evidence of a transport mode.

  5. 05 · Quantity, units and weight

    Read quantity with quantity_unit and the applicable measurement-unit fields. gross_weight_kg and net_weight_kg are different measures; package_count is not interchangeable with either weight or quantity. Missing values remain missing, not zero. Establish compatible units before comparing or adding observations.

  6. 06 · Invoice, statistical and calculated values

    invoice_amount belongs with invoice_currency. statistical_value, statistical_value_usd and calculated_statistical_value_usd are distinct fields, as are unit_value and unit_value_currency. Resolve currency, reported versus calculated values, and declaration versus item level before making a total or unit-price comparison; not every amount field is additive.

Interpretation and request scope

What these field definitions do—and do not—prove

Does a documented field mean it is present in every import record?

No. The reviewed standardized TR HS contract permits missing values in every column. Column existence is verified, but import-specific field population and completeness were not measured in that metadata review. Confirm the required fields for the exact source and period before relying on an extract.

Can a record count be described as a shipment count?

Not without a defined grain and deduplication method. The retained archive uses standardized source observations; declaration details, item details and analytical versions must be distinguished. Repeated files, repeated payloads and repeated business items are different duplication questions. An observation count is not automatically a unique-shipment total.

Does the archive date range establish complete import coverage or a refresh schedule?

No. A mixed-direction archive's earliest and latest dates do not establish continuous import coverage for a particular HS code, nor the date of the latest customer-ready update. Check import direction, the exact code and requested months separately. This page makes no national-completeness or refresh-frequency promise.

Does this guide confirm a download, API or export dataset?

No. A reviewed internal field contract is not a tested customer download or public API. The independent Turkey export product has its own evidence and must not supply periods or completeness claims for an import request. Delivery format, access and permitted use require separate confirmation.

What should I include in a Turkey import report request?

Use the existing Describe your scope form below. State import direction, the product or HS code, declaration-date window, country role, required sender or receiver fields, quantity or value measures, and preferred output. These details define what needs checking; submitting a request does not confirm availability, a quotation or immediate access.

Scope review

Describe a Turkey import-data research scope

Share the product or HS code, period, partner market and measures you need. The question can then be checked against an exact source and its limitations.

  • A bounded research question
  • Source and field questions recorded
  • Known limitations kept explicit