Docs / System Flow (Sandbox)

myodo Complete System Flow

Status: SANDBOX DOCUMENT - Work in Progress
Purpose: Comprehensive explanation of end-to-end product flows
Last Updated: January 2026

This document explains every step of how data moves through the myodo ecosystem - from the moment a repair order is created to the moment a customer books their next appointment. Every touchpoint, every handoff, every notification.

Table of Contents

  1. System Overview
  2. Service Record Upload Flow
  3. Device Telemetry Flow
  4. Vehicle Profile & Linking
  5. Service Notification Flow
  6. Scheduling System Flow
  7. Shop-Consumer Messaging Flow
  8. Data Privacy & Consent Flow
  9. Complete User Journey (End-to-End)

1. System Overview

The Core Concept

myodo acts as an intelligent broker between three parties:

The system's job is to create and maintain connections between these parties, facilitate communication, and ensure the right information reaches the right person at the right time.

The Universal Key: VIN

Everything in myodo revolves around the Vehicle Identification Number (VIN). The VIN is a 17-character unique identifier assigned to every vehicle manufactured since 1981. It never changes for the life of the vehicle.

The VIN connects:

When any piece of data enters the myodo system, the first question is always: "What VIN does this belong to?"

Data Sources

Data enters myodo from three sources:

SourceData TypeHow It Enters
myodo DeviceMileage, engine data, trip infoAutomatic cellular transmission
Shop DashboardService records, repair ordersManual upload by shop staff
Consumer AppHistorical records, preferencesPhoto upload, manual entry

2. Service Record Upload Flow

Step 1: Service Is Performed

A vehicle owner brings their car to a repair shop. The shop performs work - could be an oil change, brake replacement, tire rotation, major repair, or any combination of services. At the end of the visit, the shop generates a repair order (also called an invoice or work order).

This repair order contains:

Step 2: Shop Uploads the Repair Order

The shop employee accesses the myodo Shop Dashboard and uploads the repair order. This can happen in several ways:

Method A: PDF Upload (Most Common)

  1. Shop exports repair order as PDF from their shop management system (ShopGenie, Tekmetric, Mitchell, etc.)
  2. Shop employee drags and drops the PDF into the myodo dashboard
  3. myodo receives the file and queues it for processing

Method B: Photo Upload

  1. Shop employee takes a photo of the printed repair order
  2. Photo is uploaded via the dashboard or mobile app
  3. myodo receives the image and queues it for processing

Method C: Direct Integration (Future)

  1. Shop management system has API integration with myodo
  2. When repair order is finalized, it automatically syncs to myodo
  3. No manual upload required

Step 3: AI Document Processing

When myodo receives a repair order (PDF or image), the AI processing pipeline activates:

3a. Document Intake

3b. Text Extraction

3c. VIN Detection

3d. Data Extraction

The AI extracts structured data from the unstructured document:

3e. Data Normalization

Different shops describe the same service in different ways. The AI normalizes this:

3f. Confidence Scoring

Step 4: Record Storage

Once processed, the service record is stored in the myodo database:

Step 5: Relationship Linking

After storage, the system checks for and creates relationships:

5a. Vehicle-Shop Link

5b. Vehicle-Owner Link (If Device Exists)

5c. Consumer Notification (If Linked)

3. Device Telemetry Flow

Step 1: Device Installation

