
Both shipping price excluded tax

@JoostWan could you please add more details here.
What is "Tax Class for Shipping"? which are Tax Calculation Settings?
Which tax zones/rates do you have? Which of them are enabled by tax rules?
See the settings in the screenshots (Default Magento 2.1.1). The shipping price in the Estimate shipping and tax is tax included. But settings are "Showing excluded tax for shipping". The shipping price in the totals is correct (ex tax).





@JoostWan cannot reproduce the issue from clean installation. Setting from the screenshots are applied.

Could you specify steps?
@JoostWan or do you mean you see $5.00 in shipping methods block, but $4.13 in totals block?
Yes. Shipping price are set to show excluded tax. But shipping price in estimate block is included tax. Thats confusing customers because there a two different prices
Thank you for the report. We created internal issue MAGETWO-58059
Fix has been delivered to develop branch.
This issue was fixed for develop branch.
Closed.
Hi @veloraven,
The issue was reported on Magento 2.1. Please don't close the issue unless the fix is released for 2.1.x branch officially. Until the fix gets into a released version, this issue will persist for ordinary merchants.
If there's some internal policy that says you should close the issue, could you guys at least put a milestone when you're closing the issue so that we see in which future version the fix is planned to be released
I'm seeing the "fixed for develop branch" message used by you ( @veloraven ) as an excuse to close an issue over and over again. After that, the issue seems to become forgotten about, for good. As if you don't care whether the issue is actually resolved for the users.
I've written about that multiple times. Do you not read the messages people address to you? Do I need to redirect this sentiment to @magento-team or @maksek or who-else in order for it to get some kind of response?
@korostii Kudos. Though seeing as how @veloraven hasn't responded in almost three months, I doubt there is a real person behind the name tag. Seems like a programmed auto-response.
Most helpful comment
Hi @veloraven,
The issue was reported on Magento 2.1. Please don't close the issue unless the fix is released for 2.1.x branch officially. Until the fix gets into a released version, this issue will persist for ordinary merchants.
If there's some internal policy that says you should close the issue, could you guys at least put a milestone when you're closing the issue so that we see in which future version the fix is planned to be released
I'm seeing the "fixed for develop branch" message used by you ( @veloraven ) as an excuse to close an issue over and over again. After that, the issue seems to become forgotten about, for good. As if you don't care whether the issue is actually resolved for the users.
I've written about that multiple times. Do you not read the messages people address to you? Do I need to redirect this sentiment to @magento-team or @maksek or who-else in order for it to get some kind of response?