Folks of the great QuickBooks Support Engineering or lack there of,

We are now approaching 11 months of waiting for a fundamental fix to this BUG!

Lets get real for a moment, how, in this day and age, could anyone not understand the importance of a requirement such as this.

And for the record, actually research the definition of a SKU (Stock Keeping Unit).  From Investopedia, a SKU is a scannable bar code, most often printed on product labels in a retail store!

QuickBooks appears to be using the SKU field for something entirely different to which I would describe as a Product No, , Part Number,  Product ID etc.

We are SIMPLY speaking of a backend database where products, or service details are stored in unique columns.

Why on earth would we not have the control to create the myriad  of possibilities associated with OUR business. (Don't even get me started on Serial numbers!).

Bottom line, want to please your subscription paying audience, try fixing release problems in a timely fashion rather than absurd workarounds!

Thanks for your patience, allowing me to vent, after reading the repeated requests for nearly a year and comments by QuickBooks support where they never even investigated their recommendations before publishing on a SUPPORT page.