Scale (SDK) orders that use profile switching can fail to rate for some destinations. This happens because Shipstore checks the rate shop on the profile whose API key Scale sends, before the profile switch runs. Add an empty rate shop with a matching API Symbol on that profile and the orders rate.
Problem
Scale (SDK) sends orders that are set up to switch to a destination-specific profile. Rating fails for the destinations that need a rate shop (for example, certain states), while other orders are fine. The error comes up before the profile switch happens.
Cause
Shipstore checks the rate shop against the profile named by the API key in the incoming request. That profile is usually a base or test profile that Scale sends. This check runs before the profile switch. If the base profile has no rate shop that matches the one the target profile uses, the check fails and the order errors, even though the target profile is set up correctly.
How to check: the orders that fail are the ones that rely on a rate shop after the profile switch, and they all come in on the same base or test profile from Scale.
Fix
- Find the profile whose API key the Scale/SDK request sends. This is often a base or test profile.
- Find the rate shop used by the destination profile the order switches to, and note its API Symbol.
- On the API-key profile, add a rate shop with the same API Symbol.
- Leave that rate shop empty. It does not need any services. It only needs the matching API Symbol so the check passes.
- Reprocess an order for one of the destinations that was failing.
What you should see
- Orders for the destinations that were failing now rate and produce labels.
- The API-key profile has an empty rate shop with the matching API Symbol.
Related articles
- Profile switch rule errors when the new profile has no integration
- Rate shop returns no rates and an SDK.PreRate error