This topic describes the order management APIs in Episerver Commerce.
In this topic
- Order objects diagram
- Order manipulation diagram
- Order processing diagram
- Order calculations diagram
Note: You should avoid casting back and forth between concrete Order classes (OrderGroup, OrderForm, etc.) and the new abstraction interfaces (IOrderGroup, IOrderForm, etc.).
For example, from the time you load the cart or purchase order until you save it, only use one API. 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 Episerver Commerce orders. For more information, see order manipulation.
Below represents how to process different actions for Episerver commerce orders. For more information, see order processing.
Below represents how to work with calculating totals for Episerver commerce orders. For more information, see order calculations.
Last updated: Jun 18, 2020