Order system overview

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 Optimizely Commerce Connect order system is below.  For more information, see Order manipulationOrder manipulation.

The diagram below represents how to create, edit, and delete orders. See Order manipulationOrder manipulation.

The diagram below represents how to process different actions for orders. See Order processingOrder processing.

The diagram below represents how to work with calculating totals for orders. See Calculate ordersCalculate orders.