View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010581 | Taler | merchant backoffice SPA | public | 2025-11-10 23:43 | 2025-11-13 17:39 |
| Reporter | Christian Grothoff | Assigned To | sebasjm | ||
| Priority | urgent | Severity | feature | Reproducibility | N/A |
| Status | assigned | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | 1.0 | ||||
| Target Version | 1.2 | ||||
| Summary | 0010581: Profiles to simplify merchant backend | ||||
| Description | The current menu structure is WAY to complex for merchants, especially as it shows them many options that may not apply to their user type. Please do the following: * rename "Interface" to "Personalization" * under Interface, add a new drop-down setting "Profile" with choices like - Farm shop (Orders, Templates) - Online Point of sale (Orders, inventory, categories) - Offline Point of sale (Orders, inventory, categories, Templates, OTP devices) - Digital publishing (Orders, Templates, soon: Token families) - E-commerce (Orders, Inventory, Webhooks) - Vending machine (Orders, soon: templates with v1) - Expert (all stable, including bank account adding *with* revenue API) - Developer (all) Naturally, we always show "bank accounts" and "access tokens" and --if action is required or in expert/dev mode-- the KYC status. Clemens may (eventually) give you a longer list of profiles and which menu items to enable for each (the above is just a first rough cut), so make sure to make it easy to extend the list. The existing settings "Advanced order creation" becomes part of 'expert', and 'developer mode' is also obsoleted by the above choice. Like the existing other interface settings (language and date format), the new option should be persisted client-side in local storage. | ||||
| Tags | No tags attached. | ||||
| related to | 0010596 | assigned | sebasjm | Taler | Taler Merchant Backend SPA, "KYC status" menu [nice-to-have for target version 1.2] |
| has duplicate | 0010591 | closed | Florian Dold | Taler | Taler Merchant Backend: Profile creation for merchant user groups [nice-to-have for target version 1.2] |
|
|
should we have a default ? Maybe also being able to select the profile on self provision. I suspect that this is going to be saved on local storage? That will be lost if opened from another browser |
|
|
Yes, I know local storage won't be available in another browser. I still think this is the right choice for this setting for now. As for a default, I'm not sure we can safely pick one. Maybe best to ask the user explicitly to provide this (so if the option is not set, show a dialog to ask them what profile they want to use)? |
|
|
Hernâni and me were asked to provide insights from our Merchant Backend testing. We filled in a feature matrix today with our comments and recommendations. Clemens will probably condense the findings and forward them. There are some hints from my side to render to the main menu list a better structure, so better wait for Clemens' summary (if any). Here is one other hint I would like to share now and here when looking at the description above: Farm shop owners would likely be pleased to see the "inventory" option in the main menu as they are often not disposing of an ERP program or inventory management app and could be found of our FLOSS solution (or maybe give up an existing non-free software for inventory management). So better keep the options orders, inventory, templates for farm shops. |
|
|
Well, *today* the inventory management wouldn't work for them, as the QR code templates wouldn't work with the inventory. So that makes no sense. Once Bohdan has finished the templates v2 implementation, I agree: then we should enable the inventory. |
|
|
"Interface" should be renamed to "Personalisation" |
|
|
Stefan: that's already the first bullet point of the description. Please avoid adding noise. |
|
|
British English, please. |
|
|
Spec for this: https://docs.taler.net/design-documents/074-merchant-backend-simplification.html |
|
|
I've elaborated on DD74 some more... |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-11-10 23:43 | Christian Grothoff | New Issue | |
| 2025-11-10 23:43 | Christian Grothoff | Status | new => assigned |
| 2025-11-10 23:43 | Christian Grothoff | Assigned To | => sebasjm |
| 2025-11-11 17:56 | sebasjm | Note Added: 0026385 | |
| 2025-11-11 18:00 | Christian Grothoff | Note Added: 0026386 | |
| 2025-11-11 20:38 | Stefan | Note Added: 0026387 | |
| 2025-11-11 21:05 | Christian Grothoff | Note Added: 0026389 | |
| 2025-11-12 23:13 | Stefan | Note Added: 0026412 | |
| 2025-11-12 23:15 | Christian Grothoff | Note Added: 0026413 | |
| 2025-11-12 23:15 | Stefan | Relationship added | related to 0010591 |
| 2025-11-12 23:20 | Stefan | Note Added: 0026414 | |
| 2025-11-12 23:33 | Stefan | Relationship added | related to 0010596 |
| 2025-11-12 23:44 | Christian Grothoff | Priority | high => urgent |
| 2025-11-12 23:44 | Christian Grothoff | Target Version | 1.5 => 1.2 |
| 2025-11-13 17:25 | Florian Dold | Relationship replaced | has duplicate 0010591 |
| 2025-11-13 17:30 | Florian Dold | Note Added: 0026427 | |
| 2025-11-13 17:39 | Christian Grothoff | Note Added: 0026428 |
