Allow Default Terms and Conditions and Formats by Store Location

Name of Feature/Request: Allow Default Terms and Conditions and Formats by Store Location

What financial, time savings, or quality of life improvements will occur from this: To be able to use Terms and Conditions and Formats by Location. | Frequency: Daily | The upcoming default Class set at the employee level will help a lot for Class tracking on its own.Sales Tax is not calculated by the address in our system because that’s not how state sales tax works unless you’re shipping items. Could you imagine having to show ID at WalMart so they could charge you the sales tax applicable at your house? We charge 2 sets of sales taxes, one for purchases made from our Columbia, MO store and one for purchases made from our Osage Beach, MO store. Sure the Class shows which store collected the tax, but we’re committing fraud by accidentally collecting the wrong tax amount.Even if we enter a shipping address for Columbia, having a default tax required in the system results in any new customer created at the transaction level to be automatically assigned the default tax currently set for Osage Beach. The employees at the other store must remember to manually change the tax, which is an extremely difficult habit to develop.Having a default tax per Class would resolve this.A workaround would be to add Sales Tax to the short form customer information gathered when creating a new transaction and adding a customer on the fly. Since Customers can be assigned the appropriate Sales Tax at the location level, forcing a default Sales Tax selection at the customer level would be an easy workaround. Name, Phone, Email, Tax.I’m hoping that you mean item locations on transactions will be able to set to a default warehouse assigned by Class and the pending update will tie that to the employee. If so, that would be a decent fix. If you mean the default location set at the item level, I can’t imagine how that is a useful tool.The transaction formats, especially the company contact info, would be nice to have unique to the location. As we grow and add locations, listing them all will take up a considerable amount of space on a document. Forms are unique to the store location as well, as each location has unique building codes, permit requirements, subcontractors and several other lists. Having employees automatically get the correct form by Class would enable easy customization per store. Each store has regionally unique laws regarding the installation of certain items in certain places, even beyond the building codes. These are laid out within the Terms forms. Selecting this on each transaction is a small thing, but if you’re fixing one, you might as well fix everything while you’re under the hood. Since the coming update assigns employees to a Class, allowing terms, formats and forms to be assigned to a Class as well would solve the issue.Leads would have to come in from separate forms for each location and the form name would need to carry the location. That’s not horrible, but clunky. Using a custom field is ok, but it makes the stock Leads list useless, as it doesn’t show the custom field. Instead a custom report would need to be created, and employees would need to be trained around the deficiency. Opportunities are Tasks in Sales clothing, and would be a great place to use a custom field or category to separate the two for custom reports. Creating new opportunities through API however becomes a lot more difficult. We use Pools to separate the store employees currently. Once employees can be separated by Class, allowing Opportunities to be separated by Class would allow the correct Pool to be assigned each Opportunity automatically. (The same would go for Tasks of course.)Let me know if I can clarify things further!Thanks for the assist!

Attempted Solutions So Far: Manual manipulation of each of these items during the creation of each transaction is the only way to deal with it in Striven currently.

Digging deep - Any additional Why behind this request / How was this accomplished before Striven in what system or software: Previously accomplished: Arduously in Striven. In Results, Davisware, ServiceFusion and Quickbooks, the ability exists.

StrivenID: 4564494