30/06/22What was the build date on the invoice?
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
30/06/22What was the build date on the invoice?
what was your original order date?I finally got my VIN and the final invoice. Telling me to pay now.$
I scrolled back, looks like it was 11th Jan.what was your original order date?
I only got sent my VIN today, with the invoice dated yesterday 03/07.VINs appear to have been assigned on 28/6 and we have a build date of 30/6. So VIN assignment 2 days before production. Would love to see more build dates.
Officially sent today. The current batch seems to have been assigned 28th as thats when they appeared in account source code. Unless you were checking that you may not have been aware it had been assignedI only got sent my VIN today, with the invoice dated yesterday 03/07.
Ah yes! I did see Hoopys post with some pretty good detective work but it looked like a few 3's amongst many Y's. I do hope I am wrong and we start getting some good news in the next couple of weeks! I didn't realise this journey was going to be filled with so much hoping and guessing!Really good question.
HoopyFrood did spot some M3s in a different area.
Hopefully more to come soon.
I don't think there is any correlation to vin.Are we any closer to understanding if there is substance to the 'isNotMatchedToRa00Vin' theory?
I am wondering if it's correlated to a scheduled future production run. We discounted it before all this because new (at the time) Y orders had it too.I don't think there is any correlation to vin.
Someone (other than me) order a Y now and see what it says.I am wondering if it's correlated to a scheduled future production run. We discounted it before all this because new (at the time) Y orders had it too.
But as it turned out, loads of Ys were in fact built super quickly. So it's possible those orders were assigned to an already scheduled build? Maybe it needs a revisit. If we can find Y orders with 'true', that will give a clue.
Ra00 just stands for:Are we any closer to understanding if there is substance to the 'isNotMatchedToRa00Vin' theory?
Interesting! Especially in relation to what has happened with those Y orders now getting a VIN... HMMMM....I am wondering if it's correlated to a scheduled future production run. We discounted it before all this because new (at the time) Y orders had it too.
But as it turned out, loads of Ys were in fact built super quickly. So it's possible those orders were assigned to an already scheduled build? Maybe it needs a revisit. If we can find Y orders with 'true', that will give a clue.