Ability to update person info records after order has been released to warehouse

We have found various use cases where we need to be able to update the person info records on an order after the order has been released to the warehouse.  Currently, the OMS platform only allows updates to the orders up until the order has been released and there is no configuration available to allow it in other statuses.  When trying to update these details we get the error: <Errors>

<Error ErrorCode="YFS10137"

ErrorDescription="YFS: Order cannot be modified in current status" ErrorRelatedMoreInfo="">

<Attribute Name="ErrorCode" Value="YFS10137"/>

<Attribute Name="ErrorDescription" Value="YFS: Order cannot be modified in current status"/>

<Attribute Name="DocumentType" Value="0001"/>

<Attribute Name="OrderNo" Value="5029021516"/>

<Attribute Name="PrimeLineNo" Value="1"/>

<Attribute Name="ProcessType" Value="ORDER_FULFILLMENT"/>

<Attribute Name="SubLineNo" Value="1"/>

<Attribute Name="ModificationType" Value="SHIPTO is disallowed because none of the statuses are set to 'allow'"/>

<Attribute Name="ModificationLevel" Value="ORDER_LINE"/>

<Attribute Name="OrderHeaderKey" Value="202306091748048038825609"/>

<Attribute Name="EnterpriseCode" Value="DisneyNA"/>

<Attribute Name="Override" Value="Y"/>

<Attribute Name="OrderLineKey" Value="202306091748048038825622"/>

</Error>

</Errors>

There are cases where we would want to update person info records after an order has been released to the warehouse, the following usecases provides those examples.  Currently, in order to resolve these issues, we have to request the IBM team to run manual update SQL statements to resolve the orders.  This is an extensive process and takes multiple days to get the proper approvals needed to run the scripts and impacts guest satisfaction.

1. When we need to fix an order's address for items that aren't necessarily shipped to a guest (ex. Gift Cards). In this case, we have an address validation which is failing in between "Shipped" and "Order Invoice Created" status which is causing the order to hang and not proceed to process payment.

2. When we need to update a guest's email address and phone number due to a middleware issue where the encoded values were sent instead of the actual characters (ex &#x2b; for + and &#x40; for @)