Switch from "invoice" to "order details" in our emails.

[barryhughes]

Submission Review Guidelines:

• I have followed the WooCommerce Contributing Guidelines and the WordPress Coding Standards.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have reviewed my code for security best practices.
• Following the above guidelines will result in quick merges and clear and detailed feedback when appropriate.

Changes proposed in this Pull Request:

We refer to some of our order emails as 'invoices', which turns out to be problematic for some merchants/in some jurisdictions. This change drops the use of 'invoice', preferring 'order details' instead.

Some existing uses of 'invoice' remain in place (for instance, in relation to class and template names) to preserve backward compatibility and minimize disruption.

Closes #26692.

How to test the changes in this Pull Request:

💡 When testing this, you will benefit from the ability to see the emails dispatched by WooCommerce. So long as your site is configured correctly, 'real emails' are fine for this—otherwise you may benefit from a tool such as Email Log.

Open an existing order for editing, and look at the order actions meta box (typically found in the top right of the screen). You should see an entry reading, "Send order details to customer." Previously, this read, "Email invoice / order details to customer."

Select the above option and click on Update. The email should be sent to the customer:

• The email subject should read Details for order #1234 on My Site (of course, the order number and site name will be different). Previously, it was either Invoice for order #1234 on My Site or Your latest My Site invoice (depending on order payment status).
• The email header should simply be Details for order #1234. Previously, it was either Invoice for order #1234 or Your invoice for order #1234.

Now visit WooCommerce ▸ Settings ▸ Emails. You should see an entry for the Order details email (previously was referred to as Customer invoice / Order details):

Finally, consider clicking through via the above admin screen and modifying the settings for this email. Your changes should be reflected just as they would have been before this PR was written.

Changelog entry

• Automatically create a changelog entry from the details below.

Significance

• Patch
• Minor
• Major

Type

• Fix - Fixes an existing bug
• Add - Adds functionality
• Update - Update existing functionality
• Dev - Development related task
• Tweak - A minor adjustment to the codebase
• Performance - Address performance issues
• Enhancement - Improvement to existing functionality

Message

Comment

[barryhughes]

As was previously true, the email subject and header text can anyway be defined and overridden by the merchant (via the email settings screen). This change is really intended just to tweak the defaults, since use of 'invoice' is problematic in some contexts and geographies.

[webdados]

"Order details" on the order actions menu and as email name is perfect.

I would set the default email subject to "Details for order #1245 on My Site" and "Details for order #1245" as header.

[github-actions]

Test Results Summary

Commit SHA: f608530

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	259	0	0	2	0	261	0m 38s
E2E Tests	344	0	0	8	0	352	7m 19s

---

To view the full API test report, click here.
To view the full E2E test report, click here.
To view all test reports, visit the WooCommerce Test Reports Dashboard.

[barryhughes]

I would set the default email subject to "Details for order #1245 on My Site" and "Details for order #1245" as header.

Thanks, @webdados: updated.

[github-actions]

Hi @jorgeatorres,

Apart from reviewing the code changes, please make sure to review the testing instructions as well.

You can follow this guide to find out what good testing instructions should look like:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

[jorgeatorres]

LGTM. Thank you @barryhughes! Tests well.

Adding that I pushed a tiny commit to fix a typo in a docblock (f608530).

[webdados]

Thanks for this!