TruckCheck

What It Is

TruckCheck is a commercial vehicle procurement application focused on UAE trucks, pickups, vans, finance, insurance, and partner-routed buying workflows.

It already combines public browsing, quote capture, partner onboarding, partner access, internal ops routes, used-market ingestion, and listing-enhancement flows inside one codebase. It should not be treated as a simple static marketing site.

Architecture

TruckCheck currently runs as a single Next.js 15 application compiled through OpenNext for Cloudflare Workers. The same repo owns public pages, internal browser routes, server routes, data helpers, importer scripts, Cloudflare migration files, and a legacy Prisma schema that still points at PostgreSQL for part of the importer service.

Runtime Surfaces

The current public and operator surfaces include /, /browse, /vehicles/:slug, /used, /network, /get-quotes, /partner-onboarding, /partner-access, /team-access, /partner, /ops, and the internal /app/* operator shell for offers, pipeline, partners, market, enhancement, revenue, and commercial operations.

The main homepage, staff workspace shell, partner portal shell, and both access routes were visually rebuilt on 2026-04-15 to move the application toward the Topolo product standard while keeping the existing backend contracts intact.

The server surface currently includes quote intake, offers, opportunities, leads, partners, vehicle listing reads and used imports, importer scheduling and worker execution, staff and partner session handling, and listing enhancement endpoints under /api/*.

API Reference

The current contract is curated in the docs platform rather than OpenAPI-backed. The active route families cover quote requests, partner onboarding and partner access, vehicle listing reads, importer control, and listing enhancement.

Auth and Permissions

TruckCheck now supports Topolo-backed staff sign-in through the dedicated Auth service srv_truckcheck. Staff users can enter /team-access through Topolo, the internal /app shell hosts the shared Topolo launcher through a same-origin Auth gateway, and Auth now grants TruckCheck explicitly to the Work To Work organization. TruckCheck still keeps its own signed staff session cookie after the Topolo callback completes, and partner access remains local and env-backed.

Data Ownership

TruckCheck owns vehicle listings, quote requests, offer comparison payloads, partner onboarding records, partner routing metadata, audit events, and enhancement job state. The current persistence model is mixed: some runtime writes already prefer D1, while other flows still depend on generated output artifacts or a legacy PostgreSQL and Prisma importer path.

Deployments

TruckCheck is currently structured as a Cloudflare Worker deployment with D1 and queue bindings defined in wrangler.jsonc. The checked-in source repo still reflects its original external Cloudflare account posture, and the final Topolo-managed hostnames, Auth integration, R2 rollout, CI automation, and release gates remain part of the production-readiness work.

Failure Modes

• generated output/ partner-review artifacts may be absent, so dealer and body-builder verification counts can fall back to zero until crawlers repopulate them
• env-backed demo auth remains in the codepath and is not suitable for a Topolo-managed production rollout
• runtime persistence is split between D1 blob storage and a separate Postgres and Prisma importer design
• Cloudflare resources and deployment automation are not yet standardized onto the final Topolo operating model

Debugging

Start with /systems/topolo-truckcheck, then verify whether the issue is in public browsing, quote intake, partner access, internal ops, importer execution, or enhancement. For build failures, first confirm that the generated output/firecrawl and output/google-maps artifacts exist.

Change Log / Verification

• Added canonical public TruckCheck coverage on 2026-04-15 so the application now has a Topolo system entry, public and internal docs, and a repo-local CloudControl manifest during third-party onboarding
• Hardened the current baseline on 2026-04-15 so install, typecheck, and build are no longer blocked by missing generated partner-review artifacts or live Google Fonts fetches during build
• Refreshed the public homepage, staff workspace shell, partner portal shell, and access pages on 2026-04-15 so local preview now reflects a more modern SaaS product posture without changing the underlying backend flows yet
• Integrated Topolo-backed staff sign-in on 2026-04-16 so TruckCheck staff users can enter through Topolo and use the shared launcher inside /app
• Registered TruckCheck as Auth service srv_truckcheck on 2026-04-16 and granted the Work To Work organization explicit launcher access so the shared Topolo switcher can treat TruckCheck as a real app destination during staging rollout