Hey y’all, I built a new application over the weekend - WaitingForJeep.com. With the new '23 Model Year 4XE builds on the way, I figured I’d avoid the headache of checking the Jeep website and the other tracker site obsessively. Instead, let the beautiful world of automation handle all of that for me.
This is just the first iteration of the web app. Here’s what you can currently do:
Enter your Vehicle Order Number (VON) & Last Name on the site to track:
– your current status along with the build codes
– window sticker
– build sheet
– option codes
Using the link generated above, you can now directly open it to view your order status anytime. It follows the format: https://waitingforjeep.com/orderstatus/?orderNumber=8DigitOrderNumber&lastName=YourLastName
In the backend, I have built all that is needed to:
track the order status at a regular interval (currently set at 1hr)
trigger off events as order status changes, including VIN assignment
Here’s what else I have planned for it:
Create some email templates for the email alerts
Set up an outgoing email alert system
Set up an account portal for users to add orders they want to track
For Brokers - have the ability to track bulk orders & notify their customers and themselves of changes to the status of the orders.
Here’s a screenshot of what my order looks like on this site:
Also, small suggestion. I put my VON for my TRX order and it was able to populate… it was not able to for my Hellcat as it requires 8 “digits” and the Hellcat VON has letters so if you are able to remove that digit requirement then I think this tool would become universally compatible with all CDJR orders.
I noticed my GC 4xe order is showing as a 23. Is this an assumption or something you’re pulling from the jeep site? I was under the assumption it would be a 22. Happy to Pm you the von if it helps. Again great work
Thank you everyone for always being so supportive of these projects! I don’t want to spam y’all with individual thank you’s - please take the post love as an alternative
lol, it really was. Started working on it Friday evening
made some changes to change the type to string & remove those validations. Text input keyboard view on mobile should populate the regular keyboard now too. I did leave in the 8-character limitation though - let me know if you need that changed and if it works for your Hellcat, @GOAT !
@harrydogyo - The vehicle data is pulled directly from the main source. You probably have a 2023 being built. Check what your VIN decodes to @ NHTSA - Welcome to VIN Decoding :: provided by vPIC (enter only your vin in this form)
@Kellstar - I appreciate the call out for ScanThatCar! I am running into some issues pulling those history reports, so if it doesn’t populate right away, trying again later could potentially work. But License Plate & VIN Decoding will always work
I appreciate it! The WaitingForTesla post got moved to here, so I figured I’d just start here.
Built on Gatsby (React) paired with MUI / Material UI. The entire backend is powered with Firebase & Google Cloud — nosql database, serverless functions, messaging queues & authentication (coming soon).
Order Numbers with Alphanumeric characters, like Hellcats, can now be searched. I forgot to remove an extra validation on the API. (cc: @GOAT, @Nypharm )
As for some orders coming back as 2023 vs 2022 (on your VIN), that’s just Jeep sending it back as such. No clue as to why. The 10th character on your VIN denotes the model year (N = 2022, P = 2023).
