Order management in the Admin Panel lets you monitor the orders customers place through the storefront, find a specific order, and inspect its full detail.

At checkout, a customer's pending cart becomes an order, and the customer then submits that order. What happens after submission depends on the store's configuration. If your store is set to approve orders before they go to the ERP, a new order waits for an employee's approval instead of being sent. Otherwise, the order goes straight into line for the ERP. Without approval, a submitted order shows as complete at once, but that only means it is waiting its turn for the ERP, which answers later. After it is queued, the ERP may still turn the order down.

Each order carries a DigiTrade order status and an ERP status. The orders list has an ORDER STATUS column and an ERP STATUS column, and its filter fields include Status and Erp status. Read the two together to get a quick picture of how far an order has progressed. An order can be finished on the DigiTrade side while the ERP has not yet confirmed it, which means the storefront side has processed it but the ERP has not answered.

The Orders screen lists orders in a paginated table with Rows per page and page-number controls. It has a Search for Orders box and the filter fields Status, Erp status, Start Date and End Date. Use the search box when you are looking for one particular order, and use the filters to review orders by state or by date range. Each row lists the customer, sync key, order number, creation date, total, order status, last-updated date, ERP document number and ERP status. Each row has a selection checkbox, and the screen has Select all, Unselect and Delete controls with a count of selected items.

Each order has a detail view with read-only fields for Created, Order, Company name, Sync Key, Erp Document #, Shipping Address, Contact Person, Email, Phone Number, Shipping Date and Notes. A line-item table lists SKU, PRODUCT, BASE PRICE, DISCOUNT, ITEM PRICE, QUANTITY and SUBTOTAL for each product. The order summary lists Products, Subtotal, Customer Discount, Tax and TOTAL. Use the Search SKU box while you review an order's line items. The detail view also includes an ERP request / response button. Depending on the order, the detail view offers only Back, or it also offers ADD PRODUCT, RESTORE, DECLINE and CONFIRM, with an edit button on each line item.

An order waiting for approval is stored but held back from the ERP until someone releases it in the Admin Panel. Orders require approval when the store's approval setting is YES. Approval behavior with an unset setting is not confirmed. When approval is turned off, an automation tied to the awaiting-approval event does not run for submitted orders. Approval releases an order that was waiting to be sent to the ERP. Approving an order raises an order-approved event, which is separate from the order-placed event. Tie a notification to the order-approved event when you want to tell the customer that their order was approved. To decline an order that is waiting for approval, an employee must give a reason of 1 to 255 characters. Declining is permanent and the order never goes to the ERP, so there is nothing to cancel there and the ERP never creates a document for it. The customer is not told automatically, so tie a notification to the order-refused event if you want them to receive an explanation. The reason is whatever the employee typed, in any language, so write the template so it still makes sense around it. After an order is submitted, an employee can still change how many of an item it contains, and the total updates to match. The customer is not told automatically, and each changed line raises its own event that an automation can use to announce the change. A customer cannot edit a basket once it has been placed.

A message marked as sent has been accepted by the messaging application; this does not confirm delivery to the customer. An automation message's stored subject and text are redacted whenever its run carries a value the log cannot retain, even if the message does not mention it.

A shop can define order modes beyond the standard one, such as a mode for price offers. Submitting a price offer clears it from the shopper's basket, and they can find it later by its name. The dashboard's total sales figure leaves price offers out. Each order records which mode it was placed in as its document type, so you can tell a declined price offer from a declined order. There is a cap on how many named carts can be kept; going over it shows a readable error, and a cap of 0 means unlimited.