This topic describes the order management APIs in Episerver Commerce, and provides an overview of components used when working with orders.
In this topic
Working with order APIs
You should avoid casting back and forth between concrete Order classes such as OrderGroup and OrderForm, and abstraction interfaces such as IOrderGroup and IOrderForm. For example, it is recommended to use only one API from the time you load a cart or purchase order until you save it. While this is not always possible, doing it whenever possible helps avoid hidden problems when casting.
The object model for the Episerver Commerce order system is below. For more information, see order manipulation.
The diagram below represents how to create, edit, and delete orders. For more information, see order manipulation.
The diagram below represents how to process different actions for orders. For more information, see order processing.
The diagram below represents how to work with calculating totals for orders. For more information, see order calculations.
Last updated: Jun 18, 2020