How should parcel shipping software handle exceptions across carriers?
Key Takeaways
Parcel shipping software should handle exceptions across carriers by translating each carrier's exception codes into a small set of common types, sending each type through one playbook, and closing it only with evidence. An AI logistics coordinator should work one queue for all carriers, so the team does not chase the same problem differently in each carrier's portal.
- A parcel exception is any event that stops a package from being delivered as planned, such as an address problem, damage, a delay, or a failed delivery attempt.
- Each carrier reports exceptions with its own codes and wording. The same problem can look different across carriers.
- Common types make exceptions comparable and let one playbook handle them all.
- One queue across carriers keeps exceptions from hiding in separate portals.
- Each exception needs an owner, a next step, and a closing piece of evidence.
- Wilson, by Cartage, is an AI logistics coordinator that supports parcel workflows within the agreed customer scope, tracks shipments, and follows up on exceptions within the customer's rules.
Why are parcel exceptions harder to manage across carriers?
Parcel exceptions are harder to manage across carriers because each carrier describes the same problem in its own words, in its own system. An AI logistics coordinator should translate those descriptions into common types, so the team can act on them the same way.
A distributor that ships with two or three parcel carriers may see exceptions like "address information required," "consignee not available," "delivery attempted," "shipment exception," or "delay." Each carrier uses its own codes. One carrier's "exception" may mean a weather delay; another's may mean an incorrect address. Without translation, coordinators must learn each carrier's language and check each carrier's portal.
The table below shows how carrier messages can map to common types.
| Common type | Examples of carrier wording | Typical next step |
|---|---|---|
| Address problem | Incorrect address, address information required | Confirm correct address with customer; update carrier |
| Recipient unavailable | Delivery attempted, business closed | Confirm delivery window; arrange redelivery or pickup |
| Delay in network | Weather delay, operational delay | Confirm new date; tell customer if needed |
| Damage | Damaged, package being repackaged | Start claim; decide on reship |
| Refused | Refused by recipient | Ask customer why; arrange return or reship |
| Lost or no movement | No scan for several days | Open trace; decide on reship |
| Held at location | Held at carrier facility | Arrange pickup or redelivery |
These mappings are examples. Each carrier's actual codes should be reviewed and mapped during setup.
The cost of unworked exceptions
An exception that sits unworked can turn into a return, a lost sale, or a claim past its deadline. A package held at a carrier facility for a few days may be returned to the shipper, adding cost and delaying the customer. A damaged package not reported in time may lose its claim. An AI logistics coordinator that works each exception promptly keeps these costs small.
One queue instead of many portals
When exceptions live in each carrier's portal, someone must check every portal every day. On a busy day, one gets skipped. One queue, fed by every carrier's exceptions, shows all problems in one place, sorted by urgency. An AI logistics employee can build that queue and work it.
Who should own the queue
One person or team should own the exception queue each day. Often that is customer service or a logistics coordinator. Without an owner, the queue becomes another inbox nobody empties. An AI logistics coordinator can work most items in the queue, and the owner reviews what is left and handles the judgment calls.
Same problem, same response
A customer who moved should be handled the same way whether the package went by one carrier or another. Common types let the team write one playbook per problem. A playbook is a written set of steps for a situation. The AI logistics coordinator follows the playbook for each type and adds the carrier-specific steps where needed.
Exceptions start before pickup
Some exceptions start in the shipper's own process. A wrong address in the order system, a missing phone number, or a box that is too heavy for its label all create exceptions later. Catching these at label time prevents them. An AI logistics coordinator can check addresses, weights, and required fields before the label prints, and flag orders that will likely fail.
Why parcel exceptions add up
Each parcel exception is small. But a shipper sending hundreds of packages a day may have many exceptions each week. Each one takes a few minutes to investigate and fix. Together they can fill a coordinator's day. Handling them through one queue and clear playbooks cuts that time.
How should exceptions be classified and prioritized?
Exceptions should be classified into common types and prioritized by customer impact and urgency. An AI logistics coordinator should work high-priority exceptions first and handle routine ones under rules.
Start with the most common types
Most parcel exceptions fall into a few types: delays, address problems, and failed delivery attempts. Writing clear playbooks for these first covers most of the volume. Rarer types, such as customs holds on international parcels or hazardous material issues, can be added later. An AI logistics coordinator can show which types occur most, so the team writes the most useful playbooks first.
Priority factors
| Factor | Higher priority when |
|---|---|
| Order urgency | The order is marked urgent or time-critical |
| Customer | The customer is a key account |
| Value | The package contents are high value |
| Exception type | Damage, lost, or refused |
| Time left | The promised delivery date is close |
Age matters
An exception that is three days old is more serious than one that appeared an hour ago. Older exceptions are closer to return deadlines and claim limits, and the customer has waited longer. The queue should show each exception's age and push older ones up. An AI logistics employee can apply age-based rules, such as escalating any exception open more than two business days.
Routine versus urgent
A one-day weather delay on a standard order is routine. A lost package with a replacement part for a customer's broken machine is urgent. The software should sort exceptions so urgent ones reach a person quickly. An AI logistics employee can handle routine exceptions under rules and escalate urgent ones.
Exceptions on multi-box shipments
A shipment of several boxes may have an exception on one box while the others deliver. The customer may receive a partial order. The exception should be linked to the order, so the team sees that the order is incomplete. An AI logistics employee can track each box and tell the customer which part is delayed.
Map codes once, use them always
Mapping carrier codes to common types is setup work. Once done, every new exception is classified automatically. The map should be reviewed when carriers change their codes or when a new carrier is added. An AI logistics coordinator can flag codes it has not seen before for a person to map.
Group related exceptions
A storm can delay hundreds of packages at once across carriers. Treating each as a separate exception floods the queue. Grouping them by cause, such as "weather delay in the Northeast," lets the team handle them together. An AI logistics employee can group delays with the same cause and send one summary, then handle any that need individual follow-up.
Hypothetical example: a mixed morning
This example is hypothetical and does not describe a real customer. A medical supply distributor starts the day with 23 parcel exceptions across three carriers. The AI logistics coordinator classifies them: 14 network delays, 4 address problems, 2 recipients unavailable, 2 damaged, and 1 with no movement for four days. It sends customers routine delay messages where the date changed, contacts customers to fix addresses, and arranges redelivery for the unavailable recipients. It sends the two damage cases and the no-movement case to customer service with the facts. The team reviews five exceptions instead of 23.
What should the playbook for each exception type include?
Each playbook should include the first action, the information needed, the owner, the customer message, and the evidence that closes the exception. An AI logistics coordinator should follow the playbook and record each step.
Fix the root cause
Each exception has a cause. Address problems often come from incomplete customer records. Failed deliveries often come from receivers with short hours. Damage may come from weak packaging on certain products. Recording the cause lets the team fix the source, not only the symptom. An AI logistics employee can tag each exception with its cause and show the most common causes each month.
Address problems
The first action is to confirm the correct address with the customer. The information needed is the full address, including suite numbers and contact phone. The owner is usually customer service or the AI logistics coordinator. The carrier is updated through its process. The exception closes when the carrier confirms delivery. Address corrections may carry a carrier fee. The record should note the cause, so the customer's address can be fixed in the system for next time.
Hypothetical example: a held package
This example is hypothetical and does not describe a real customer. A distributor's package is held at a carrier facility after two failed delivery attempts at a business that closes at 4 p.m. The AI logistics coordinator contacts the customer, who asks for delivery before noon. The coordinator requests a morning redelivery through the carrier's process. The package delivers the next morning, before the carrier's hold period would have sent it back.
Recipient unavailable
The first action is to confirm when the recipient can receive. Some carriers attempt redelivery automatically; others hold the package. The playbook should say whether to request redelivery, arrange pickup, or wait. The exception closes on delivery.
Record every address fix
When a customer confirms a corrected address, update the order system too. An AI logistics coordinator can tell customer service which records to fix, so the same error does not repeat.
Delay in network
The first action is to get the carrier's new expected date. If the delay moves delivery past the promise, the customer should hear. If not, no customer message is needed. The exception closes on delivery.
Delays that need no action
Many network delays clear within a day and do not change the promised date. These need no customer message and no person. An AI logistics coordinator can record them, confirm delivery when it happens, and close them quietly. Keeping these out of people's view leaves time for the exceptions that matter.
Damage
The first action is to record the damage and decide whether to reship. The claim process follows the carrier's rules and deadlines. The owner is usually customer service or a claims owner. The exception closes when the replacement arrives and the claim is filed.
Reship rules
A reship decision should follow a rule: for example, reship immediately for urgent orders, or after a trace confirms loss for standard orders. The rule should say who approves the cost and which service to use. An AI logistics coordinator can apply the rule and record the reship with the original exception, so both packages are tracked together.
Refused
The first action is to ask the customer why. The package may be wrong, damaged, or not needed. The playbook should cover return, reship, or credit. The owner is customer service.
Returns need their own playbook
Refusals, failed deliveries, and customer returns all send packages back. The shipper needs to know what is coming back, when, and in what condition. The warehouse needs to receive it and decide whether to restock, repair, or scrap. An AI logistics coordinator can track returns as their own shipments and tell the warehouse when they will arrive.
Lost or no movement
The first action is to open a trace with the carrier. If the order is urgent, reship without waiting. The exception closes when the original package is found or the claim is filed and the replacement delivered.
Carrier-specific steps
Each carrier has its own way to correct an address, request redelivery, or start a trace. The common playbook says what to do; the carrier-specific steps say how. Keeping both lets the team use one playbook while respecting each carrier's process. An AI logistics coordinator should know the carrier-specific steps for each carrier in scope.
Claims deadlines
Carriers set deadlines for filing claims for damage or loss. Missing the deadline can mean losing the claim. The playbook should record each carrier's deadline and the information the claim needs. An AI logistics employee can track open claims against these deadlines and remind the claims owner before they expire.
Playbook summary
| Type | First action | Owner | Closes when |
|---|---|---|---|
| Address problem | Confirm address | AI logistics coordinator, customer service | Delivered |
| Recipient unavailable | Confirm delivery window | AI logistics coordinator | Delivered |
| Delay in network | Get new date | AI logistics coordinator | Delivered |
| Damage | Record, decide reship | Customer service, claims | Replacement delivered, claim filed |
| Refused | Ask customer why | Customer service | Return, reship, or credit done |
| Lost | Open trace | AI logistics coordinator, customer service | Found or claim filed and replaced |
How should customers hear about parcel exceptions?
Customers should hear about parcel exceptions when the exception changes their delivery or needs their input, with a clear next step. An AI logistics coordinator should avoid sending carrier jargon and should not duplicate messages the carrier already sends.
Keep the message history
Every message to the customer about an exception should be saved with the shipment. When the customer calls, customer service can see what the customer was told and when. An AI logistics coordinator can keep that history alongside the exception's steps.
When to tell the customer
- Address problem: always, because the customer must confirm the address.
- Recipient unavailable: when redelivery needs the customer's input.
- Delay: when the new date misses the promise.
- Damage or lost: when a reship is planned, with the new date.
- Refused: the account owner should contact the customer.
Tell the account owner about key accounts
When an exception affects a key customer, the account owner should know before the customer calls. A short internal message, with the order, the problem, and the plan, lets the account owner reach out first. An AI logistics employee can send this message when the exception's customer is marked as a key account.
Avoid duplicate messages
Many parcel carriers send their own delivery notifications to recipients. If the shipper also sends messages, the customer may receive two different updates. Decide which messages the shipper sends and which it leaves to the carrier. An AI logistics employee can send only the messages the carrier does not cover, such as a reship plan.
Ask for the customer's input once
When an exception needs the customer's input, such as an address or a delivery time, ask once, clearly, with a deadline. Repeated vague requests annoy customers. An AI logistics coordinator should send one specific request and follow up only if no answer arrives by the deadline.
Plain words, clear next step
A customer message should say what happened in plain words and what happens next. For example: "Your package for order 33910 was damaged in transit. We have shipped a replacement today, arriving Thursday." The customer does not need the carrier's exception code.
Internal teams need a different view
Customer service, sales, and the warehouse each need different parts of the exception picture. Customer service needs the open exceptions by customer. Sales needs to know when a key account is affected. The warehouse needs to know about reships and returns. An AI logistics coordinator can send each team the part it acts on, through its preferred channel.
Hypothetical example: an address fix
This example is hypothetical and does not describe a real customer. A parts distributor's package shows "address information required." The AI logistics coordinator emails the customer: "We need your suite number to complete delivery of order 41207." The customer replies with "Suite 300." The coordinator updates the carrier, and the package delivers the next day. Customer service also updates the customer's address in the order system.
How should you evaluate parcel software on cross-carrier exceptions?
Evaluate parcel software by feeding it exceptions from each of your carriers and checking whether they land in one queue, map to the right types, and follow the right playbooks. An AI logistics coordinator should resolve routine exceptions and route the rest with facts.
Demo tests for cross-carrier exceptions
| Buyer requirement | Demo test | Evidence to see |
|---|---|---|
| One queue | Load exceptions from three carriers | All in one list |
| Common types | Use different wording for the same problem | Same type assigned |
| Priority | Mark one order urgent | Urgent exception at the top |
| Playbooks | Trigger an address problem | Customer asked, carrier updated |
| Damage handling | Trigger a damage exception | Reship decision and claim owner notified |
| Customer messages | Trigger a delay past the promise | Clear message, no duplicate |
| Closing evidence | Close an exception | Delivery or claim evidence saved |
Test a new exception code
Ask the vendor to feed in an exception code the system has not seen. Watch whether the AI logistics coordinator flags it for mapping rather than ignoring it or forcing it into the wrong type. New codes appear when carriers change their systems.
Demo questions about cross-carrier exceptions
- How are each carrier's exception codes mapped to common types?
- What happens with a code the system has not seen before?
- How are exceptions prioritized?
- Which exceptions can the AI logistics coordinator resolve under rules?
- How are claims tracked to completion?
- Can we see exceptions by carrier and type over time?
Compare carriers fairly
Exception rates differ by carrier, but also by lane, package type, and destination. A carrier with more exceptions may be serving harder areas. Compare carriers on similar shipments before drawing conclusions. Wilson can use shipment data from the loads it runs to produce carrier-performance reports on request, which can support fair comparisons.
How to measure cross-carrier exception work
Track the time from exception to resolution by type. Count exceptions resolved without a person. Compare exception rates by carrier. These measures show whether the AI logistics employee reduces parcel exception work.
Use a week of your real exceptions
Give the vendor a week of your real parcel exceptions from each carrier. Ask it to classify them, prioritize them, and show the next step for each. Your own exceptions show whether the mapping and playbooks fit your carriers.
Scoring the cross-carrier exception demo
Score each test as pass, partial, or fail. A pass means the exception was classified, handled by the playbook, and closed with evidence. A partial means it was classified but a person did the follow-up. A fail means it stayed in a carrier portal.
Warning signs in a cross-carrier exception demo
- Each carrier's exceptions appear on a separate screen.
- Exceptions show raw carrier codes only.
- There is no priority order.
- Customers receive carrier jargon.
- Exceptions close without evidence.
Where does Wilson fit in cross-carrier parcel exceptions?
Wilson, by Cartage, is an AI logistics coordinator that supports parcel workflows within the agreed customer scope. It tracks shipments using the best source available and follows up on exceptions within the customer's rules.
Wilson replaces the TMS for freight execution and connects to the company's ERP through a method that fits the customer's environment. It sends internal updates through channels such as Slack, Microsoft Teams, or email, and can notify consignees by email or SMS where configured.
What Wilson records
Wilson keeps searchable shipment records with change history. A team can see each exception, its type, the steps taken, and the result. Wilson audits and reconciles carrier invoices against what was booked, which helps catch exception-related charges such as address correction fees.
What Cartage asks about parcel exceptions in discovery
Cartage asks which parcel carriers the team uses, which exceptions are most common, who handles claims, and how customers are told today. These answers shape the exception types and playbooks an AI logistics coordinator follows.
What Wilson does not do for parcel exceptions
Wilson does not replace each carrier's claim process. The parcel carriers, exception sources, and playbooks in scope should be confirmed in a demo. Wilson does not claim a ready-made connection to every carrier system. Exact ERP connection details depend on the customer's systems.
Reports for carrier reviews
Exception records by carrier and type help in carrier reviews. A carrier with frequent address-related failures in one region may need a conversation about driver procedures. A carrier with high damage rates on a product line may suggest a packaging change. Wilson can use shipment data from the loads it runs to produce carrier-performance reports on request.
Where teams start with parcel exceptions
Most teams start their AI logistics coordinator on a few lanes and expand from there. Timing depends on scope. Cartage helps identify the first workflow during discovery. Teams often start with address problems and delays, which are frequent and follow clear playbooks.
Teams writing playbooks can use a freight exception response playbook. Teams handling split shipments can see how shipment notification tools handle split orders across carriers. Both topics shape how an AI logistics coordinator handles parcel exceptions. Teams handing off between carriers can review how a parcel handoff with FedEx and UPS works.
FAQs
How should parcel shipping software handle exceptions across carriers?
Translate each carrier's codes into common types, put all exceptions in one queue, and follow a playbook for each type. An AI logistics coordinator should close each exception only with evidence.
Why map carrier exception codes to common types?
The same problem looks different across carriers. An AI logistics employee can handle it the same way once it is mapped to a common type.
Which parcel exceptions need a person?
Damage, lost packages on urgent orders, refusals, and anything involving a claim. An AI logistics coordinator should route these with the facts ready.
Should the shipper message customers about every parcel exception?
No. Only when delivery changes or the customer must act. An AI logistics employee should avoid duplicating the carrier's own notifications.
Sources
- Cartage, Wilson product scope, October 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator puts exceptions from all your parcel carriers into one queue, fixes an address problem with the customer, and routes a damage case to your claims owner: talk to the Cartage team.