Magento changed the entity type of $order after calls $invoice = $this->_invoiceService->prepareInvoice($order);

[RadarsofthouseDev]

Preconditions and environment

• Magento version: 2.4.8-p2

Steps to reproduce

1. Create a custom script or use a module with the following code:

/** @var \Magento\Sales\Api\OrderRepositoryInterface $orderRepository */
/** @var \Magento\Sales\Model\Service\InvoiceService $invoiceService */

$orderId = 7030365; // use a valid order_id that can be invoiced
$order = $orderRepository->get($orderId);

$this->_logger->info("Before entity type: " . $order->getEntityType());
$invoice = $invoiceService->prepareInvoice($order);
$this->_logger->info("After entity type: " . $order->getEntityType());`

2. Run the custom script.

Expected result

Before entity type: order
After entity type: order

Actual result

Before entity type: order
After entity type: invoice

Additional information

The $order object’s entity type changes to invoice after calling prepareInvoice().
$order should always remain of entity type "order".

Impact:
This behavior can cause unexpected side effects:
Other logic using the same $order object may incorrectly treat it as an invoice.
Leads to data integrity issues and inconsistent behavior.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @RadarsofthouseDev. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Hotel. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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-Hotel]

Hello @RadarsofthouseDev,

Thanks for the report and collaboration!

We have tried to reproduce the issue in the latest 2.4-develop branch and the issue seems reproducible for us. The entity type has changed from order to invoice after prepareInvoice() method call.

Hence confirming the issue.

Thank you for bringing this issue to our attention. If you have a potential solution, we encourage you to submit a pull request. Your contributions significantly enhance Magento Open Source for everyone. Should you need any assistance, please don't hesitate to ask!

Thanks