Skip to main content

#Import potential buyers into TradePilot

TradePilot imports customs data and other lead files into one source-backed buyer pool while preserving the origin of every imported row.

#Who this is for

Use this guide when you have a buyer file or supported conversation source and want to add potential customers without losing source evidence.

#Choose the correct source

Open Import history and select Add potential customers.

SourceBest for
Customs dataShipment, product, HS code, quantity, trade value, supplier, route, and purchase evidence
Other leadsGeneral prospect lists with company, contact, location, product, source, tags, or notes
WhatsApp translation companionSupported conversation evidence from the connected companion

Do not place ordinary prospect lists into the customs-data flow. The source type affects which evidence TradePilot expects and preserves.

#Prepare the CSV file

  1. Choose the import type and download its current CSV template.
  2. Keep the header row and place one source record on each row.
  3. Do not invent missing company, country, contact, product, or purchase values.
  4. Save the completed file as CSV.

Customs imports can include company and contact details plus product, HS code, purchase date, quantity, unit, trade value, currency, supplier, origin, destination, ports, source, record ID, and notes. Other-lead imports use a smaller general prospect structure.

#Map and identify the rows

Upload the file and review the field mapping. Select an identity field that is populated in every row you intend to import. The company name is not mandatory when another selected identity value is available.

Check a sample of the mapped values before confirming. A value in the wrong column can create misleading buyer profiles even when the upload succeeds.

#Review the import result

After processing, open the batch in Import history and compare new, merged, duplicate-review, and failed rows. Open newly imported buyers and confirm their source-backed profiles before outreach. Similar names alone should not be treated as confirmed duplicates.

#FAQ

#Which import type should I choose?

Choose customs data for shipment and purchase evidence, another lead import for general prospect lists, or the WhatsApp translation companion for supported conversation-based entry.

#Must every CSV row include a company name?

No. Each row needs a value in the identity field selected during import, while company name can remain blank when the source does not provide it.

#How can I see what happened to each row?

Open Import history to review the batch, mapping, and counts for new, merged, duplicate-review, and failed rows.

Last updated: