Edward Aguiar This was put in for me from an open ticket regarding issues where GA was erroneously returning no rates, where merely reprocessing the order would successfully find said rates. We are still working with our postage carrier on this matter.

A better request would be that fetched rates would be added to OMR, along with supporting more comparison logic. Always failing an order in a fringe scenario would not be intended behavior, and instead, In our case, we would be able to throw a custom error if the value returned was null. I believe others could find use for fetched price a useful rule to catch possible ship errors when prices fall outside expected ranges.