Selling 2022 VIN's in 2023?

[Wilson44]

I confirmed an LE R1S in the shop last night with an 013## VIN! when was that built? Very early 2022?

Looks like the news ones are at least up to 18### now. I have OPs concerns but further magnified.

Sponsored

 

[Ralph]

That’s just crazy! How are they rematching you to the same vehicle.

I was unmatched from a low VIN LE in May and then given shop access where I picked up another LE R1S with a more recent VIN. Though it wasn’t the latest during that time, it was still better than the first one.

It seems to me that at least some, if not all initial matches of vehicle to customer configuration are now being done by software. The glitch may be that the system does not have a provision for "customer rejection".

So the workflow might go something like this:

The OP config is matched to a now available vehicle. He gets it unassigned due to the fact that it is a 2022 and it's mid 2023. Subsequently, the software matching program runs again, probably during an overnight, unattended process. The program finds a VIN/spec that matches a customer that wants that spec. So it assigns that VIN to that customer - again. Customer and guide are assigned/informed (again) and off we go through another cycle.

Perhaps a refinement needs to be made to the matching program allow guides to add a customer ID and VIN indicating that customer has rejected that VIN - "do not match this customer with this VIN". Or if already in place, do some more training.

It seems far more likely that something like this happened rather than think Rivian are such bold (and stupid) con artists that they are intentionally trying to slip the same VIN past a customer that already rejected that VIN as a problem - two more times.

 

[Dark-Fx]

I confirmed an LE R1S in the shop last night with an 013## VIN! when was that built? Very early 2022?

Looks like the news ones are at least up to 18### now. I have OPs concerns but further magnified.

Is it a 23? Rivian reset the VIN counter for a brief period when the model year change happened, but they realized it caused issues with their servicing system and then switched back to a completely sequential serial. Guessing it was built in Dec22.

If it is a 22, then build date is probably June 22 or so.

 

[shandel]

Yeah, not really seeing how they were attempting to make good on it for me. They assured me on two separate occasions that it was a “glitch” and wouldn’t happen again…and then it did. Now, I’m being told it is going to take a few business days just to unmatch me from the VIN.

Frankly, I would have just taken the 2022 if they were having such a hard time, but I would have expected some type of discount being that the vehicle is a year old, but they flat out refused.

Making good on it would have been to offer a discount, being that it was an older vehicle, not asking me to pick a different color so that they would stop running into the very issue that they created. That, coupled with the refusal to simply speak on the phone, is what I find the most disturbing.

If I choose to cancel, it isn’t me trying to “show them”, as I know at the end of the day whatever choice I make will have no impact whatsoever on Rivian. If I were to cancel, it would simply be because as a consumer, I have lost confidence in a brand and their ability to provide effective customer service.

Honestly, it sounds like a computer issue that it keeps matching you. The guides probably have very little control over that. I'd keep working with the guides and just wait to get the vehicle you want.

 

[Amerocks]

It seems to me that at least some, if not all initial matches of vehicle to customer configuration are now being done by software. The glitch may be that the system does not have a provision for "customer rejection".

So the workflow might go something like this:

The OP config is matched to a now available vehicle. He gets it unassigned due to the fact that it is a 2022 and it's mid 2023. Subsequently, the software matching program runs again, probably during an overnight, unattended process. The program finds a VIN/spec that matches a customer that wants that spec. So it assigns that VIN to that customer - again. Customer and guide are assigned/informed (again) and off we go through another cycle.

Perhaps a refinement needs to be made to the matching program allow guides to add a customer ID and VIN indicating that customer has rejected that VIN - "do not match this customer with this VIN". Or if already in place, do some more training.

It seems far more likely that something like this happened rather than think Rivian are such bold (and stupid) con artists that they are intentionally trying to slip the same VIN past a customer that already rejected that VIN as a problem - two more times.

I agree, I think it was more of a software issue than anything else, though I was reassured on multiple occasions that the problem was resolved, when it actually wasn't. That's where my concerns popped up, along with the fact that I wish they would have been upfront about the vehicle being a 2022 right from the get go. I just stumbled upon the build year when I was finalizing the insurance and honestly, would have missed it otherwise.

