When an error message appears during the quoting process, it is typically generated by our core system (the "back end" API) that powers the ShipHero web and mobile apps. These messages are designed to help you identify exactly where a configuration or shipment detail may need to be adjusted.
How "Cheapest" Quoting Works
To ensure you get the best possible rate, ShipHero communicates with all of your connected carriers simultaneously. Each carrier provides quotes for multiple shipping methods, which our system then compares to find the lowest price.
Because this process involves several external systems, you may occasionally see an error message. This notification appears if at least one carrier is unable to complete the request or encounters an issue while generating a quote.
The carriers that had errors are listed, followed by two links:
- View error details: a list of errors by the carrier.
- View service response: the JSON response as provided by the quoting service.
Understanding Error Details
The user can get more information on what went wrong with quoting these carriers by clicking View error details.
When multiple carriers are involved, we break down the feedback so you know exactly where the issue lies. You will see a list of each carrier that encountered an issue, followed by the specific error messages they returned.
Keep in mind:
General vs. Specific Errors: An error message may apply to the carrier’s overall service rather than one specific shipping method.
Partial Success: It is common for a carrier to successfully provide quotes for some shipping methods while still reporting errors for others. If you see both a price and an error for the same carrier, you can still proceed with the available quotes.
The quality of the message will vary. Some error messages may contain code but still be legible and understandable (e.g. b'{”status”:”blocked_too_many_attempts”}'). However, engineering should be aware of error messages a user would need help understanding.
Understanding Service Response
Users and support people can also access the raw response of the quoting service by clicking on View service response.
This may provide further insight into what went wrong beyond what the quoting and error messages provided.
The service response section was meant as a substitute for a proper error details section, and now that we have one, it will be removed once users get a chance to get accustomed to it.