You can automate order processing across every stage in the order lifecycle. When your automated business logic encounters an issue that interrupts normal processing, a process exception occurs. Various issues can cause a process exception, such as a failed fraud check, a payment capture error, a lack of available inventory, or a problem with a shipping carrier.
- Check for Active Process Exceptions
When a process exception occurs, Order Management creates a process exception record and generates a notification that appears at the top of the associated Order Summary page. The process exception typically states the problem that requires user review or intervention. Your business logic and workflows determine whether to continue processing an order summary when an exception occurs. When necessary, you can suspend order processing until the issue is reviewed and resolved. - Create a Process Exception
Create a process exception to manage a processing issue that isn’t automatically identified by your order management processing business logic. - View Process Exception Details
A process exception record contains details about the cause of the processing failure. - Identify the Cause of a Process Exception
Process exceptions can occur at any stage in the order lifecycle. Identifying the cause of a process exception is the first step toward resolving the issue. - Resolve a Process Exception
After you identify the cause of a process exception, you can resolve the issue and continue normal processing on the order summary.