Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/OrderManagement/OrderProcessing/ManagingOrders.htm

## Managing an Order

End users and order admins can submit, void, or unlock existing orders using the following actions:

* Submit – Users can submit saved orders. When a user selects the Submit action, the order moves to the Submitted state. Submitted orders are locked and users cannot edit the order or order lines. Any delivery orders for the order are also moved to the Submitted state.
* Void – Users can void saved orders. Voiding a saved order marks the order for deletion without deleting the record. When a user selects the Void action, the order moves to the Void state. Any delivery orders for the order are also moved to the Void state.
* Unlock – Users can unlock submitted or voided orders. When a user selects the Unlock action, the order is moved to the Saved state. Any delivery orders for the order are also moved to the Saved state. Users can make changes to the order while it’s in the Saved state before re-submitting the order.

**Who can use this feature?**

* End Users - Browser, iPad, Windows
* [Submitting an Order](#Submitti)
* [Voiding an Order](#Voiding)
* Order Admins - Browser
* [Unlocking an Order](#Unlockin)
* Users do not require an additional license

### Configuring Managing Orders for

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif) Order Admins](#)

To configure this feature, ensure [Configuring Order Management](../OM_Config.htm) is complete.

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif) End Users](#)

To configure this feature, ensure [Configuring Order Management](../OM_Config.htm) is complete.

If end users should be able to void orders, as well as be prevented from directly deleting orders, the following additional steps must be competed:

1. Remove the following permissions from all permission sets applied to the user:

   | Object | Object Permissions | Object Types | Fields | Field Permissions |
   | --- | --- | --- | --- | --- |
   | order\_\_v | D | All | n/a | n/a |
2. Grant execute permission for **Void** action for the order\_\_v object.
3. Add the **Void** action to the Submitted state in the Order Lifecycle.

### Submitting an Order as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

When a user selects the Submit action, the order is moved to the Submitted state. Any delivery orders for the order are also moved to the Submitted state.

### Voiding an Order as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

When a user selects the Void action, the order is moved to the Void state. Any delivery orders for the order are also moved to the Void state.

### Unlocking an Order as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Order Admins](#)

When a user selects the Unlock action, the order is moved to the Saved state. Any delivery orders for the order are also moved to the Saved state. The user can make any necessary changes to the order while it’s in the Saved state before re-Submitting the order.

### Related Topics

[Order Processing Overview](OrderProcessOverview.htm)

[Capturing an Order Signature](CaptureSignature.htm)