Instead of using the best rate's amount, use the best rate itself

Created on 18 February 2025, 16 days ago

Problem/Motivation

Currently, inside the "ShippingRatesSubscriber" "filterBestRate" method, if the current rate is a "best_rate" (best rate group), we are going over the "saved_rates" (the eligible rates being shown) and use the cheapest rates price, as the price of our "best rate" shipping rate. Which can then be selected by our end user.

Unfortunately, this causes the "Best Rate" Shipping Method to be referenced by the shipment instead of the ACTUAL rate with the best price (and its shipping method).

This causes issues when processing orders, as they don't reference the correct shipping method.

Steps to reproduce

Proposed resolution

Use and reference the shipping rate entity with the best price instead of the "best rate" shipping method entity.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡©πŸ‡ͺGermany Grevil

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024