|
| Reporter | Christian Grothoff | Assigned To | avalos | Resolution deadline | |
|---|
| Implementer | | Reviewer | | |
|---|
| Release signed by | | Deployed by | | |
|---|
| Verifier | | Communicator | | |
|---|
| Data protection authority notification required | No | | |
|---|
| CSIRT notification required | No | | |
|---|
| Estimated effort (hours) | | Actual effort (hours) | 0 | |
|---|
| Fast-track | No |
|---|
| Work package | none |
|---|
| Priority | normal | Severity | major | Reproducibility | always |
|---|
| Status | implementing | Resolution | open | |
|---|
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
|---|
| Product Version | git (master) | |
|---|
| Target Version | post-1.0 | |
|---|
|
| Summary | 0010288: PoS app does not tolerate mixed currencies in backend products |
|---|
| Description | If you have some product in EUR and another product in KUDOS, the PoS backend fails to accept the configuration.
However, these days the merchant backend is multi-currency capable, so this should work. |
|---|
| Additional Information | We need to figure out what the UX should be. For now, I think the answer has to be that we require the user of the PoS app to select a currency first (implict or explict) and then only show products denominated in that currency afterwards. The issue here is that in the end an order can only be paid in one currency, so we need to know that early with the current setup.
|
|---|
| Tags | No tags attached. |
|---|
|