03 / Automotive commerce & services
Partigo.Find it. Fix it. Drive it.
Parts discovery, workshop booking and service tracking, connected through the customer's vehicle.
Development preview
Vehicle-first automotive platform
Partigo brings the fragmented automotive journey into one product: a saved garage, compatible parts, supplier offers and a clear path from workshop discovery to approved work and service history. Behind the customer app, provider tools connect fulfillment, workshop operations and customer relationships.
The problem
Buying a part and arranging a repair often means repeating vehicle details, comparing disconnected offers and chasing updates. The product needs to keep the vehicle, the customer's decisions and the transaction history connected.
The product approach
A shared vehicle context drives discovery and compatibility, while parts orders and service bookings retain their own vehicle and financial records. Customers can review costs and approve work; suppliers and workshops have operational tools for what happens next.
From the right part to the next service.
A garage that guides discovery
Save vehicles and select the car you are working on. Its make, model and vehicle details carry into parts discovery, compatibility and service browsing.
Parts, fitment and supplier offers
Search by part name, category and OEM reference. Review available fitment information, supplier offers and stock before adding a part to the cart.
Checkout with clearer decisions
Review backend-calculated totals before confirming. Price changes require a refreshed preview, and recoverable checkout drafts preserve the customer's request across retries.
Workshop discovery and booking
Explore maintenance, repair, bodywork and upgrade services. Review workshop offerings, select a service slot and keep the booking attached to the right vehicle.
Itemized quotation approval
Review proposed parts and labor line by line. Approve or reject individual items, retain accepted decisions and follow the agreed scope of work.
Orders, progress and service history
Return to parts orders and service bookings, follow status updates and reopen the vehicle's service history. A different browsing vehicle does not change an existing booking.
Two customer journeys. One vehicle context.
Buy a part
- Select vehicle
- Find a compatible part
- Review offer & total
- Place order & follow fulfillment
Arrange a service
- Choose service & workshop
- Book a slot
- Review inspection & quotation
- Follow approved work & handover
Real screens. A connected experience.
Actual app captures from the September 2026 development review, using sample data and test fonts. Names, prices, ratings and counts shown are demonstration content, not live availability or customer results.
Vehicle-aware home
A selected vehicle connects parts and service entry points.
Saved vehicle garage
Switch the browsing vehicle without changing existing transactions.
Part details & fitment
Review OEM references, specifications and vehicle compatibility.
Service discovery
Discover maintenance, repair, bodywork and upgrades.
Quotation decisions
Itemized decisions preserve the customer's approved scope.
Service progress
Follow the service journey from booking through handover.
An operating layer for automotive businesses.
The platform also includes supplier and workshop workflows. Provider CRM capabilities depend on the assigned plan, licensed branches and user permissions.
Supplier fulfillment
Branch inventory, order acceptance, preparation and courier handover connect the parts purchase to operational tasks.
Workshop operations
Booking, inspection evidence, quotations, approved scope and work-order stages support a traceable service journey.
Provider CRM
Provider-scoped customer and vehicle records, leads, interactions and next-service follow-up keep business relationships organized.
Walk-in and phone jobs
Provider-originated work uses the booking workflow while retaining its source, separate from marketplace acquisition.
Consent-aware communications
Fixed reminder templates and channel/purpose consent controls are implemented. Sending requires project-specific configuration and is disabled by default.
Accounting handoff
Fiscal document drafts, structured exports and a Qoyod connector support accounting handoff. These are not a claim of native ZATCA certification or verified production issuance.
Mobile experience. Operational depth.
The codebase separates customer, supplier and workshop responsibilities, with tenant/customer-scoped APIs, persistent customer drafts and backend authority for checkout and workflow decisions.
- Flutter & Dart
- Provider state management
- NestJS & TypeScript APIs
- Prisma & PostgreSQL
- Secure session storage
- English & Arabic interfaces
Available for a guided product demonstration.
Partigo is in private development and acceptance testing. The current evidence does not establish a public app-store release, production payment activation or a completed live customer/provider pilot. Payment, messaging, logistics and accounting integrations require configuration and rollout validation.