Hi @sgeleon. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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.

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).
• 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

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.

I have also tried this now its working fine

Are there any actual issues being caused with the hyphen in order string?

I believe alpha numerical with hyphen is widely accepted for order numbers and I have seen other systems use incremental for reorders as well.
IIRC in those systems incremental was used to decrease loading duplicate data as majority of data is copy of original order. Not sure how Magento handles it

@magento give me 2.4-develop instance

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

Hi @engcom-Bravo, here is your Magento Instance: https://e7daaa19f82979722b9e29636ed6d495.instances-prod.magento-community.engineering
Admin access: https://e7daaa19f82979722b9e29636ed6d495.instances-prod.magento-community.engineering/admin_1b88
Login: a8900544
Password: e1717c92f1e3

Hi @sgeleon,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

The order number is the same 8 digits as the previous order with “-1” added to the end.from frontend it is working fine.

Hence Confirming the issue.

Thanks.

✅ Jira issue https://jira.corp.adobe.com/browse/AC-12854 is successfully created for this GitHub issue.

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
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.

Hi @AndresInSpace
Yes, the issue is from a logical standpoint from the admin/custommer side, the "-1" order number and "Link to previous order" have always been reserved for when orders are edited.

When an order is edited, the original order is cancelled and a new one is made to replace it. Therefore, it makes sense to have a "-1" appended to the order number and a "Link to the previous" order on the order view page because the new order replaces the old one.

When you use the reorder button you are telling Magento you want to place a brand new order that is similar to the previous one but that does not replace it. The reorder button is just a shortcut to order the same products for the same client instead of having to go through the new order process from scratch. It doesn't make any sense from the admin or customer side to use "-1" and "Link to the previous order" in this case.

Magento previously treated editing and reordering differently, now it is treating them the same. This is incorrect.

for anyone else experiencing this issue i opted to revert some of the changes that were made in #37298

diff --git a/Model/AdminOrder/Create.php b/Model/AdminOrder/Create.php
index 4b1868e..a791e2f 100644
--- a/Model/AdminOrder/Create.php
+++ b/Model/AdminOrder/Create.php
@@ -2044,10 +2044,8 @@ class Create extends \Magento\Framework\DataObject implements \Magento\Checkout\
     private function beforeSubmit(Quote $quote)
     {
         $orderData = [];
-        if ($this->getSession()->getReordered() || $this->getSession()->getOrder()->getId()) {
+        if ($this->getSession()->getOrder()->getId()) {
             $oldOrder = $this->getSession()->getOrder();
-            $oldOrder = $oldOrder->getId() ?
-                $oldOrder : $this->orderRepositoryInterface->get($this->getSession()->getReordered());
             $originalId = $oldOrder->getOriginalIncrementId();
             if (!$originalId) {
                 $originalId = $oldOrder->getIncrementId();
@@ -2074,16 +2072,12 @@ class Create extends \Magento\Framework\DataObject implements \Magento\Checkout\
      */
     private function afterSubmit(Order $order)
     {
-        if ($this->getSession()->getReordered() || $this->getSession()->getOrder()->getId()) {
+        if ($this->getSession()->getOrder()->getId()) {
             $oldOrder = $this->getSession()->getOrder();
-            $oldOrder = $oldOrder->getId() ?
-                $oldOrder : $this->orderRepositoryInterface->get($this->getSession()->getReordered());
             $oldOrder->setRelationChildId($order->getId());
             $oldOrder->setRelationChildRealId($order->getIncrementId());
             $oldOrder->save();
-            if ($this->getSession()->getOrder()->getId()) {
-                $this->orderManagement->cancel($oldOrder->getEntityId());
-            }
+            $this->orderManagement->cancel($oldOrder->getEntityId());
             $order->save();
         }
     }