Car logos for salary sacrifice and novated leasing platforms

An employee choosing a car through a salary sacrifice or novated lease scheme compares by make first. The chooser, the side-by-side comparison, the employer dashboard, and the quote all need the same badge at a different size. Serve every one from one URL pattern, across every employer portal you run.

See what it saves

meridian.scheme.example/choose/compare

Live CDN output

Compare your shortlist

Employee car scheme · Meridian Health NHS Trust · 36 months, 8,000 miles a year

Pick up to three

	Kia EV3 GT-Line	Tesla Model 3 RWD	Volvo EX30 Single Motor
Net monthly cost	£376	£398	£354
Gross sacrifice	£578	£612	£545
P11D value	£38,995	£39,990	£36,990
WLTP range	375 mi	318 mi	295 mi
Benefit-in-kind	3%	3%	3%
Includes	Insurance, servicing, tyres	Insurance, servicing, tyres	Insurance, servicing, tyres

Lowest net cost: Volvo EX30 Single Motor. The quote PDF uses the same badge as format=png.

GET https://motomarks.io/img/kia?type=badge

An employee's comparison view on a scheme portal. Make chips, column badges, and the PDF reference are live CDN requests from the same slugs at three sizes. Pick up to three makes; the lowest net cost is underlined.

What it changes for a scheme provider

A scheme provider's costs scale with employers onboarded and brands on the panel. Logo work is one of the few that does not have to. Four costs that stop growing, and what each one replaces.

Employer schemes launch on the contract date: Every new employer gets a branded portal with the makes their scheme allows. When the make list is configuration and the badges are URLs, the portal is ready when the contract is signed, not when someone has assembled a logo set for it.; Replaces an asset step in every employer onboarding
EV brands added the week they matter: Salary sacrifice runs on electric cars, and the brands offering them change fast. A make that enters your panel is a slug from the JSON API; it appears in the chooser, the comparison, and the quote without a design ticket.; Replaces a design request per new EV brand
Comparisons employees can read: An employee weighing three cars against their take-home pay needs to tell them apart in a second. A badge above each column does that. The same badge at the same size in every column, because the URL is the same.; Replaces inconsistent imagery in the comparison view
Documents that survive payroll and HR: Quotes go to the employee, the employer, and payroll as PDFs and emails. PNG from the same slug keeps the mark identical across all of them, and a rebrand reaches the template without anyone opening it.; Replaces a template sweep across quote, agreement, and payroll letter

Leaselab: novated leasing, 100 brands, one URL

Leaselab is a novated lease provider: this page is their business. They maintain more than 100 brands across multiple platforms, and the employee car chooser is where every one of them has to be right. This is what their CTO said changed.

Company: Leaselab
Footprint: Multiple platforms
Library: More than 100 automotive brands
Before Motomarks: An extensive operational cost

What the team stopped doing

01
Hours chasing updated brand assets
The asset behind the URL is updated; the URL does not change
02
Resizing logos by hand for each placement
size= and type= are query parameters
03
Applying one change across various systems
Every platform reads the same URL, so one update reaches all of them

“Novated leasing is our business, so the employee car chooser is the product. An employee compares three cars side by side and the badge is how they tell them apart at a glance. We serve those from Motomarks at whatever size the layout needs, and the same slug goes on the quote document. Nothing is stored on our side.”

Adrian Ciaschetti

CTO, Leaselab

Where the badge goes on a scheme platform

From the employee's first click to the payroll letter. Each row is the literal query string that surface sends.

Employee car chooser: A 20px badge on each make chip, so the employee filters by brand before they scroll.; type=badge&size=xs
Side-by-side comparison: A 44px badge above each column with make and model beneath it.; type=badge&size=md
Employer portal and scheme dashboard: The makes on a scheme's panel in the header, and a badge per active agreement in the drivers table.; type=badge&size=sm
Quote, agreement, and payroll letter: PNG for PDF renderers and email clients; same slug, same size scale.; type=badge&size=sm&format=png
Fleet and utilisation reports: A 16px wordmark per row in the employer's monthly report.; type=wordmark&size=xs&aspect=height

What a scheme panel costs to keep by hand

The defaults describe a provider with a thirty-make panel across an employee portal, an employer dashboard, and document templates. Every brand added to the panel and every rebrand lands on each of them. Put in your own numbers and compare with a plan.

Your numbers; change any input. First year = brands × minutes per brand + changes × codebases × hours per change. Each year after drops the one-time build. The model counts engineering time only; it leaves out CDN hosting, storage, and the cost of shipping an out-of-date mark.

Coverage for scheme panels

The EV makes that fill salary sacrifice panels, the newer brands joining them, and the hybrid and petrol options novated leases still carry. Each tile links to the brand's logo page; the browse page has the full index.

EV makes on scheme panels

Newer EV brands joining panels

Hybrid and petrol options for novated leases

Badge, wordmark, and full-logo availability varies by brand.Browse every published brand Request a missing brand

Integration in four steps

Panels as slugs, one badge component, PNG for documents, and one key for every employer portal. The examples use JSON and React; the URLs are the same in any stack.

“The chooser, the comparison, and the quote PDF share one slug. Adding an EV brand is a row, not a project.”

Adrian Ciaschetti

CTO, Leaselab

