Importing vendor data at scale without manual re-entry can be challenging, especially during vendor onboarding. The good news is that most import issues stem from formatting, validation rules, or country-specific requirements, not from system failures.
TradeTapp has robust vendor import capabilities that support everything from simple, lightweight vendor lists to full BuildingConnected (BC) Quals exports.
In this guide, we’ll walk through the core template requirements, supported data types, international vendor considerations, and the fastest ways to troubleshoot common import errors.
Note: This guide is intended for TradeTapp admin users at general contractor organizations. Vendors themselves do not run imports and will not have access to the import tool. If you are a vendor looking to submit qualification information, you’ll need to complete that directly through a TradeTapp invitation.
TradeTapp’s vendor import helps GCs bring vendor data into the platform faster, especially when onboarding large vendor lists or migrating from other systems. Imports work best when the source data closely follows the platform’s structure and validation rules.
You know that a vendor import is successful when you see everything in the Vendor Grid. Here, GCs can:
While the vendor import process helps streamline onboarding, TradeTapp’s vendor import features are intentionally structured to protect data quality and prevent conflicts. Specifically:
TradeTapp uses tax identifiers and existing vendor accounts to prevent duplicate vendor records. These safeguards help ensure data integrity and avoid fragmented vendor profiles.
TradeTapp has an XLS-based import template with predefined columns and tabs, in which one logical vendor record is represented across multiple tabs using a shared Company ID.
As with most structured import systems, the template depends on standardized formatting to map data correctly, and so column names, formats, and tab structure must remain unchanged.
Certain basic fields in the template, including the company name and contact email, are required to create a vendor record. That said, there are also optional fields, which help create more complete vendor profiles and support stronger benchmarking, analysis, and qualification workflows later on.
Also, some fields become conditionally required based on the country or data type.
The specific data groups included in the import template include:
Important: not all tabs or fields behave the same for international vendors.
This section covers the vendor data fields most commonly included in imports. It also sheds light on common failure reasons for each category. If you encounter these errors, double-check the information you’ve entered to make sure it matches TradeTapp’s supported formatting and validation rules.
If you’re importing international vendors into TradeTapp, there are a few important limitations and country-specific rules to keep in mind.
TradeTapp supports importing and managing international vendor data, including financial information and multi-currency workflows, as long as the data meets the required validation standards.
Some restrictions are intentional. TradeTapp applies country-specific safeguards to maintain clean qualification workflows and reduce incomplete or invalid vendor submissions.
Qualification workflows depend on country-specific validation logic tied to things like tax IDs, postal codes, and regional address structures.
Restricting qualification invites for unsupported international workflows helps TradeTapp prevent vendors from getting stuck in incomplete applications. This also preserves consistent benchmarking and review standards for GCs.
This is a high-level overview of the TradeTapp vendor import process, from preparing your file to resolving validation issues after upload.
Start with the latest TradeTapp vendor import template and enter vendor data beginning on row 4, since the first few rows contain instructions and examples. Keep the same Company ID across tabs so TradeTapp can associate related vendor data correctly.
If you’re working from a BuildingConnected export, make sure any required supporting tabs, such as Custom Questions, are included before upload.
Before uploading, review the file carefully for formatting issues. Confirm required fields are populated and verify that state or province values, postal codes, tax IDs, phone numbers, and currency fields match supported formats.
It’s also a good idea to review international vendors separately, since validation rules can differ significantly from US and Canadian vendors.
To upload the file, log in to TradeTapp as an admin user and navigate to Settings → Vendor Import. From there, upload the completed file and start the import process.
While the file is processing, TradeTapp will display that the import is in progress. Once complete, the platform will show whether the import succeeded or failed. If issues are detected, error messages will point to the affected records or fields so you can troubleshoot.
If the import fails, review the error messages carefully and correct the issues directly in the original source file rather than editing vendors individually after upload. Once the data has been corrected, re-upload the updated file to retry the import.
Most import issues are straightforward to fix once you know where to look. In many cases, these issues are caused by formatting mismatches, missing country context, or unsupported values.
Check that the state or province value matches TradeTapp’s supported list exactly. If the vendor’s country does not use states or provinces, remove the value entirely. Also, confirm that the country field itself is populated correctly, since validation rules often depend on it.
Make sure the postal code format aligns with the vendor’s country requirements. In some cases, spaces or formatting characters may need to be removed. International addresses should always include a valid country value so the system can apply the correct validation rules.
Verify that the tax identifier matches the selected tax ID type and that the identifier itself is supported for the vendor’s country. If a tax ID is optional or unsupported for that vendor type, leaving the field blank may be the correct approach.
International phone numbers should include country codes where required. Remove unsupported formatting elements, such as extensions, extra spaces, or punctuation, that may interfere with validation during import.
Use only currency codes supported within TradeTapp and make sure the selected currency matches up with how the GC plans to enter, review, and benchmark financial data within the platform.
Re-importing makes the most sense when validation or formatting issues affect a large number of vendors across the file. For smaller corrections or isolated updates, editing directly within TradeTapp is usually faster. It’s also important to remember that imported data will not overwrite information submitted directly by vendors through their own accounts.
TradeTapp continues to expand its international support capabilities, including more flexible country-aware validation rules and broader international qualification workflows. Over time, this will help simplify onboarding while maintaining the data consistency and benchmarking standards GCs rely on.
Hopefully, this article gives you the guidance you need to run cleaner, faster vendor imports with fewer headaches along the way.
Remember, vendor imports are powerful, but they’re intentionally strict for a reason. If you run into import failures, they’re usually because of data format, validation rules, or missing country context. You can avoid issues by reviewing your data carefully before upload and making sure it aligns with TradeTapp’s import requirements.
