Car logos for dealership website platforms

Rooftops launch without an asset step

A new dealer's franchise strip is eight slugs in a config file. The site goes live when the content is ready, not when someone finds the Ram badge at the right size and drops it into the theme.

Replaces an asset checklist for every new rooftop

One fix reaches every dealer site

When a manufacturer refreshes its mark, every rooftop you host picks up the new asset within a day from the same URL. No theme release, no per-site deploy, no dealer left on the old logo.

Replaces a theme release and redeploy per rebrand

Current marks on every rooftop

Manufacturer brand standards reach dealers through the franchise agreement, and the website is the first place a field rep looks. Serving the current mark everywhere removes one thing your dealers can be flagged for.

Replaces brand-standards fixes chased site by site

Tickets that are never raised

"Our Chevrolet logo is the old one" is a support ticket, an asset hunt, and a redeploy. When the badge comes from a maintained URL, the dealer never has a reason to send it.

Replaces brand-asset support tickets from dealers

Inventory filters

A 20px badge beside each make and its count. WebP by default, so a thirty-make filter stays light.

type=badge&size=xs

Franchise strip

The brands a rooftop sells, in the header or footer of every page that rooftop serves.

type=badge&size=sm

Vehicle detail header

The make badge next to year, model, and trim, matched to the listing it came from.

type=badge&size=sm

Brand landing pages

A full logo at the top of /new/toyota, sized for a hero and cached for a day.

type=full&size=lg

Service and parts pages

The makes a service centre works on, without a second image set to maintain.

type=badge&size=sm

1. 01

   Map inventory feed makes to brand slugs

   Your DMS or inventory feed spells makes its own way (MERCEDES-BENZ, Mercedes Benz). Pull the published list from the JSON API on your server once a day and store the id next to each make in your own tables.

   Secret keys stay on the server. The browser only ever sees the publishable key in image URLs.

   const res = await fetch("https://api.motomarks.io/brands", {
     headers: { Authorization: `Bearer ${process.env.MOTOMARKS_SECRET_KEY}` },
   });
   const brands: { id: string; name: string }[] = await res.json();
   
   // "mercedes-benz" <- "Mercedes-Benz"
   const slugByName = new Map(
     brands.map((brand) => [brand.name.toLowerCase(), brand.id]),
   );
   
   await db.makes.upsertMany(
     feedMakes.map((make) => ({
       name: make,
       slug: slugByName.get(make.toLowerCase()) ?? null,
     })),
   );

2. 02

   Render the badge from one template partial

   One partial serves the filter, the result rows, and the detail header. The only thing that changes per placement is the size parameter.

   Keep the make name in alt and in visible text so the interface reads correctly if a variant is not published for a brand.

   <img
     src="https://motomarks.io/img/{{ vehicle.make_slug }}?type=badge&size=xs&token=pk_YOUR_PUBLISHABLE_KEY"
     alt="{{ vehicle.make }}"
     width="20"
     height="20"
     loading="lazy"
   />
   <span>{{ vehicle.make }}</span>

3. 03

   Configure each rooftop's franchise list

   The franchise strip and the make filter read the same array. Adding a rooftop or a new franchise is a config change, not an asset upload into the theme.

   {
     "dealer": "northgate-auto",
     "domain": "northgateauto.example",
     "franchises": [
       "toyota", "honda", "ford", "chevrolet",
       "hyundai", "subaru", "volkswagen", "bmw"
     ]
   }

4. 04

   Let the CDN and the browser cache

   Every image ships with a 24-hour Cache-Control header from an AWS CloudFront-backed CDN. Add loading="lazy" to filter and list badges, and preload only the badge above the fold on a brand landing page.

   On Pro, restrict the publishable key to your dealer domains (*.yourplatform.example) so a copied key cannot be reused elsewhere.

   HTTP/1.1 200 OK
   Content-Type: image/webp
   Cache-Control: public, max-age=86400, immutable

Questions before you integrate