@Rene_Poschl answers the question below.
First, I'll say that at one company, we had a resistor library that had an entry for each and every resistors. Of course, this was over 20 years ago, and we used DOS PCAD, and the library organization was driven by ERP needs.
At the day job now, we go with house part numbers and the concept of a component "family." A "family" of parts are things that are obviously common (like resistors) but vary in exactly one parameter. So 0603 1% resistors are a "family" and the variable is the value. In our library we have things like RES_0603_1% and RES_0402_1% and RES_0603_0.1%. Each is a different family and each symbol has a Part Number field set to the family part number (created by our ERP system).
So you place a RES_0603_1% on your schematic and edit the Value field to a real resistor value. Do that for all resistors in the design. A BOM processing tool takes the BOM generated from the schematic and for things that have families it marries the family part number and the value and builds a proper part number for use by purchasing.
Others use a similar system, except that their BOM processor knows Panasonic or whomever part numbers and can build such from the resistor value.
This subject always comes up when discussing library organization. It's an old old problem, and nobody's solution is better than any other solution. It just depends on user needs. I can only advocate for what has worked for me. Your solution make work better for you. The good news is that Kicad supports different workflows and requirements.