Streamline use of Order Number and Purchase Order Number

[Lukemodi]

When creating, viewing or editing licenses, there are 2 very similar fields present: order number and purchase order number. For everything else (assets, components...), there is only order number.

I guess the intention is to separate between your own order numbers when ordering and the suppliers order numbers when confirming your order, but having both of these on only licenses makes it a bit confusing in my opinion, but this could be an issue of not being a native english speaker.
This is even worse in the german translation where both of these translate to "Bestellnummer" and i would not be surprised if that's the case in more languages.

In my opinion, there are 2 possible ways to improve on this:

1. remove purchase order number, which would mess with everyone using it

or

2. add purchase order number to the asstes, components, accessories, consumables and possibly rename both fields to something like internal order number and external order number

This would ensure that workflows and infomation are the same across all types of objects. I understand that renaming an established field may create issues, so I am not entirely sure about that, but i am confident that having both fields everywhere already improves on the confusion when first starting with license management.

[snipe]

Purchase orders work differently than regular orders. In a purchase order, you order things before paying for them, and the order may or may not be complete when you receive it.

[Lukemodi]

OK, i never understood it in that way, even after looking it up, thanks for the clarification.

But i still don't see why this should only be present on licenses by that definition. Isn't this applicable to all kinds of products?

[snipe]

We're currently working on a new ordering system that would handle all of that. Some folks use custom fields for purchase orders since we didn't used to have them at all, but the new ordering system will cover all types of items.