Intuit just doesn't undertand that not every business operates the same way. It's that adage where they want you to do it their way, not your way. Akin to the grocery stores not carrying a variety of brands you prefer...they want you to have what they want you to have, not what you want you to have. Ultimately the consumer has the power of the purse, and Intuit's 'Quickbooks' brand name is slowly eroding away as it's become less and less configurable and flexible, and other brands that recognize this need are gaining market share.
That said, it's unconscionable that QB cannot simply engineer into their software the ability to custom label fields in their software. I understand that the foundation of their product is accounting, but they are more and more trying to become a sales tool, and to that end, they need to recognize that though there may be standardized functions and terminology in accounting, that every industry has differing syntax in their sales protocols.
The ability to change any 'quote' or 'estimate' to another term (as in our hospitality industry - 'RESERVATION') make this yet another Quickbooks obstacle to overcome. As the years go by, we feel we are too entrentched in Quickbooks to move on to more flexible alternative, but balk as the idea of a platform change so we just make it work. There used to be a way to change these monikers but as new QBO versions emerge, functionality wanes. Now, we are stuck with the auto-generated emails that automatically insert the word "ESTIMATE" into the subject line, and the very first line of the body of the generated email is " **QUOTE ONLY** ". We need NONE of these things inserted into that email, and anyone in business should recognize that a QUOTE and an ESTIMATE have two different meanings in business. And there should be a way to turn on/off those hardcoded subject and body labels. I suspect that the managing engineers have never been in business as they cannot seem to understand the contradictory legal nature of these two business terms.
The solution should be that the user should be able to define the term(s) that best suit their business needs, and (in our case) have the ability to elimate the moniker(s) altogether.
