Parts catalogs
For distributors, retailers, and marketplaces: categorize new supplier descriptions into your approved product taxonomy.
STAYCHARTED AMT / AUTOMOTIVE
AI Classification for Automotive Parts, Service & Warranty
Use StayCharted AI Model Trainer to categorize parts descriptions, service notes, and warranty claims. Train on approved examples and review uncertain results.
FROM YOUR EXAMPLES
Front ceramic disc brake pad set, with wear sensor.Braking → Brake padsIllustrative category · Not a live prediction
Where this fits in your work
Service operations
For dealerships, repair chains, and fleet workshops: categorize incoming concerns and service notes for staff to review.
Warranty and claims
For manufacturers, parts suppliers, and warranty teams: organize claim narratives and findings into consistent claim categories.
Catalog and e-commerce teams at distributors, retailers, and marketplaces
Parts catalogs: turn supplier wording into your taxonomy
A supplier calls it a starter assembly; your catalog places it under Electrical → Starter motors. Train on descriptions your team has already categorized, then suggest the same approved labels for incoming listings. Keep the supplier SKU alongside each result for your import process.
| What comes in | Suggested category | Where the result is used |
|---|---|---|
| Supplier CSV: “Front ceramic disc brake pad set” | Braking → Brake pads | Suggest the product category in your catalog import |
| PIM export: “12V starter motor assembly” | Electrical → Starter motors | Review and standardize supplier listings |
| Listing text: “Spin-on engine oil filter” | Filters → Oil filters | Organize products for browsing and reporting |
Illustrative examples using sample category names.
Category assignment does not validate vehicle fitment, interchange numbers, or product specifications. Keep those checks in your catalog and compatibility systems.
Service managers at dealerships, repair chains, and fleet workshops
Service operations: organize the concern before the work begins
Customers and service advisors describe similar concerns in different words. Categorize the reported concern from a booking form, email, advisor note, or transcribed call. A separate model can categorize completed technician findings; do not use a later diagnosis as an input when classifying an initial request.
| What comes in | Suggested category | Where the result is used |
|---|---|---|
| Booking form: “Steering wheel shakes when I brake” | Braking concern | Help service staff review the intake record |
| Advisor note: “Cabin air stays warm with AC on” | Heating and air-conditioning concern | Group requests for scheduling review |
| Transcribed call: “Oil change and scheduled service” | Routine maintenance request | Categorize demand in service reporting |
Illustrative examples using sample category names.
These labels describe reported concerns, not diagnoses. Your team handles urgent symptoms, safety checks, repair advice, and scheduling decisions.
Warranty and quality teams at manufacturers, suppliers, and administrators
Warranty and claims: make incoming case descriptions comparable
Use reviewed claim records to teach the categories your team already applies. Keep the customer’s claim type distinct from a verified failure finding or the coverage decision. Classification can organize incoming cases and support reporting without treating an allegation as a confirmed defect.
| What comes in | Suggested category | Where the result is used |
|---|---|---|
| Claim form: “Mounting tab was broken when the box arrived” | Reported arrival damage | Group cases for damage-evidence review |
| Claim narrative: “Replacement unit stopped working after installation” | Reported functional failure | Organize cases for technical review |
| Return note: “Connector differs from the one on the vehicle” | Reported compatibility issue | Group cases for fitment-record review |
Illustrative examples using sample category names.
The model does not determine cause, fraud, warranty eligibility, or reimbursement. Authorized reviewers apply coverage terms and inspect the evidence.
PREPARE YOUR EXAMPLES
Start with a file your team has already labeled.
Choose one task first: product category, reported service concern, or claim type. Export descriptions and approved labels from your existing system. Use only inputs that will be available when a new item arrives. A part number identifies a record; a useful description tells the model what it is. Keep customer-reported symptoms separate from verified technician findings.
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.
| Task | Input example | Approved category |
|---|---|---|
| Catalog | 12V starter motor assembly | Electrical → Starter motors |
| Service concern | Customer reports steering vibration while braking | Braking concern |
| Claim type | Part received with broken mounting tab | Reported arrival damage |
Illustrative rows and categories. Use your own approved labels.
From examples to reviewed results
Prepare
Resolve inconsistent labels and remove unnecessary sensitive information.
Train
Choose a model on your plan and train on representative examples.
Validate
Inspect held-out accuracy by category and the mistakes that remain.
Use and improve
Publish, fill a file or call the API, then review and feed corrections into the next version.
KEEP REVIEW IN THE WORKFLOW
Know where the model stops.
A category does not verify vehicle fitment, diagnose a mechanical fault, or determine warranty coverage. Keep compatibility checks, repair decisions, safety inspections, and claim approvals with the appropriate systems and qualified people. Do not rely on a category to rule out an urgent safety concern.
Evidence and implementation
Agree on category boundaries
Define what belongs in each category and how to handle overlapping descriptions. A brake-related noise and a confirmed brake component failure answer different questions. For catalog hierarchies, start with one approved target level or a complete category path rather than assuming the model will construct a taxonomy for you.
Check performance before applying results
Review held-out accuracy by category and inspect mistakes. Keep near-duplicate part listings and repeated records from the same service or claim case from giving a misleading picture of performance. Test on new suppliers, unfamiliar descriptions, and the rare categories your team needs to recognize. Confidence helps prioritize review; it is not a guarantee.
Return categories to the systems you use
Fill an exported spreadsheet and use your existing import process, or build an API integration on a supported plan. Your catalog, dealership, workshop, or warranty system receives the category and confidence and decides what happens next. StayCharted does not provide a native connection to every PIM, ERP, DMS, or claims platform.
Prepare documents, calls, and photos
For text classification, provide readable columns or API inputs. Extract text from PDFs and scanned invoices, and transcribe calls, before sending the relevant text. For a separate image task, train on labeled photos of visible conditions such as packaging damage or surface scratches. A photo cannot establish an internal fault or prove that a part is safe.
Improve through reviewed examples
Review uncertain answers and sample confident ones. Correct labels and add representative examples when suppliers, products, or service terminology change. Retrain, compare the report, and publish the version you want to use. Feedback does not silently change your published model.
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.
Common questions
Who is this automotive solution for?
Parts distributors, retailers, and marketplaces can classify catalog descriptions. Dealerships, repair chains, and fleet workshops can categorize service concerns. Manufacturers, parts suppliers, and warranty administrators can categorize claim records. Each team supplies its own approved labels and representative examples.
What data do we need to start?
Start with a spreadsheet of readable descriptions or notes and a column containing the approved category for each row. Choose one task and use examples that reflect future inputs. Parts catalogs, reported symptoms, and claim findings usually need separate labeling rules and models.
Can StayCharted verify whether a part fits a vehicle?
No. Product categorization does not establish fitment. Vehicle compatibility, dimensions, interchange references, and catalog validation must be checked in your existing fitment data and systems.
Can it diagnose a vehicle or approve a warranty claim?
No. It can categorize a reported concern or a claim narrative. A qualified technician determines the diagnosis; your warranty terms, evidence, and authorized reviewers determine coverage and approval.
Can it classify service calls, invoices, and inspection photos?
Transcribe calls and extract text from invoices or scanned documents before using text classification. Labeled inspection photos can support a separate image model for visible conditions. Image classification does not replace functional testing or detect every hidden defect.
Does it integrate with our catalog or workshop system?
Use spreadsheet exports and imports, or build an API integration on a supported plan. StayCharted returns classification results; your integration controls record updates and workflow actions. Native connections to a particular PIM, ERP, DMS, or warranty platform should not be assumed.
How do we know whether a model is useful?
Check held-out results for each category, inspect mistakes, and test representative new records. Set a review policy around the consequences of a wrong category. No automotive accuracy figure is promised here; performance depends on your labels, examples, and incoming records.
Explore the details
Try it on your own examples.
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.