Orders details
Management of an order is available in its Order Details page.
Information
Information related to order are displayed in Order information section.Order information section includes Summary, Payment and Delivery section.Summary section is used to display information related to order like creation date and type of commande.Payment section is used to display payment information like sub-total and shipping fees.Delivery section is used to display delivery information like client information, delivery address and billing address.
Content of Summary , Payment and Delivery section can be defined in Parameter page.
Alerts (like orchestration timeout) are displayed in Summary section.
Delivery information can be modified through Edit delivery information pop-in by clicking on Modify delivery information button.
Note : Delivery information can be modified until preparation is done.
Comments can be added and viewed by clicking on Comments button.
Items, parcels and bags
Order Details page display items of an order and their information like name, image or quantity.
Items will be grouped when prepared by vendors.
Groups can be bags or parcels.
Information related to groups (like tracking code and carrier) will be displayed.
Displayed information related to groups and items can be defined in Parameter page.
Information related to items and groups can be accessed by clicking on them.
States can be modified in accordance with state graph.
Depending on its state, an item can be removed from the order.
For parcels / return parcels managed by carriers proving tracking link, a Track Parcel button will be available.
It will open carrer tracking parcel page to follow parcel shipping.Print button allows to print documents related to shipping (like shipping label).
The configuration must be done in Configuration > Backoffice > Order > Order detail. To display images on items, do not forget to complete this configuration :
🏷️ Items Section - Snapshot of Order Content
In this section, you will find all the lines of the order. The lines are grouped by state, and for each line, three lines of information can be displayed. You have the flexibility to configure the displayed information in the order details configuration page.
If the same item is included in two different order items, it will be displayed separately. You can click on an item to navigate to the parcels in which it is contained.
Bundles are displayed folded if all its components are in the same state as the bundle. If the components have different states, the bundle will be unfolded.
Review stock before manual claim. If the claimed state is available in the manual state change list, a list of stock locations stock will be displayed. Stock is calculated using the stock query of the current ruleset, or of the ruleset assigned to the order if orchestration has not yet started.
Parcels Section - Clear Details of Order Fulfillment
In this section, you will find packages and bags. To view the contents of a parcel, simply unfold it.
For each parcel, three lines of information can be displayed. You have the option to configure the displayed information in the order details configuration page.
You can print or reprint documents by clicking on the printer icon. The printable documents can be customized in the Order details configuration page.
If a parcel is currently being shipped, the tracking link will be displayed. Please note that the availability of the tracking link depends on the carrier you are using.
History
All actions related to the order is tracked and displayed in its Historysection.
For actions manually set, user identity of the one that initiated it will be displayed.
Elements can be filtered based on log level or user responsible of the action, by clicking on Filter button.
Text can be searched by typing it in Search text input field. Search will be applied on all texts displayed in History section and only elements containing search text will remain displayed.Tracking Parcel and Print button are available on history element related to shipping events.
Note : Dates are in format DD/MM/YY
The user is only displayed on log lines coming from requests with different users. As a result, the log preview may show a user that appears to be “shifted” once the history is loaded, since their first log line becomes visible at that point.
Stock
Viewing stock locations of all articles based on the stock query used during the current orchestration rule can be accessed by clicking on Stock button. If orchestration has not yet started, the stock of the orchestration rule assigned to the order is the one used.
Note : Stock page related to an order is not shareable. Access must be through its Order details page
Orchestration
Current rule of an order can be viewed through Orchestration pop-in by clicking on Orchestration button.Orchestration pop-in allows to switch to a specific ruleset and rule.
Note : Change of ruleset/rule depends on user rights.
Display of prices
Prices on item block
The “price” of the order_item corresponds to original_price - sum(discounts)
There are two different rules to merges LIG in the item block in the order detailed page :
If the LIGs have the same item_id, status, price and epcs, then they are merged.
If the epcs are different, then they are not merged.
Note: same epcs = the “epcs” array is identical, or non-existent in the LIGs.
If the “epcs” table has at least 1 element, when you click on the line, a new “RFID” tab displays the list of detected EPCs. The format is simply a list of elements, not a code block.A new “order.detail.ShowLinesInformation” configuration exists in the BO back.
If this configuration is set to false, nothing changes from the current behavior. The merge remains as it is today, and the information or pricing details fields cannot be consulted via the BO.
If this setting is true, then we will act on the merged lines:
If the merged LIG order items all have identical “pricing_details” and “information” fields, then we leave them merged, with no change to their current behavior.
If at least 1 order item of the merged LIGs has a different “pricing_details” or “information” from the others, then :
In the global view, they will always be merged. No differentiation at first glance.
Clicking on the line displays a list of order items. You can click on each item to access its details. The breadcrumb trail at the top allows you to go back in the selection.
Whether or not there is a merge of different order items, the “Information” and ‘Pricing’ tabs are added to the “Modify” tab when the line is clicked. They contain data from the “information” and “pricing_details” fields respectively. These fields can only be viewed, not edited. These tabs are only displayed if they are non-zero.
The “Information” section is a block of JSON code.
The “Pricing” section displays items according to the design system. Only fields present in the order_item are displayed. There are 3 sub-sections:
“Price”- the list of possible fields is : price (number), original_price (number), refunded_price (number), currency (string),
“Discounts” - the list of possible fields is id (string), title (string), percentage (number), amount (number)
“Taxes” - the list of possible fields is : id (string), title (string) percentage (number), amount (number)
The default configuration of the order.detail.ShowLinesInformationis false in the BO back for every project.
Prices in the payment section
The “price” of the order corresponds to original_price - sum(order_items price), which is the amount actually paid by the customer.
| Subtotal - {x} items {price}|
{x} is the number of articles and {price} is the sum ofpricing_details.priceof eachorder_items| Shipping fees {price}|
There are as many lines as there are shipping fees. {price} comes fromshipping_fees.price. The line is not displayed if there are no shipping fees in the order.| Discount - {id}/{title} - {percentage} -{amount}|
There are as many lines as there are discounts. Fields come frompricing_details.discounts. If {title} exists, we display it, otherwise we display the {id}. The {amount} must be displayed as a negative number as it is a discount.| Total taxes included {price}|
The {price} corresponds topricing_details.price| Taxes - {id}/{title} - {percentage} -{amount}|
There are as many lines as there are taxes. Fields come frompricing_details.taxes. If {title} exists, we display it, otherwise we display the {id}.
Discounts sent to the order_item mesh must not be sent to the order mesh, and vice versa.