01
Configure each employer's panel as slugs
An employer scheme allows a set of makes. Store that as slugs from the JSON API. The chooser, the comparison, and the employer dashboard all read this array; adding a brand to the panel is a config change.
schemes/meridian-health.json
```
{
  "employer": "meridian-health",
  "portal": "meridian.scheme.example",
  "term_months": 36,
  "panel": ["tesla", "kia", "hyundai", "bmw", "volvo", "polestar", "byd", "mg", "volkswagen", "skoda", "cupra", "toyota"]
}
```

Render the badge in the chooser and the comparison

One component owns the URL. The chip asks for xs, the comparison column for md. Keep the make name visible so a column reads correctly if a variant is not published for a brand.

components/make-badge.tsx

const SIZE_PX = { xs: 20, sm: 32, md: 44 } as const;

export function MakeBadge({ slug, name, size = "sm" }: { slug: string; name: string; size?: keyof typeof SIZE_PX }) {
  const src = `https://motomarks.io/img/${slug}?type=badge&size=${size}&token=${process.env.NEXT_PUBLIC_MOTOMARKS_KEY}`;
  return <img src={src} alt={`${name} badge`} width={SIZE_PX[size]} height={SIZE_PX[size]} loading="lazy" />;
}

Use PNG in the quote and the payroll letter

PDF renderers and many email clients do not decode WebP. Request format=png for anything that leaves the browser. A fixed width and height keeps the document layout stable.

templates/quote.html

<!-- employee quote, employer confirmation, payroll deduction letter -->
<img
  src="https://motomarks.io/img/{{ make_slug }}?type=badge&size=sm&format=png&token=pk_YOUR_PUBLISHABLE_KEY"
  alt="{{ make_name }}"
  width="32"
  height="32"
/>

04
One key across every employer portal
Employer portals usually live on subdomains of one platform. One publishable key serves all of them; browser requests are attributed by Referer, so usage is visible per employer. On Pro, restrict the key to *.scheme.example.
Usage dashboard
```
Allowed hostnames (Pro)
  *.scheme.example

Usage by domain, last 30 days
  meridian.scheme.example     61,204
  northbank.scheme.example    48,930
  civic.scheme.example        22,117
```

Questions before you integrate

Our portals sit behind employee login. Does the Free plan work there?

Publishable keys work the same behind authentication. On the Free plan the attribution link must be on a publicly reachable page, so it would go on your public marketing site. Startup and Pro remove the requirement, which is the usual fit for a scheme provider with several employer portals.

Employers often want their own branding. Does that affect the logos?

No. Manufacturer badges are the same URL regardless of the portal theme. The employer's own logo is yours to host; the manufacturer marks come from the CDN and stay identical across every portal, which is what you want when a driver moves between employers.

Can we show the badge in a novated lease quote in Australia as well as a UK salary sacrifice quote?

Yes. The URL and the published library are the same worldwide. Coverage includes the makes common to Australian novated lease panels and UK EV salary sacrifice panels; check the browse index for a specific brand and request any that are missing from the submit page.

How do we keep the make list current as EV brands enter the market?

Fetch the brand list from the JSON API with a daily revalidation and intersect it with each employer's panel. New brands, logo updates, and aliases appear in the public changelog, and the URL structure does not change as the library grows.

What does this save a scheme provider?

Startup is $228 a year billed monthly, Pro $588. A provider with twenty employer portals and a panel of thirty makes has six hundred badge placements to keep current from one image set; one EV brand added to the panel by hand touches every portal and every template. Leaselab, running novated leasing across multiple platforms with more than 100 brands, described that as an extensive operational cost. The cost model on this page uses your numbers.

Every employer portal,
every badge, one key.

Create a free key, store each panel as slugs, and the next employer you onboard launches with its badges already in place.

Read the Image CDN docs

Free includes 1,000 requests per day with an attribution link. Startup and Pro remove attribution.

More ways teams use Motomarks

Leasing and finance applications

Teams building lease and loan origination, quoting, captive finance, and portfolio tools

Read the guide

Fleet management and mobility

Fleet leasing companies, fleet management software, and corporate mobility providers

Read the guide

Vehicle make selector

Developers adding a make picker to search, quoting, affordability, history check, or booking flows

Read the guide

Car logos for salary sacrifice and novated leasing platforms

What it changes for a scheme provider

Leaselab: novated leasing, 100 brands, one URL

What the team stopped doing

Where the badge goes on a scheme platform

What a scheme panel costs to keep by hand

Coverage for scheme panels

EV makes on scheme panels

Newer EV brands joining panels

Hybrid and petrol options for novated leases

Integration in four steps

Configure each employer's panel as slugs

Render the badge in the chooser and the comparison

Use PNG in the quote and the payroll letter

One key across every employer portal

Questions before you integrate

Our portals sit behind employee login. Does the Free plan work there?

Employers often want their own branding. Does that affect the logos?

Can we show the badge in a novated lease quote in Australia as well as a UK salary sacrifice quote?

How do we keep the make list current as EV brands enter the market?

What does this save a scheme provider?

Every employer portal,every badge, one key.

More ways teams use Motomarks

Leasing and finance applications

Fleet management and mobility

Vehicle make selector

Every employer portal,
every badge, one key.