I was trying to find the right way to store a customer’s legal name on the customer screen and I’m not sure I see where to put it. A lot of our customers primarily use a DBA, but then when checks arrive they have a legal name (and sometimes legal address) that doesn’t match up at all with their trade name.
Would it be possible to have a second Legal Name field somewhere that we could fill out (and is searchable) so we can easily find a customer that sends us a check without an invoice number and legal name only? This is also a field which can sync to QB (and other accounting systems, I’,m sure).
If I’m honest, we think there are too many fields on the customer creation/edit screen already, so we’re not excited by the prospect of adding another. With this in mind, maybe this would be best as a custom field in your account rather than a field built into Breww. Then, you could have it today (and can search against it using BrewwQL) without needing to wait for us to build a new feature.
Ok, thanks. Custom fields are not searchable using the “Search for anything in Breww” search box, but are “searchable” via BrewwQL. You can set them at in Settings → Customer, lead & CRM settings → Custom fields.
Using BrewwQL is a distant second, I find people have a hard time using that generally (yes, I know it’s easy but most of our staff has zero tech skill and it’s just hit and miss with remembering this).
I know that the screen is getting cluttered, but supporting a Legal Name separate from DBA might be a good idea for any future business-logic or integrations you might contemplate. E.g. linking with things like license checking (where often the Legal Name is what is getting checked), as well as flagging payments that do not come from the licensed entity (which is technically illegal).
That’s right. “Everything” would be quite unhelpful in practice, so it’s a curated list of searchable things.
I agree, this might be helpful. I’ll keep this request open to collect votes and see how many others want this over using a custom field. Until it’s implemented, I’d suggest you go with the custom fields solution.
Thank you for keeping it open. This is a field which would sync with the accounting system.
Regarding the searching of Anything, I might suggest that we think something is important enough to track that we are creating a custom field for it, that it’s probably something we would like to see searched.