The vehicle owner (or a shop employee) installs the myodo device:

  1. Locate the OBD-II port (under the dashboard, driver's side, near the steering column)
  2. Plug the myodo device into the port
  3. The device powers on automatically (draws power from the vehicle's 12V system)
  4. LED indicator shows status (blinking = connecting, solid = connected)

Step 2: Device Registration

The device must be registered to a vehicle owner's account:

  1. Vehicle owner opens the myodo app
  2. Selects "Add Device"
  3. Scans the QR code on the device (or manually enters the device serial number)
  4. The app sends a registration request to the myodo backend
  5. The backend associates the device serial number with the user's account

Step 3: VIN Auto-Detection

Once plugged in, the device reads the vehicle's VIN:

  1. Device sends a request over the OBD-II protocol asking for the VIN
  2. The vehicle's onboard computer responds with the 17-character VIN
  3. Device transmits the VIN to myodo servers
  4. The VIN is validated and associated with the device and user account
  5. The vehicle's make, model, year, and engine are decoded from the VIN
  6. Manufacturer maintenance schedules for this specific vehicle are loaded

Step 4: Continuous Data Collection

While the device is installed, it continuously collects data:

When the Vehicle is Running:

Data Packet Contents:

When the Vehicle is Parked:

Step 5: Data Transmission

The device sends data to myodo servers via cellular connection:

  1. Device has a built-in cellular modem with pre-installed SIM card
  2. Connects to available cellular network (multi-carrier, chooses strongest signal)
  3. Data is encrypted before transmission
  4. Transmitted to myodo ingestion servers
  5. Server acknowledges receipt
  6. If transmission fails, data is buffered on-device (up to 7 days of storage)

Step 6: Server-Side Processing

When data arrives at myodo servers:

6a. Authentication

6b. GPS Processing (Privacy-Critical)

6c. Odometer Update

6d. Service Interval Calculation

6e. Alert Generation

4. Vehicle Profile & Linking

The Vehicle Profile

Every vehicle in myodo has a profile, which is the central record that connects everything:

How Linking Works

Scenario A: Device First, Then Service

  1. Consumer buys myodo device and installs it
  2. Device registers VIN to consumer's account
  3. Vehicle profile is created (or existing orphan profile is claimed)
  4. Consumer takes car to a shop for service
  5. Shop uploads repair order
  6. myodo detects: "This VIN has a registered owner"
  7. Service record is automatically linked to consumer's account
  8. Consumer sees record in their app immediately
  9. Shop is now linked as a service provider for this vehicle

Scenario B: Service First, Then Device

  1. Consumer takes car to a myodo-connected shop
  2. Shop uploads repair order
  3. myodo creates a vehicle profile for this VIN (orphan profile - no owner)
  4. Service record is stored, linked to vehicle profile
  5. Later, consumer buys and installs myodo device
  6. Device reads VIN during registration
  7. myodo detects: "This VIN already has service history"
  8. Existing vehicle profile is linked to consumer's account
  9. All previous service records now appear in consumer's app
  10. Consumer "inherits" the service history

Scenario C: Consumer Uploads Historical Records

  1. Consumer has myodo device installed
  2. Consumer has old service records (paper, email, photos)
  3. Consumer uploads these via the myodo app
  4. AI processes and extracts data
  5. VIN is matched to consumer's vehicle
  6. Historical records are added to the vehicle's service history
  7. Service intervals are recalculated based on complete history

The Shop-Consumer Connection

When a shop services a vehicle with a myodo device, a relationship is created:

5. Service Notification Flow

Trigger: Service Approaching

The notification system constantly monitors all vehicles with active devices:

  1. Every time new mileage data arrives, service intervals are recalculated
  2. If a service item crosses the notification threshold, an alert is triggered
  3. Default threshold: 500 miles before service is due
  4. Consumer can customize thresholds (250 miles, 1000 miles, etc.)

Notification Content Generation

When a notification is triggered, the system generates the message:

Information Gathered:

Message Constructed:

"Your [Vehicle Year Make Model] is due for an oil change in about 500 miles. Schedule with Joe's Auto Repair?"

Notification Delivery

Push Notification (Primary)

  1. Message is sent to Apple Push Notification Service (iOS) or Firebase Cloud Messaging (Android)
  2. Consumer's phone receives the notification
  3. Notification appears on lock screen and in notification center
  4. Tapping the notification opens the myodo app to the scheduling screen

Email Notification (Secondary)

  1. If consumer has email notifications enabled:
  2. Email is generated with service details
  3. Includes "Schedule Now" button linking to the app
  4. Sent via email delivery service

SMS Notification (Optional)

  1. If consumer has SMS notifications enabled:
  2. Short message is generated
  3. Sent via SMS gateway
  4. Includes link to schedule

Notification Frequency Controls

To prevent notification fatigue:

6. Scheduling System Flow

Consumer Initiates Scheduling

From the notification or from the app, the consumer decides to schedule:

  1. Consumer taps "Schedule" button
  2. App opens scheduling interface
  3. Default shop is pre-selected (most recent service provider)
  4. Consumer can change shop if desired

Shop Availability (Pro Shops)

If the shop has a Pro subscription with calendar integration:

  1. myodo queries the shop's calendar for available slots
  2. Available times are displayed to the consumer
  3. Consumer selects a date and time
  4. Selected slot is temporarily held (5 minutes to complete booking)

Shop Availability (Free Shops)

If the shop is on the free tier (no calendar integration):

  1. Consumer sees shop's business hours
  2. Consumer selects a preferred date/time
  3. Request is sent to shop as a "requested time" (not guaranteed)
  4. Shop will confirm or suggest alternatives

Appointment Request Submission

Consumer submits the scheduling request:

Data Included in Request:

Shop Receives Request

The shop is notified of the incoming appointment request:

  1. Push notification to shop dashboard: "New appointment request"
  2. Email notification to shop's designated email
  3. Request appears in shop's dashboard queue

Shop Confirms or Modifies

Option A: Confirm as Requested

  1. Shop clicks "Confirm"
  2. Appointment is locked in
  3. Consumer receives confirmation notification
  4. Appointment appears on both calendars

Option B: Suggest Different Time

  1. Shop clicks "Suggest Alternative"
  2. Shop selects available times to offer
  3. Consumer receives notification with options
  4. Consumer selects from alternatives or requests different times
  5. Process repeats until agreement is reached

Option C: Decline

  1. Shop declines the request (too busy, don't offer that service, etc.)
  2. Consumer is notified
  3. Consumer can request from a different shop

Appointment Confirmation

Once confirmed, both parties receive:

Consumer Receives:

Shop Receives:

Appointment Reminders

As the appointment approaches:

7. Shop-Consumer Messaging Flow

myodo as Message Broker

All communication between shops and consumers flows through myodo. This provides:

Message Types

Type 1: Service Updates

Shop sends updates about in-progress service:

Type 2: Quotes and Estimates

Shop sends pricing information:

Type 3: Photos and Documentation

Shop shares visual information:

Type 4: General Communication

Free-form messaging:

Message Flow (Shop to Consumer)

  1. Shop composes message in dashboard
  2. Shop attaches photos/documents if applicable
  3. Shop clicks "Send"
  4. Message is stored in myodo database
  5. Consumer notification is triggered
  6. Consumer's phone shows push notification
  7. Consumer opens app to view full message
  8. Read receipt is recorded
  9. Consumer can reply

Message Flow (Consumer to Shop)

  1. Consumer opens conversation in app
  2. Consumer types message or attaches photo
  3. Consumer sends
  4. Message is stored in myodo database
  5. Shop notification is triggered
  6. Shop sees notification in dashboard
  7. Shop views and responds

Privacy Controls in Messaging

8. Data Privacy & Consent Flow

Consumer Data Ownership

Fundamental principle: The consumer owns their data.

Consent Levels

Level 1: Account Creation

Consumer agrees to:

Level 2: Device Registration

Consumer agrees to:

Level 3: Shop Connection

When a shop services their vehicle, consumer is notified:

Level 4: Data Sharing (Per-Request)

When consumer schedules with a new shop:

Data Deletion Rights

Delete Specific Records

Consumer can delete individual service records:

Delete Account

Consumer can delete their entire account:

Shop Data Access

Shops have limited data access by design:

9. Complete User Journey (End-to-End)

Let's follow a complete journey from device purchase to return visit:

Day 1: Device Purchase and Installation

  1. Sarah buys a myodo device ($150) from the myodo website
  2. Device ships within 2 days
  3. Sarah receives device, downloads myodo app
  4. Sarah creates account (email, password)
  5. Sarah plugs device into her 2019 Honda Accord
  6. Device reads VIN: 1HGCV1F34KA123456
  7. App confirms: "2019 Honda Accord EX detected"
  8. Device is now transmitting mileage data

Day 5: Historical Records Upload

  1. Sarah finds old service receipts in her glovebox
  2. Opens myodo app, taps "Add Service Record"
  3. Takes photos of 3 old receipts
  4. AI processes and extracts: Oil change (15,000 mi), Tire rotation (18,000 mi), Oil change (21,000 mi)
  5. Records appear in her service history
  6. App calculates: "Next oil change due at 26,000 miles"

Day 30: Shop Visit

  1. Sarah takes car to Joe's Auto Repair for a check engine light
  2. Joe diagnoses: Loose gas cap (no repair needed)
  3. Joe uploads the repair order to myodo Shop Dashboard
  4. myodo links the record to Sarah's vehicle (VIN match)
  5. Sarah receives notification: "New service record from Joe's Auto Repair"
  6. Record appears in her app: "Check Engine Diagnosis - $45"
  7. Joe's Auto Repair is now linked as a service provider

Day 90: Service Notification

  1. Sarah has driven 4,500 miles since her last oil change
  2. Oil change interval for her vehicle: 5,000 miles
  3. myodo triggers notification (500 miles before due)
  4. Sarah's phone buzzes: "Your Honda Accord is due for an oil change in about 500 miles. Schedule with Joe's Auto Repair?"

Day 90: Scheduling

  1. Sarah taps the notification
  2. myodo app opens to scheduling screen
  3. Joe's Auto Repair is pre-selected
  4. Sarah sees available times (Joe has Pro subscription)
  5. Sarah selects: "Thursday 10:00 AM"
  6. Sarah taps "Request Appointment"
  7. Request is sent to Joe's dashboard

Day 90: Shop Confirmation

  1. Joe receives notification: "New appointment request"
  2. Joe sees: Sarah M., 2019 Honda Accord, Oil Change, Thursday 10 AM
  3. Joe sees Sarah's history at his shop: "Check Engine Diagnosis - 2 months ago"
  4. Joe clicks "Confirm"
  5. Sarah receives: "Appointment confirmed! Thursday 10:00 AM at Joe's Auto Repair"

Day 93: Appointment Reminder

  1. Wednesday evening: Sarah receives push notification
  2. "Reminder: Oil change tomorrow at 10:00 AM at Joe's Auto Repair"
  3. Sarah adds to phone calendar

Day 94: Service Visit

  1. Sarah arrives at Joe's at 10 AM
  2. Joe already has her info pulled up from myodo
  3. Joe performs oil change
  4. Joe notices: "Brakes are getting worn, recommend replacing in 10,000 miles"
  5. Joe completes service, generates repair order
  6. Joe uploads to myodo: "Oil Change - $65, Note: Brake pads wearing"

Day 94: Post-Service

  1. Sarah receives notification: "Service record updated: Oil Change at Joe's Auto Repair"
  2. Record appears in app with full details
  3. myodo updates next service: "Oil change due at 31,500 miles"
  4. myodo notes: "Brake pad replacement recommended around 36,000 miles"
  5. Sarah's service history is complete and up to date

Day 180: Next Cycle Begins

  1. Sarah approaches 31,000 miles
  2. myodo sends notification: "Oil change due in 500 miles"
  3. Sarah schedules with Joe again
  4. The cycle continues

Summary: The myodo Value Loop

The complete system creates a virtuous cycle:

  1. Device tracks mileage → Enables accurate service predictions
  2. Accurate predictions → Consumer trusts notifications
  3. Consumer trusts notifications → Consumer schedules service
  4. Consumer schedules service → Shop retains customer
  5. Shop retains customer → Shop uploads records
  6. Shop uploads records → Better service history
  7. Better service history → More accurate predictions
  8. Repeat

myodo sits at the center of this loop, facilitating every connection while ensuring the consumer maintains control of their data and relationships.

myodo - Your car. Your records. Your choice.

Investor Elevator Pitch

What We Do: myodo is the intelligence layer between vehicles and repair shops. We broker the relationship - tracking real mileage, storing service history, and connecting drivers to shops at exactly the right moment.

How It Works: A small device plugs into your car and reports mileage to our system. We combine that with service records from shops. When maintenance is actually due, we notify the driver and route them back to their shop. One tap to schedule.

Why We Win: We sit in the middle. Drivers get accurate reminders and a complete service history. Shops get customers who come back. We're the broker that makes both sides better off.

The Business: $150 device, $15/month for drivers. Free dashboard for shops, $100/month Pro tier. $25/month for fleets. Same device, same backend, three revenue streams.

The Ask: $500K on a $5M cap. 12-month runway to 300 devices, 20 shops, $65K ARR.

Document Status: SANDBOX - Work in Progress