View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004868 | OXID eShop (all versions) | 2.6. Administer orders | public | 2013-01-23 19:40 | 2023-11-17 14:01 |
| Reporter | patchwork.de | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | not fixable | ||
| Product Version | 4.7.2 / 5.0.2 revision 53018 | ||||
| Summary | 0004868: VAT should be recalculated if admin changing 'country' in delivery adress or adds 'UStID' for customer | ||||
| Description | see 'steps to reproduce' | ||||
| Steps To Reproduce | 1. customer make an order in a german online shop with adress in Switzerland (VAT is calculated with 0 which is ok) 2. customer sends email 'please ship it to my adress in Germany' 3. admin adds delivery adress in Germany 4. VAT is still 0 which is NOT ok - should be now the german VAT! or: 1. customer make an order in a german online shop with adress in Austria (VAT is calculated with 19% which is ok) 2. customer sends email 'please add my austrian USTID' 3. admin adds USTID in backend 4. VAT is still 19% which is NOT ok - should be now 0! | ||||
| Tags | Order, Order Recalculation | ||||
| Theme | Not defined | ||||
| Browser | All | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
| related to | 0004624 | acknowledged | Order recalculation does not use discounts/taxes which were valid when order was made, but current ones | |
| has duplicate | 0005000 | closed | jurate.baseviciene | VAT settings when changing delivery options |
|
|
related https://bugs.oxid-esales.com/view.php?id=4624 |
|
|
Related pull request https://github.com/OXID-eSales/oxideshop_ce/pull/232 |
|
|
We already discussed this on similar issues e.g. those that complain that recalculating the order in the admin backoffice does not use tax rates that were valid at the time of order. To state it very clearly: Doing something like this is illegal. In Germany this would be Forgery of documents. (An order is such a document) That is also the reason why an order should be read-only. What you can do and what we will probably implement in a better, more automated way in a later release is this: - Reject/Cancel the order - Create a new order with the new data This could be automated including the new order confirmation being triggered to the customer (maybe even with a request to confirm again that he wants this new order). |
