Prestashop

We need a hierarchical order validation module with 4 levels (payers, administrators, structures, and contacts). Payers, administrators, structures, and contacts will be customer accounts managed in PrestaShop. In the PrestaShop back-office, it will be possible to define whether a customer account is a payer, an administrator, a structure, or a contact. Orders will be definitively validated at the highest hierarchical level. A payer can manage multiple administrators. An administrator can be managed by multiple payers. An administrator can manage multiple structures. A structure can be managed by multiple administrators. A structure can manage multiple contacts. A contact can be managed by only one structure. Declaration of hierarchical links From the PrestaShop back-office, at the customer level, a drop-down list will be interfaced to define whether a customer is a payer or an administrator. By default, the value of this field is empty. A second interface will allow assigning payers to administrators. A third interface will allow assigning administrators to structures. A fourth interface will allow assigning structures to contacts. Customer area - features related to payers Payer customer accounts will have an additional section in the customer area called “my administrators” and will allow the administrator to: • Consult the order history of their administrators, • Validate or refuse orders submitted for validation, • Consult previously validated or refused orders. • Select multiple orders to assign them an internal reference (addition or modification) in batches but also to validate or refuse them in bulk. Customer area - features related to administrators Administrator customer accounts will have an additional section in the customer area called “my structures” and will allow the administrator to: • Consult the order history of their structures, • Validate or refuse orders submitted for validation, • Consult previously validated or refused orders. Customer area - features related to structures Structure customer accounts will have an additional section in the customer area called “my contacts” and will allow the administrator to: • Consult the order history of their contacts, • Validate or refuse orders submitted for validation, • Consult previously validated or refused orders. Order management For payers, administrators, and structures, orders will be displayed in 2 paragraphs. For each order, it will be possible to consult its details, decrease quantities, and validate or refuse the order. The first paragraph will list orders to be validated or refused in ascending chronological order. At the end of each line, there will be a “validate” button and a “refuse” button, as well as a button to view the details. In the detail view, it will be possible to decrease quantities. Upon validation or refusal, a confirmation request for this choice will be displayed (to avoid accidental actions). Validation or refusal are irreversible actions. Following this action: the chosen option will be displayed at the end of the line and the order will be moved to the second paragraph. The second paragraph will list validated orders as well as refused orders in descending chronological order. The order will have a status of “payment accepted” only after validation by the payer1. Upon status transformation, the customer account that placed the order will receive a confirmation email1. If the order is refused at any hierarchical level, the customer account that placed the order will be informed by email that their order has been refused1. If an order is placed at any hierarchical level, the higher hierarchical level will be notified by email that an order is awaiting validation1. If the order is validated by a hierarchical level, the higher hierarchical level will be notified by email that an order is awaiting validation1. If the order is validated by the payer, the customer account that placed the order will be informed by email that their order has been accepted and the status of the order will change from “waiting for validation” to "accepted".