This document describe the complete list features for orders management and how will be shown.
User will use the backoffice to manage their orders and verify the status of the current and past orders.
Access all information provided from the Merchant Backend API in a understandable and accessible way
User should use the backoffice to manage orders by:
4 tabs will be show for an easy access to common filter, click on any of this and search will reset all filter except date
Columns for the order listings will be:
Actions per row:
An export button will allow the user to download the result page in CSV format.
An infinity scroll is propose instead of a pagination, reasons:
this form is divided into 4 sections
product
: where the merchant can add inventory product and non-inventory
product.price
: where the merchant can override the total price (if product was
added) or set the order price and summary.payment
: where some default of the payment processing can be changedextra
: where the merchant can add extra information in JSON formatThis section has two parts:
The first part will add/remove product from the current stock.
name
: search box to select product by description field. if not found it
will be a ‘create new’ option leading to the create product without losing
contextquantity
: mandatoryThe second part will add non inventory product. To add a product a create product form will be shown. The product in the list can be edited or deleted from the list.
In both cases, the total unit and price of the products will be calculated and shown in the bottom of the section. If the merchant collapse one of the product list a line with a resume of the total price and units will be shown.
This section has 2 scenarios.
The fist one is without products being added: the order price
and
summary
inputs will be shown.
If there is at least one product added, the total products price
as the sum
of all products prices will be shown. The order price
will default to
total products price
. The products taxes
and profit
will be shown
since order price
cannot be less that product taxes
.
This section show optional values that can be overwritten by the merchant
refund deadline
: calendar type of input. default from instancepay deadline
: calendar type of input. default from instanceauto refund deadline
: calendar type of input. default empty, optional.delivery date
: calendar type of input. default empty, optional.delivery location
: location section similar to instance jurisdiction or
instance address. optionalmax fee
: default value from the instancemax wire fee
: default value from the instancewire_fee_amortization
: default value from the instanceA success message showing the amount, summary and the order id. Additionally the taler_pay_uri can be shown to be copied to send to the customer.
action buttons that allow the following:
Status text should be set with a background color for easier recognition when indicated:
This is a resume of most important information
Event of status changed over time describe vertically. Sorted from newest to oldest. On line per status updated, with datetime and a short description.
Info taken from:
refund_details: a row showing date an amount
wire_details: a row date and id
About wire details
Normally one wire transfer will involve more than one payment from the same exchange. And an order can have multiple wire transfers if the payment involved more than one exchange.
This section is not going to be shown if there is no error
If the order was claimed
collapsed as default. show disabled if unpaid
If there is any refund:
refund_amount
Warn if there is a pending refund when refund_pending
is true
Ask for:
order list was originally thought with pagination footer
ascending boolean flag cloud be eliminated using the load before and load after and a design without random access to pages was proposed
A SearchBox was considered for managing filter. Filter will allow paid, refunded, wired status and date.
The UI of the search box is an input field with tags showing field=value
for
any filter set. Additionally a custom criteria can be supported like
date>last_week
or amount>USD:10