Magento 2 new FedEx api not getting the right price

[ShapesGraphicStudio]

Preconditions and environment

• Magento version: 2.4.7-p2
• FedEx negotiated rates

Steps to reproduce

1. Navigate to store as guest
2. Place order
3. Get FedEx Shipping rates

Expected result

Get our special deal prices

Actual result

Get "normal price

Additional information

Hello,

I just upgraded to 2.4.7-p2 to get the new FedEx api working.

Connection works fine but I'm not getting the right prices for our account.

FedEx tells us that we have a wrong param in the request : "rateRequestType": [ "LIST" ], Should be "rateRequestType": [ "PREFERRED" ],

I could not see this option in admin. Should it not figure there?

I tried to change this directly in vendor/magento/module-fedex/Model/Carrier.php and it seems to do the job. But I also tried to override the Model to avoid update issues without luck.

Any idea on how I could get this fixed please?

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] 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[bot]]

Hi @ShapesGraphicStudio. 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.

[alikhani97]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @alikhani97. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @alikhani97, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[m2-assistant[bot]]

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: :point_down:

• [ ] 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-Bravo]

Hi @ShapesGraphicStudio,

Thanks for your reporting and collaboration.

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

We are able to get the FedEx Shipping rates.Could you please elaborate the steps to reproduce to proceed further and please let us know if we are missing anything.

Thanks.

[Mohamed-Asar]

@engcom-Bravo This issue exist only in REST API method. Please compare the shipping rates for both REST API and SOAP method, you will see rates difference in REST API Response I've verified with fedex team, they said wrong rateRequestType was passed in the request . please see the below screenshot

[ShapesGraphicStudio]

@engcom-Bravo the problem here is not about getting shipping rates but getting the RIGHT rates for us.

We dealed special rates with FedEx, but they were not being displayed to our customers.

FedEx team (commercial and deev) told us us that we have a wrong param in the request : "rateRequestType": [ "LIST" ], Should be "rateRequestType": [ "PREFERRED" ], To have the right price.

After changing that we had the right prices showing, so I think this param should be an option in admin.