Allow for more control over receipt emails to comply with fiscal regulations

Other Development Issue

Summary

Describe the issue
To comply with (European) regulations, the receipt that is sent via the email, whether or not it's additionally printed as a physical copy, shall not be different than the original receipt. Currently, the receipts are parsed from OPOS to HTML, get stripped of any logos or images and will then only be added as a variable inline of the HTML email. This makes the receipt look incorrect and especially the fact that any logos/images are stripped and it's also removing the required fiscal QR code is incorrect.

Version and Error Info
Commerce SDK Component: Workflows
Component Version: 9.54.25225.4
Commerce SDK Version: 9.54.25225.4
Exception/Error Details: N/A

Reproducing the Issue

Link to GitHub repo/solution where the issue is reproducible: N/A

Steps to reproduce the behavior:

1. Set up receipt profile
2. Design receipt + save
3. Design email template (with the %message% variable), save and apply it to the receipt profile
4. Run CDX job 1090
5. Sing on to POS, make a sale, print the physical receipt and send it to your email address
6. See major difference between printed receipt and emailed receipt, including: no logo, no other images, no fiscal QR code, receipt just part of the email body.

Screenshots

N/A, specific ones can be provided upon request

I would like to see options to control with parameters whether logos are stripped or be able to change the behavior with an extension directly. The relevant helper class and its methods are public but part of the Workflow namespace which is neither extensible, nor accessible. Additionally, a redesign of the receipt emails may be useful to support more variables or an option to define custom variables to be used in the receipt email. Also, barcodes shall be printed correctly as images / svgs, which could be done with a package. If not possible, their OPOS code should be removed, so <B:...> is not actually part of the email body as plain text. Ideally, the receipt could be sent as a PDF attachment depending on the set parameters.

This is mandatory as not every customer will want / need a physical receipt but opts to receiving it via email. Still, regulations would need to be adhered to and include the fiscal QR code (also) within the receipt email.

Start with the receipt profile and email template flow using the %message% variable, then trace the OPOS-to-HTML parsing used when CDX job 1090 processes the profile. Compare the emailed output with the physical POS receipt, including logos, images, fiscal QR codes, and barcodes; done should be defined by the chosen control or extension behavior and its validation.