Import not working for certain fields [#2747885]

Forgive me if I don't use common drupal terminology as I've been on this architecture for about a week, and was given the task to import a large import file into the system. The version I'm using is Drupal 7 and this Feeds module was already installed.

When I imported the file, all 750 records were added to the content resource screen. All my nodes were properly added. However, no errors were reported, I don't know if this is default functionality. When I went to check the content, all the fields that has simple mappings (text, boolean, date) were filled, but the ones that had a complex type (postal code) were ignored. The import file I'm using is a CSV file, TAB delimited, each cell value is surrounded by double quotes ("). The order of the CSV fields (columns) and the import feeder have the same ordering weights; like Column 1: Name, Column 2: Description.. maps to the Feeder importer in the same order.

Here's the structure of the content:

http://oi65.tinypic.com/4fxxes.jpg
(this is the uploaded file image ContentStructure.jpg)

The address contains multiple fields, State, City, Zip Code

Here's how the import feeder looks (mind you, it recognizes each field in this address table)

http://oi63.tinypic.com/21j3nmh.jpg
(this is the uploaded file image Address.jpg)

So when I check each content of what's been imported, the Name, Description, Phone, Website... everything except Address fields (City, State, Zip Code) were imported. Also the Taxonomy field.. AIRS.. was also skipped.

I've tried everything, and spent several hours conditioning my import file, with failed results. And I've come to conclude that this is an issue with the module itself.

Personal commentary:
I figured that this should be throwing errors at me. Mentioning if field has been skipped, or if a value can't be stored, instead of just importing the record. If this is default functionality, I personally wouldn't recommend this module for what we're doing. The interface and the UI is great and easy to understand. But if it can't do nested (grouped) fields, I'm going to have to find different alternatives.