Invoice PDF on frontend does not use configured logo image

[jigar48]

I have installed the Magento 2.3.2.

I have uploaded custom logo on Stores -> Configuration -> Sales -> Sales ->Invoice and Packaging Slip Design.
https://prnt.sc/pawmig

I have placed test order and created invoice for that order.

I have print the invoice from the front end customer account page under the My orders and this is what I am getting.
https://prnt.sc/pawngp

I have print the same invoice from the back end : sales -> order -> invoice -> print -> https://prnt.sc/pawnvs
This is what I am getting https://prnt.sc/pawo9h

Preconditions (*)
I have installed the Magento 2.3.2.

I have uploaded custom logo on Stores -> Configuration -> Sales -> Sales ->Invoice and Packaging Slip Design.
https://prnt.sc/pawmig

Information on your environment
I have installed the Magento 2.3.2.

Steps to reproduce (*)
I have installed the Magento 2.3.2.

I have uploaded custom logo on Stores -> Configuration -> Sales -> Sales ->Invoice and Packaging Slip Design.
https://prnt.sc/pawmig

I have placed test order and created invoice for that order.

I have print the invoice from the front end customer account page under the My orders and this is what I am getting.
https://prnt.sc/pawngp

I have print the same invoice from the back end : sales -> order -> invoice -> print -> https://prnt.sc/pawnvs
This is what I am getting https://prnt.sc/pawo9h

Expected result (*)
Invoice print should be contains the same logo in the header either It should be print from the front end or back end. (Added:) If it shouldn't that has to be mentioned somewhere in the comments or official User Guide documentation.

Actual result (*)
https://prnt.sc/pawngp - front end invoice print
https://prnt.sc/pawo9h - back end invoice print
(Added:) It is nowhere officially specified that the Logo for PDF print-outs is meant to be exclusively for Backend print-outs.

[m2-assistant]

Hi @jigar48. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@jigar48 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hello @jigar48. Thanks for reporting. Backend and Frontend invoice pdfs use quite different templates so they look quit differently as it is logically supposed to be. The invoice available on Frontend is shop styled and is just an acknowledgement for a customer that his or her order has been invoiced while the invoice printed out from backend is business styled and is designed to be used in a company's account, bookkeeping and other official document flow. With that the Frontend invoice uses the logo of the store while the Backend logo is set separately. Probably there's a little bug in this comment "Your default logo will be used in PDF and HTML documents." saying nothing about the logo being used only for Backend printing. What do You think of it.

[jigar48]

There is no place where mentioned that Logo should be use for the back end purpose only. and one more thing that the logo which we upload in to sales -> invoice and packing slip design, there is 2 field Logo for Print and Logo for HTML Print layout.

Now Logo For the HTML print layout should not be part of the Backend. because that is only possible in the Front end side under the customer account -> My orders page.

so Its typically bug because that logo should be display in the front end print side as well.

[magento-engcom-team]

@engcom-Bravo Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Component: " label(s) to this ticket based on verification result. If uncertain, you may follow the best guess

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-20527 were created

Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.