How VV Garage Integration Works

Source: vv_garage_controller.rb, vv_garage_external_controller.rb

• Adding a customer to VV Garage automatically adds all of that customer's vehicles; deleting a customer clears all VV Garage data from their records
• The external API is protected by a global API key rather than session-based authentication
• Error codes follow a structured pattern: 500/501/502 for general errors, and 401-406 for availability and booking-specific errors
• Vehicle ownership conflicts are detected and reported via specific error codes (402 for vehicle already owned by another customer, 403 for ownership transfer conflicts)

Support scenarios

• "Customer's vehicles didn't appear in VV Garage" → Adding a customer should automatically add all their vehicles. If vehicles are missing, check that they are properly linked to the customer in Workshop. Manually re-triggering the customer add should sync all vehicles.
• "VV Garage returned error 402 or 403" → These are vehicle ownership conflict codes. Error 402 means the vehicle is already registered to another customer in VV Garage. Error 403 indicates an ownership transfer conflict. The ownership needs to be resolved in VV Garage before the vehicle can be linked.
• "All our VV Garage data disappeared after we removed a customer" → Deleting a customer from VV Garage clears ALL associated VV data. This is by design but cannot be easily undone — the customer and vehicles need to be re-added.