CSV import is not very likely to happen, except in a very limited form. I can import part names, and stock numbers, no problem. But importing relational data (parts+storage+stock) from a flat spreadsheet file is a recipe for disaster. I don't think this is possible in general case.
why is this problematic ?
if i give you a table like this :
location, part name, part manufacturer, vendor , vendor order code, description, note
That is what i have now.
for example
ICA175,NE555,TEXAS INSTRUMENTS,DIGIKEY,NE555DE4-ND,Timer circuit, NRND replaced by 296-6501-2-ND
ICM219,24c32,ST Micro,,,I2C eeprom, overstock in REELIC107
REELIC107,24c32,ST Micro,,,I2C eeprom,reel of 3000
ICA175 is my location reference.
i use a system of antistatic bags in bins. ICA=IC analog , ICD=IC digital ,ICC= cpu ,ICM=memory, T = transistor D=diode, REELxx = whole reels
the rest is a sequence number. i gave up on ordering them by part number. i go too many being 'injected'
this excel sheet has more information in it in further columns but those are irelevant for stock management.
the other fields are :
Part ref, Part Library, Footprint Ref, footprint Library, Comment , Designator, and some other fields.
Altium reads the same excel file and builds symbol libraries ( it links in the schematic symbols and footprints. ) so when i pull a bom i have all info : who makes it ,where do i buy it , what is order code ,and where is it in my lab. if it is a new part the leader field will be blank.
Any schematic and board made with this spreadsheet ties everything together. no going fishing afterwards ...