{
  "slug": "what-is-blue-collar-parts",
  "title": "What Blue Collar Parts Is",
  "description": "Blue Collar Parts builds serialized inspection decals and digital service records for commercial trucks, trailers, generators, and marine equipment. What the platform does, who it is for, and what it deliberately does not do.",
  "track": "product",
  "kind": "article",
  "status": "in-development",
  "isRegulatoryAdjacent": false,
  "publishedAt": "2026-09-01",
  "updatedAt": "2026-09-01",
  "cfr": [],
  "related": [
    "how-the-serialized-decal-works",
    "bcp-and-part-396-recordkeeping",
    "what-is-commercial-vehicle-inspection"
  ],
  "url": "https://shopbluecollarparts.com/kb/what-is-blue-collar-parts",
  "markdownUrl": "https://shopbluecollarparts.com/kb/what-is-blue-collar-parts.md",
  "body": "Blue Collar Parts (shopbluecollarparts.com) sells **serialized inspection decals paired with a digital service record**. A technician completes an inspection or service on a piece of equipment, binds a serialized QR decal to that record, and the decal becomes a permanent scannable pointer to what was actually done.\n\nThe problem it addresses is not the inspection. It is what happens to the paperwork afterward.\n\n## The problem\n\nAn annual inspection produces a report. Under [49 CFR 396.21(b)(1)](/kb/dot-inspection-recordkeeping) that report has to survive fourteen months and be produceable on demand by an authorized official. In practice it is a carbon copy in a folder in a shop office, and the obligation to produce it sits with the carrier operating the vehicle — **not** with the shop that performed it, even if that shop has since closed or lost the file.\n\nSo the failure mode is rarely \"the inspection was done wrong.\" It is \"the inspection was done correctly eighteen months ago and nobody can find the paper.\"\n\n## What the platform does\n\nFour things, in order:\n\n1. **Inspection and service entry.** A technician fills out the inspection or service record on a phone, in the field. Defect data is captured per component rather than as a single pass/fail verdict.\n2. **Serialized decal binding.** The technician scans a decal from their own kit. That serial is bound to the record they just completed, one to one.\n3. **A public, scannable record.** Anyone who scans the QR on that decal — a driver, a fleet manager, an official, a prospective buyer — lands on the as-filed record for that specific serial.\n4. **Distribution to the equipment owner.** The record can be published and sent to the customer, so the person who owns the equipment holds a copy independent of the shop.\n\nThe decal is the index. The record is the thing that matters.\n\n## What equipment it covers\n\nTrucks and trailers, where the [federal annual inspection](/kb/annual-dot-inspection-requirements) applies, and generators and marine equipment, where interval-based preventive maintenance applies but no federal inspection regime does. The same serialization and record mechanics serve both; only the form content differs.\n\n## What it deliberately does not do\n\nThis matters as much as the feature list, and it is stated plainly because ambiguity here is a liability:\n\n- **It does not make a regulatory determination.** The platform can record that a component was measured and what the measurement was. It does not certify that a vehicle is compliant. A [qualified inspector under 49 CFR 396.19](/kb/who-can-perform-dot-inspection) makes that determination; the platform records it.\n- **It does not replace the inspection report.** A decal under [49 CFR 396.17(c)(2)](/kb/dot-inspection-decal-requirements) is documentation *based on* a report. The report still has to exist and still has to be retained.\n- **It does not verify inspector qualification.** Qualification evidence under §396.19(b) and §396.25(e) is the carrier's recordkeeping obligation.\n- **No machine output publishes a record.** Where the platform uses automated processing to assist a technician, the output is held beside the technician's own input for human review. Nothing is published, and no regulatory conclusion is reached, without a person approving it.\n\n## Availability\n\nThe platform is in active development. Pages in this section carry a status marker: **in development** means the behavior described is built and specified but not yet generally available. Nothing here should be read as a claim that a feature is live in production today.\n\n---\n\n*Product behavior described here is subject to change. Regulatory content is informational only and is not legal advice — see [49 CFR Part 396](https://www.ecfr.gov/current/title-49/part-396).*",
  "license": "CC BY 4.0",
  "licenseUrl": "https://creativecommons.org/licenses/by/4.0/"
}