Are there any watch outs for having multiple sales order forms, and updating/editing transactions using the different forms? We collect some different information based on items sold, and to keep things as neat as possible on the forms, i was thinking about perhaps having multiple SO forms could help.

Having different forms can help but you must have some identifier other then form which should distinguish forms. Like we have different SO for web orders and different for store. And we have list order type field which is mandatory decide which form to use.

@Gregory Jones watch out for making fields mandatory on one form, but not on others. That would cause problems.

@Olivier Gagnon (DXC) That's a good callout! I think for the most part it would be adding/removing custom fields based on the needs that the form will be for, it's definitely something i'll make a note of.

I prefer one form with a workflow to show/hide the proper fields at the proper time based on the record contents. When you have separate forms you run the risk of the wrong form being displayed to the wrong person or for the wrong item. The other thing I have seen is, you clearly define which items or sales teams user which form then a new item gets created this is not clear cut which it uses and needs something from both then you end up with a anther form and a new set of rules.

It will most likely get messy very easily, the multiple form thing is dangerous and hard to maintain...

Messy is what I am afraid of...we originally were going to use transaction item options for some things, but that features is clunky in the UI...expecially when another subsidiary is a lot larger and really messed up the options box when it appears with their millions of options.

Create multiple forms and make them default or available to that specific role and user. and if you want to display certain items to specific team then create a saved search with the criteria and apply that to the form so when the user log's in with that role he will only see that specific items.this way we can maintain the forms and items at same time.

Speaking as someone who inherited an absolute mess of transaction forms from an implementation definitely look at other options discussed here first. That being said in the most lean version of our forms I would still have a few Sales Order forms for eg Wholesale, Ecomm and Physical POS. My rule of thumb would be if more than 50% of the fields/sublists/tabs wouldn't apply to a type of sale potentially justifies a separate form (obviously that's very broad, your business case may be totally different). For us the 1:1 relationship between forms and pdf templates is a factor, you might want to consider too.