A country column already answers the question
Bulk reads country context from each row, so an international file does not have to be forced through one country picker.
If your file already has a country column, I don't want the upload page asking you which country the whole file belongs to. You already supplied the answer, and it might be different on every row.
A contact list can contain US ZIP codes, Australian postcodes, and UK phone numbers together. One country picker cannot describe that file.
Here is a small hypothetical input:
postal,country
02601,US
2000,AU
SW1A 1AA,GB
Bulk reads the two-letter country code beside each value. That context travels with postal lookups and phone numbers that need a country to be interpreted. It also matters when counting duplicates: the same postal text under two different countries is two different lookup inputs.
A phone number already written with + and its calling code carries its own country context. It does not become a second billable copy just because another row labels the country differently.
When the file still needs a country
In bulk, a row's country takes precedence over the country selected for the job. If the row has no usable country code, the job's selection can supply the missing context. If the required context is missing from the file altogether, the quote asks for it.
That leaves the picker doing the job it is useful for: filling in information the file does not contain. It does not override the international list you uploaded.