Page Comparison

...

A proposed solution we will is to add new fields and mathematical calculates calculations in the system to give this information to the customer user agent.
Example:

...

The features on the screens can be consolidated into a single component for all screens, though some layout changes will be necessary(Loyalty Transaction and Orders screen). The Details Order screen will be other task.

Expand
title Improve Loyalty Transactions Screen
File: src/components/intl-loyalty/points-balance.tsx Changes: Label “Balance“ to “Points Balance“ Label “Total“ to “Total transaction points“ Add “ - “ before “Points used” Add “-“ only in numbers greater than 0' points used: 0 points used: -123 Add field “Initial points balance“ Calculate value: totalPoints - pointsEarned - poinstUsed Add field “Final points balance“ Add “bonusPoints” on “pointsEarned”

...

For existing products, we can change the number of points required to obtain them. For example, in DEV PLK ES, we can utilize the product [LOYALTY] Menú 8 alitas picantes mediano.
We can configure parameters such as the required points to use this product and the number of times it can be used per day.

Status Order

The order has ha,s a status to inform if need it needs to add, remove, or ignore the points.

More details here /wiki/spaces/PBP/pages/4856185403

...

Exist Existing the CONFIRMED status as well, and this status is added for the orders that are placed, but not finished, for example, a delivery order is placed, but it's in the delivering progress, not marked as delivered.
In this status the system doesn’t calculate the points.
More details here

...