Skip to content

Nissan Stickers

Repo: savvydealer-adam/nissan-stickers · Path: C:/Users/adam/nissan-stickers · Owner: Adam Status: Live · % Done: 70 · Last commit: 2026-04-04 Deployed: Cloud Run nissan-stickers (savvydealer-website project)

What it is

Nissan window sticker (Monroney label) PDF cache + daily sync service. Serves the factory window sticker for any Nissan VIN via a simple URL.

Why it exists

Dealer websites and tools need on-demand Monroney PDFs for any Nissan in inventory. Nissan's OEM endpoint is fine but slow and sometimes flaky — cache once, serve instantly forever.

How it works

Python + Flask on Cloud Run. - fetch_stickers.py — initial bulk fetch from a dealer inventory - sync_stickers.py — daily: parse dealer sitemap, diff against cache, fetch missing - app.py — Flask app serving cached PDFs from stickers/ - Primary source: orlandonissan.com (moved from Wesley Chapel Nissan 2026-04-04, with fallback) - Sitemap source: alanjay.com/inventory-sitemap - URL: https://<service-url>/<VIN> returns the PDF - Daily cron at 7 AM ET: parse sitemap → fetch new → redeploy if additions

What's done

  • Cache + daily sync pipeline
  • Primary / fallback sticker source logic
  • Cloud Run deploy + daily cron
  • Flask serve layer

What's next

  • Extend pattern to other OEMs (Ford, Chevy, etc.) — same Monroney need
  • Consider shared blob storage instead of in-container cache (PDFs bloat the image)
  • Monitor source stability across dealers

Where the code lives

  • app.py — Flask service
  • sync_stickers.py — daily sync
  • fetch_stickers.py — bulk backfill
  • stickers/ — cached PDFs (not committed)
  • Dockerfile + Cloud Run deploy

Integrations

  • Consumed by dealer websites (VDP "Window Sticker" button)
  • Pairs with vehicle-features for full VDP enrichment
  • Pattern should generalize to per-OEM sticker services

Don't rebuild this — extend it

For Ford / Chevy / etc., fork this pattern — dealer sitemap source + OEM sticker endpoint + cache — don't re-architect.