Many user and consultants are confused as to logic Acumatica uses when an override is made in the Shipping Rules at the Document Level. In reviewing the documentation and the system in practice, we are finding that the use of a document level shipping rule virtually has no logic or value; specifically if and when an override has been made at the line item level. In other words, it appears that Acumatica, ultimately looks to the shipping rule at the line item level to determine whether or not an order should be placed on back-order and/or cancelled when there is not sufficient inventory to ship.
In our opinion, the level of logic, and the explanation of the shipping rule behaviors has been over-complicated. If the system ultimately looks to line-item shipping rule, this means that the document level settings are effectively meaningless. We propose that a change in the business logic be made.
Many clients want to use the "Document Level" settings as a means to establish the default value of the shipping rules for the purposes of streamlining the data entry process. In other words, the Document Level settings should be used to set the default shipping rules value for the subsequent entry of sales order line items. If an override is made at the document level, it is this value that should be used when creating the line items, not the value established at the customer level.
This would be akin to establishing business rule overrides at the customer level for values established from the customer class, or inventory item value overrides of those set from the Item or Posting Class.