From your example, it appears that each variant of the lure is being regarded as a unique product, as each variant has its own SKU (Product Code).
EG:-
Product_model = TD03R-RB4
Product_Name = DAIICHI BLEEDING SABIKI - Size 4: Colour Red
Product_price = $1.44
So, the CSV your supplier is providing is actually a list of products and their variants, where each variant is treated as a SEPARATE PRODUCT.
If you decide to SPLIT OUT the size and colour from each product, so that you can later format this as ATTRIBUTES to a single product, you face a difficult choice. Attributes CANNOT have unique product codes, because zencart regards an attribute as a CHARACTERISTIC of a product, and not as a product itself.
So, if you split out these CHARACTERISTICS (size and colour), you are going to also affect the base product code, and this will require a mass edit of the data your supplier provides.
For example (use the same one above):
Product_model = TD03R delete RB4
Product_Name = DAIICHI BLEEDING SABIKI
- Colour Attribute = Red
- Size Attribute = 4
Product_price = $1.44
If you go this route, a LOT depends on how the supplier has structured their SKU codes. It look like SIZE and COLOUR are indicated by -RB4 and the base product is indicated by TD03R. If this is STANDARD, then reconstructing the SKU's should be achievable using a formula in MSExcel, where you can delete the size and colour defines.
But even if you do decide to do this, and then apply COLOUR and SIZE as attributes, your work is not yet done!
This presents a bit of a challenge, because zencart does not have the capacity to make attributes dependant.
So, your implementation of product stock management (by ITEM, then SIZE, then Colour) can be difficult.
Dependant attributes work like this:
Customer selects a product
Customer is presented with the first option - eg: SIZE
Customer selects desired SIZE, and his selection influences the display of the NEXT option - COLOUR.
If colour RED and WHITE are both in stock, both options are made available to customer, who then chooses a colour.
If WHITE is out of stock for the SIZE initially chosen, then only RED is presented as an option.
Zencart cannot do this in a standard install, but STOCK BY ATTRIBUTES module may offer an option.
Either way, you have THREE variables regarding your product set:-
Product NAME
Product SIZE
Product COLOUR
If you decide to use STOCK BY ATTRIBUTES module, then the following should be possible:
Products are all added to the database by NAME only.
SIZE is allocated to product as an attribute.
COLOUR is allocated to product as an attribute.
If I were you, I would rather get the business going first, and load up all the variants as INDIVIDUAL PRODUCTS, as this is the way your supplier manages their product database.
OKAY... so you have a shedload of products in your store... but at least the shop is open for business and you're getting sales. If you then CATEGORIZE your products carefully, and make use of MANUFACTURER filtering, your customers will not have too much of a challenge finding what they want.
THEN... Set up a test site somewhere, and on the TEST site, play around with the attributes stuff. See what it will entail before you unleash it on your customers and your admin staff!
The best way to load up products en-masse is to use Easy Populate and I have a WIKI tutorial showing people how to use Easy Populate.