Shipment exceptions
Group differently worded carrier and driver messages into your internal exception categories.
STAYCHARTED AMT / 3PL · TRUCKING · LOGISTICS
Train StayCharted AI Model Trainer to categorize shipment exceptions, 3PL customer requests, and trucking reports using your team’s approved examples.
FROM YOUR EXAMPLES
Receiver closed. Nobody available to unload.Receiver unavailableIllustrative category · Not a live prediction
Group differently worded carrier and driver messages into your internal exception categories.
Separate shipment holds, receiving shortages, picking discrepancies, and damage reports.
Suggest a review category for charge disputes or maintenance notes so teams can organize their work.
PREPARE YOUR EXAMPLES
Export reviewed customer requests, driver updates, or warehouse exception notes with the category assigned by your operations team. Start with one task, such as shipment exceptions. Include relevant context available at prediction time, such as the service type or customer’s terminology. Remove identifiers that do not explain the category and review sensitive customer or driver information before uploading.
Use one row per example with an approved answer. Keep the input representative of what the model will receive later, and agree on how to label ambiguous cases before training.
| Operational note | Approved category |
|---|---|
| Expected 48 units; counted 42 at receiving. | Receiving shortage |
| At the dock since 08:10; still waiting to unload. | Unloading delay |
| Invoice includes a second delivery attempt we did not request. | Redelivery charge dispute |
| Liftgate stops halfway when loaded. | Liftgate issue |
Illustrative rows and categories. Use your own approved labels.
Resolve inconsistent labels and remove unnecessary sensitive information.
Choose a model on your plan and train on representative examples.
Inspect held-out accuracy by category and the mistakes that remain.
Publish, fill a file or call the API, then review and feed corrections into the next version.
KEEP REVIEW IN THE WORKFLOW
Review ambiguous notes, unfamiliar exception types, and categories whose consequences affect claims, charges, or safety. A category is a suggestion, not a finding of liability or a dispatch instruction. Keep authorized staff and your existing operating rules responsible for action.
A receiving shortage and a picking shortage may need different categories even when both notes say “six units missing.” Train on examples that include the operational context. For customers with different taxonomies, use separate models and manage access through workspaces and roles. Start with customer requests, warehouse discrepancies, or claims intake; do not mix unrelated decisions into one label list.
Categorize receiver-unavailable reports, unloading delays, redelivery disputes, and maintenance requests. An unloading-delay category can flag a message for detention review, but timestamps and contract terms determine whether a charge is valid. A maintenance category helps organize work for a qualified technician; it does not determine whether a vehicle is safe to operate.
Evaluate held-out accuracy by category and inspect errors between similar labels. Include different customers, carriers, facilities, and writing styles in your evaluation. If repeated notes describe the same shipment, keep those records together when preparing separate training and test data. Use confidence to prioritize review and sample apparently confident results too.
Fill a spreadsheet with suggested categories, or have your software call a published model through the API on a supported plan. Your integration uses the returned category to select a queue or update a record. StayCharted does not provide a prebuilt integration with every transport or warehouse platform, optimize routes, track shipments, or execute dispatch actions.
With labeled photos, test categories such as crushed cartons, torn wrapping, or intact packaging using an image model. Use representative lighting, camera angles, and products. Image classification assigns a category to the supplied picture; it does not locate every defect, read shipping labels through OCR, or establish hidden damage. Logistics-specific accuracy must be measured on your own examples.
File fills return category suggestions for your existing import process. API calls return results to your own software; your integration decides how to apply them. Plan allowances and workspace rate limits still apply.
It can suggest categories for customer requests, warehouse exceptions, and claims descriptions using reviewed examples. StayCharted learns the labels you supply; your existing system or team decides what action follows.
Yes. Train separate models where customers use different taxonomies. Use workspace access controls appropriate to your customer separation requirements.
No. It supplies classifications through file processing or an API. Your team builds the integration and keeps transport planning, tracking, inventory updates, and assignments in the existing system.
For text classification, supply text already extracted by your document workflow. You can train document-type categories, but classification does not extract shipment fields, authenticate signatures, or prove delivery.
Choose one recurring task with reviewed examples and clear labels, such as shipment exception classification. Check mistakes and review effort on representative held-out records before expanding.
Free includes text Classifier Models and one AI Classifier Model. Essentials adds API access; Business adds Dedicated AI Models. Vision is an optional add-on on paid plans.