Overview
The Carrier Errors page gives you direct visibility into carrier label generation and rate call failures — errors that previously had no record you could review inside Logiwa IO. The page only displays failed calls, so every entry you see represents something that needs attention. Each failure is logged with details like the carrier, the error returned, and how long the call took, so you can investigate and resolve issues without contacting support.
When to Use It
Use the Carrier Errors page when:
A shipping label failed to generate for an order and you need to know why
A carrier rate call (rate shopping/quote request) is failing or returning no rates
You want to check whether a specific carrier connection or setup is failing repeatedly
You need the original request payload sent to a carrier to investigate further
Where to Find It
The Integrations navigation is organized into three sections:
Section | Contains |
Plugin Integrations | Store and Marketplace, Shipping (plus a Channel Logs group: Channel Methods, Channel History, Orders and Shipments, Products and Inventory) |
Channel Monitoring | Channel Health Overview, Channel Setup Details, Missing Shipment Orders, Recent Errors, Workflow Blocked Shipment Orders, Product Listing Exceptions |
Carrier Monitoring | Carrier Errors |
💡 Don't confuse Carrier Monitoring with Channel Monitoring — Channel Monitoring covers sales channel/store order errors, while Carrier Monitoring covers carrier label and rate call errors.
Step-by-Step Instructions
Navigate to Integrations.
Under the Carrier Monitoring column, click Carrier Errors.
On the Carrier Monitoring screen, select the tab for the type of failure you want to review:
Label Generation — errors that occurred while generating a shipping label
Rate Call — errors that occurred while requesting rates from a carrier. This tab uses the same columns and filters as Label Generation.
Use the Search by shipment order field, or click Filter to narrow the list (see Filtering below).
To download the original request sent to the carrier for a specific error, click the ⋯ icon at the end of the row and select Download Request.
Confirm: you should see a list of carrier call failures with the carrier, error message, and response time for each.
Filtering
Click Filter to open Select Filter Type, then choose New to build a filter or Saved to reuse one. You can search for a filter by name or choose from the list, which includes:
Carrier Connection
Carrier Setup Name
Client
Created Date
Is International?
Is Rate Shopping?
Return Label
Shipment Order Code
Warehouse
Each filter can be bookmarked (🔖) for quick reuse or added (+) directly to your current view.
Key Fields & Options
(columns are shared by both the Label Generation and Rate Call tabs)
Field | Description | Notes |
Timestamp | Date and time the call was attempted |
|
Integration Step | The step in the process where the call occurred | e.g., "LabelGeneration" |
Client | The client associated with the shipment order | Relevant for 3PL setups |
Shipment Order | The Logiwa shipment order code | Click the icon next to it to open the order |
Status | Result of the call | This page only lists failures, so Status always shows Error |
HTTP Code | The HTTP status code returned by the carrier's API | A code like 200 can still be logged as an Error if the carrier returned an error inside a successful response |
Error | Summary of the error message returned by the carrier | Truncated in the grid |
Response Time | How long the carrier took to respond (ms) |
|
Carrier Connection | The carrier plugin used | Shown as the carrier's logo (UPS, EasyPost, Stamps.com, eHub, etc.) |
Carrier Setup | The specific carrier configuration used | e.g., "UPS-Main" |
Carrier | The actual carrier processing the request | e.g., ups, usps |
Shipping Option | The requested service level | e.g., "2nd Day," "Priority" |
User | The user that triggered the call |
|
Source | The action that triggered the call | Shows "CreateLabel" on the Label Generation tab |
Common Questions & Edge Cases
Why does an error show HTTP Code 200?
An HTTP 200 means the carrier's API accepted the request, but the response body itself contained an error (for example, an invalid address message). Logiwa IO still logs this as a failed call because label generation didn't succeed, even though the transport-level call returned a success code.
What's the difference between Carrier Connection and Carrier Setup?
Carrier Connection is the carrier plugin or provider (UPS, EasyPost, Stamps.com, eHub, etc.). Carrier Setup is the specific configured connection you created in Logiwa IO for that carrier (for example, "UPS-Main").
Does this page show successful calls too?
No. The Carrier Errors page only lists failed calls. If a label or rate call succeeds, it won't appear here.
Can I see the carrier's full response, not just the request?
Not yet. In this release, you can download the original request sent to the carrier via Download Request. Full request/response visibility in the UI, along with an error-guidance drawer to help resolve errors directly from this screen, are planned for upcoming releases.
Related Articles