Add a custom column to the 'Order History' page on the user side (Ustore)

[Alexis Podevin]

English version:

Hello everyone,

On one of our storefronts, our client would like to add an additional column to the "Order History" page, on the user side (not the admin side).

In this new column, we would like to display a value that is stored in the database at the time of the order. The ordered product is a variable product, and the client uploads a list of recipients to the platform during the order process.

We have already implemented the "nickname" field for orders, but it doesn't fully meet our expectations: the nickname only appears in the order details and not when hovering over the order number.

Do you have any ideas or suggestions on how to achieve this?

Thank you in advance for your help.

--------------------------------------------------------------------

Version française :

Bonjour à tous,

Sur l'une de nos boutiques, notre client souhaiterait ajouter une colonne supplémentaire sur la page "Historique des commandes", côté utilisateur (et non côté administrateur).

Dans cette nouvelle colonne, nous aimerions afficher une valeur qui est enregistrée en base de données au moment de la commande. Il s'agit d'un produit variable, avec une liste de destinataires que le client importe sur la plateforme lors de la commande.

Nous avons déjà mis en place le champ "surnom" pour la commande, mais cela ne répond pas totalement à nos attentes : le surnom n’apparaît que dans le détail de la commande et non lors du survol du numéro de commande.

Auriez-vous une piste ou une idée pour atteindre cet objectif ?

Merci d’avance pour votre aide.

[couch]

The client-side order history page is currently a "composite" type of page where there are .net controls in an iframe on a React JS page.

This means both good and bad news.

In the short terms you _may_ be able to modify the .net page to add your additional field. This would be classified as hacking the existing product and frowned upon since it is not supported or recommended by XMPie, and could also introduce unintended security issues. Also, your efforts will be short lived if/when XMPie moves this page to be fully React JS.

The more positive news is that XMPie is intending to move more "smaller" pages to 100% React JS later this year. I do not know if the order history page is one they plan to migrate, but since it does not have a lot of complex interactions, it seems to me to be one of the "low hanging fruit" that could be done fairly quickly and easily. The good news in this is that after the page is in React JS, you can more easily make changes with a custom theme.