As an update, I ended up getting on the phone with my guide, who told me that my build was available at the Brooklyn SC and when I asked if it was a 2022, she said yes, immediately realizing that the same vehicle was again popping up. Long story short, she worked pretty hard and was able to secure a build newly off the line from the factory. Going through the final steps now and should be picking it up next week, as the vehicle just arrived from transit.

There's clearly some bugs to work out, which is expected from a relatively new company. The most important lesson I learned through the whole process is to just get on the phone with someone, as you're able to make some actual progress, as most of the guides seem pretty motivated to figure out a solution.

To anyone getting matched to older VIN's, if you have any concerns, just talk to the guides, they'll rectify it. Just be insistent that you want to "speak" with someone, not text, as a lot gets lost in translation.

 

[Wilson44]

Is it a 23? Rivian reset the VIN counter for a brief period when the model year change happened, but they realized it caused issues with their servicing system and then switched back to a completely sequential serial. Guessing it was built in Dec22.

If it is a 22, then build date is probably June 22 or so.

I don't know how to tell for sure but NHTSA VIN decoder says 2022. Am I correct to interpret 013## as one of the first 1500 R1S built?

 

[Dark-Fx]

I don't know how to tell for sure but NHTSA VIN decoder says 2022. Am I correct to interpret 013## as one of the first 1500 R1S built?

Yes. Rivian won't tell you why it hasn't been sold yet. It could be that it had to be pulled off the line for a quality issue and they are just now getting around to fixing it. Honestly I would not be that concerned about it being an older VIN unless you are worried about the depreciation hit from being already a model year old.

Your VIN has either an N or a P at Position 10 which indicates what year it was built. N = 2022, P = 2023.

 

[Redline]

I confirmed an LE R1S in the shop last night with an 013## VIN! when was that built? Very early 2022?

Looks like the news ones are at least up to 18### now. I have OPs concerns but further magnified.

It's a 2023.

The 8800 vin they gave me was an April build, and its never left the factory...I've asked them to remove it. CS said they would, but they need my guide to do it. I'm waiting on him now.

 

[CalebSchiff]

For what it's worth, I almost pulled the trigger on a Launch R1T in the shop but the guide confirmed today it'd be a 2022.

 

[Redline]

Now my guide is telling me he can remove the 8800 vin from my account, but I can't get shop access back and he wouldn't have a timeline when my original order would get filled.....

It's really only 5 months old, and never left the factory, so he's sort of making me feel like I should just take it.

When did they switch away from Meridian again?

 

[Wilson44]

Yes. Rivian won't tell you why it hasn't been sold yet. It could be that it had to be pulled off the line for a quality issue and they are just now getting around to fixing it. Honestly I would not be that concerned about it being an older VIN unless you are worried about the depreciation hit from being already a model year old.

Your VIN has either an N or a P at Position 10 which indicates what year it was built. N = 2022, P = 2023.

Thanks! ...NN0013## so it's a 2022 build in the 1300s.

That would have meridian audio, 12v in the frunk, and any other differences?

 

[NY_Rob]

You know it's now 2024 Model year for motor vehicles.. so that brand new 2022 Rivian is instantly 2 years old the second you take delivery.

Ask for a price accommodation because if no one bites at full price they will have to discount it eventually or use it as a SC loaner vehicle.

 

[Vik]

Just saw this thread. I need to pay more attention to the ordering forums!

I was recently given R1 Shop Access and selected a Launch Edition R1S. I received the VIN and it is extremely low (NN0013XX) and a 2022 model year. Why are they offering 2022 models when it is nearing the end of 2023? My guide is removing the car from my account, but who knows what will happen to my place in line and shop access.

 

[DonkeyKong]

Same issue here. 2022 LE reserved from the shop not knowing it was a 2022. However, my guide will not remove it. He said it is already in its way to Florida and I would lose my $1,000.

 

[Guy]

Thanks! ...NN0013## so it's a 2022 build in the 1300s.

That would have meridian audio, 12v in the frunk, and any other differences?

They made changes earlier this year to the front suspension casting (less welds) and also the air compressor was changed.

Sponsored