Orders are a key part of Solidus. The orders user interface is especially complex because orders connect many of the other major parts of the Solidus admin – like payments, shipments, taxes, and customer profiles.

To make sense of orders, this section of the guide explains orders in the context of a typical ecommerce store that sells basic physical products (like t-shirts), and it links out to other related parts of the users guide.

What is an order?

Every time that a customer orders product(s) from your store, a new order is created. But Solidus starts tracking orders before they are placed: as soon as a customer has put something in their cart, a new order is generated.

There are many related database objects that "make up" an order, and are created in service of an order:

All of these objects can be viewed in the context of the order – or in their own sections of the Solidus admin.

Order states

Before an order is marked as Complete, orders go through a number of other states. By default, the following states are available:

Once an order has been completed, payments and shipments can start to be processed by your store. Note that both payments and shipments have their own, separate state sets.