Start with vehicle fitment.
JLR Android systems should define vehicle model, platform code, year, original screen, drive side, HUD, harness and installation context before sampling.
Make software scope part of the quote.
Brands often need custom UI, language, OS configuration, launcher behavior and app requirements. Those decisions belong in the RFQ, not after production.
Use documentation to reduce support load.
Product specs, installation notes, software version records and warranty rules help buyers support distributors before the first bulk order arrives.