View Issue Details

IDProjectCategoryView StatusLast Update
0004868OXID eShop (all versions)2.6. Administer orderspublic2023-11-17 14:01
Reporterpatchwork.de Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionnot fixable 
Product Version4.7.2 / 5.0.2 revision 53018 
Summary0004868: VAT should be recalculated if admin changing 'country' in delivery adress or adds 'UStID' for customer
Descriptionsee 'steps to reproduce'
Steps To Reproduce1. 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!

TagsOrder, Order Recalculation
ThemeNot defined
BrowserAll
PHP VersionNot defined
Database VersionNot defined

Relationships

related to 0004624 acknowledged Order recalculation does not use discounts/taxes which were valid when order was made, but current ones 
has duplicate 0005000 closedjurate.baseviciene VAT settings when changing delivery options 

Activities

ray

2013-01-24 07:46

reporter   ~0008319

related https://bugs.oxid-esales.com/view.php?id=4624

saulius.stasiukaitis

2015-05-14 16:50

reporter   ~0010953

Related pull request https://github.com/OXID-eSales/oxideshop_ce/pull/232

SvenBrunk

2023-11-17 14:01

administrator   ~0015793

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).