How Oscar Parts Ordering Works

Source: oscar_controller.rb

• Build year parsing uses the same 3-format handler as tire registrations, supporting multiple date input formats
• The access code is configured globally, with per-company identification via site_code
• Products are auto-created if a matching product does not exist; new products always use the retail price from the Oscar order
• Parts with the part number "LAB" are treated as labor product types, following the same convention as Bursons

Support scenarios

• "Oscar order created a product with the wrong price" → New products always use the retail price from the Oscar order. If the workshop expected a different price, they need to update the product record after creation.
• "Build year isn't matching correctly on Oscar orders" → Build year parsing supports three date formats. If the vehicle's build year is in an unexpected format, it may not parse correctly. Check and standardize the build year on the vehicle record.
• "Labor item from Oscar came through as a part" → Only items with part number "LAB" are recognized as labor. If Oscar used a different identifier, the item will be created as a regular part.