Website integrationScheduled inventory updates with Upstash QStash
A scheduling layer that tells your dealership website when to pull inventory updates and run health checks, so fresh listings do not depend on someone remembering to click refresh.
Most inventory problems on a dealership website are not dramatic. They are quiet: a price that changed this morning still showing yesterday's number, a vehicle that arrived with photos that never appeared online, a feed that stopped importing on Tuesday and nobody noticed until Friday. On the websites we build, Upstash QStash acts as the clock. It triggers scheduled jobs that ask the website to run its inventory update and to perform monitoring checks. QStash does not supply inventory itself. The vehicle data still comes from your configured inventory source, such as a DealerSync import or another provider your dealership already uses. What QStash removes is the reliance on a person remembering to refresh things by hand.
Note: Availability depends on your dealership's provider agreements, account access, and website configuration. Features described here apply to the websites Relevant Dealer builds and are not an endorsement by the provider.
What the scheduler actually does
QStash sends a signed request to a specific endpoint on your website at a defined time or interval. When that request arrives, the website runs a task we have built for it, for example: import the latest inventory file from the configured source, re-check that each listed vehicle still has a price and photos, or confirm that key pages are responding. Because the trigger lives outside the website server, the schedule does not depend on anyone on your team being logged in. QStash offers capabilities such as request signing and retries; which of these are used, and how, is a configuration decision made per site rather than something to assume on every installation.
- Example: time-based triggers for inventory import jobs
- Example: recurring monitoring checks on selected pages or feeds
- Capability: signed requests the website can verify, where configured
- Capability: retry behavior for transient failures, where configured
A Monday morning, as an example
Consider a used-car store that receives trade-ins all weekend. Before scheduled updates, the sales manager emailed the web vendor on Monday to ask why the new arrivals were missing. With a schedule in place, the import job runs on a set cadence agreed during setup, and the website picks up whatever the inventory source has published since the last run. If the source itself has not been updated, the website cannot invent the vehicles. Where a monitoring check has been set up for it, a run that returns nothing new can be one signal worth reviewing, though an unchanged feed is not automatically treated as a problem; quiet days happen.
Monitoring that catches the quiet failures
Scheduled checks are as valuable as scheduled imports. As examples of what can be configured, a check might confirm that the inventory page loads, that the count of vehicles has not dropped to zero unexpectedly, or that an integration endpoint is responding. The specific checks vary by site. When a configured check fails, the result can be routed to an operational alert, for instance through transactional email, so a person looks at it while it is still a small problem. These checks are diagnostic. They point a human toward an issue; they do not repair a broken provider feed on their own.
Boundaries worth knowing
Update frequency depends on your inventory source, its export schedule, and the agreements in place with that provider. A faster trigger does not make a slower feed faster. QStash also does not decide whether a vehicle is sold; if a vehicle remains in the source data, it will typically remain on the website until the source removes it. We configure schedules per site and review them when your inventory process changes.
For website visitors
- Shoppers are more likely to see recent arrivals and current pricing, because updates run on schedule instead of on memory.
- Fewer dead ends on listings with missing photos or details, since checks surface problems sooner.
For your dealership
- Indirect operational benefit: less time spent asking a vendor to refresh inventory by hand.
- Earlier warning when an inventory feed or key page stops behaving as expected.
- A documented, repeatable schedule instead of an informal habit.
Frequently Asked Questions
Explore Other Integrations
Want this working on your dealership website?
We build custom dealership websites with practical integrations like Upstash QStash, configured around your providers and how your customers shop.