Archive note, November 2025: This post is based on BDC.aztexsystems template-builder documentation and field inventory notes.
Automotive email campaigns look simple from the outside.
A vehicle photo. A price. A button. Maybe a logo and a disclaimer. Send it to customers and move on.
Inside the workflow, it is messier.
There are single-vehicle offers, multi-vehicle inventory campaigns, holiday promotions, service offers, re-engagement emails, legal disclaimers, tracking links, logos, phone numbers, footer images, colors, background images, and email-client quirks.
The BDC template builder existed because that chaos needed a controlled surface.
Three Campaign Shapes
The system settled around several practical template types.
The single-vehicle template was for a focused offer: one vehicle, one image, pricing, finance language, a call to action, and a disclaimer.
The multi-vehicle template was for inventory showcases. It supported up to eight vehicles in a grid, each with a description, image, link, list price, and sale price.
The promotional templates handled non-vehicle campaigns: events, holidays, announcements, service specials, and hero-image campaigns where the creative already existed as a designed graphic.
Those distinctions mattered because one generic template would have been worse for everyone. The user needs the fields that match the campaign, not a blank HTML editor disguised as flexibility.
Eighty-Eight Fields Is Not Overengineering
The field inventory documented 88 production fields across the builder.
That number sounds absurd until the workflow is broken down:
- Single-vehicle campaign fields.
- Eight vehicles times five fields each.
- Promotional message fields.
- Footer images and links.
- Logo controls.
- Background images.
- Overlay settings.
- Color pickers.
- Presets.
This was not complexity for its own sake. It was the real shape of the business process.
The important engineering move was making the complexity explicit. Fields were inventoried, grouped, tested, and compared against production. Missing banner fields were found. Multi-vehicle fields were verified through the component loop. Advanced styling controls were accounted for.
Once the field map existed, the project became easier to reason about.
Preview Is A Contract
The builder was not just a form. It had to produce a real-time preview that helped the user see the email before it became customer-facing.
That preview creates a contract between input and output. If a color picker changes a title color, the preview should show it. If a vehicle slot is empty, the grid should not leave a strange blank. If a footer image is clickable, the link field should behave accordingly.
Email templates are unforgiving because rendering environments are inconsistent. A builder cannot eliminate that problem, but it can narrow the ways a campaign can go wrong.
The Lesson
The BDC template builder is not glamorous software.
It is practical software. It turns repeated, error-prone marketing production into a guided workflow with known inputs, predictable output, and enough structure to support tracking and review.
That is often where useful internal tools live: not in replacing a business process, but in containing it.