WordPress development
A custom theme to move a wrap shop off a page builder
A Mesa vehicle wrap shop was running on a hosted website builder. We built a custom WordPress theme to move it onto software the business owns — with quote capture and appointment booking as first-class parts of the site rather than third-party embeds. The theme is complete. The migration has not happened yet, and this page says so.
- Client
- A vehicle wrap and vinyl graphics shop, Mesa AZ (name withheld)
- Work
- Custom WordPress theme, quote capture, appointment booking
- Built
- Custom theme by AZ Web Corp — 8 page templates, quote and booking systems
- Status
- Theme complete, not yet deployed
A vehicle wrap and vinyl graphics shop
01 — The problem
A hosted builder is rented software
The shop's site runs on a hosted website builder. That is a reasonable place to start — it needs no maintenance, and somebody with no technical background can edit it.
It becomes a problem when the business needs the site to do something. A wrap estimate is not a contact form: it depends on the vehicle, the coverage, whether existing graphics have to come off, and whether design work is needed. Getting that into a builder means either a generic form that collects too little to quote from, or a third-party form service holding the customer data.
There is also the ownership question. On a hosted builder the site is not an asset the business controls; it is a subscription. Move, and the site does not come with you.
02 — What was built
A theme that does the quoting
The theme was written specifically for a vehicle graphics business, which means the things that matter to that trade are part of the software rather than bolted on.
- Quote requests as a custom post type, stored in the WordPress dashboard. Nothing depends on an email arriving, and enquiries survive a mail outage.
- A quote form built around how wraps are actually quoted — vehicle details, coverage, existing graphics, and whether design is needed.
- Appointment booking with its own availability and confirmation logic, so a customer can arrange a fitting without a phone call.
- Eight page templates: home, about, services, gallery, quote, booking, contact and the archive fallback.
- A separate quote form script and booking script, kept apart from the general site JavaScript so a problem in one cannot break the other.
- Template tags for the parts that repeat — service cards, gallery items, process steps — so the client's edits stay consistent across pages.
03 — Where this actually stands
Built, reviewed, not deployed
It would be easy to describe this as a completed migration. It is not one, and saying so matters more than the case study reading well.
The theme is finished and runs. The live site is still on the hosted builder — the shop's public URLs still resolve to it, and none of the WordPress routes exist on the public domain. The migration has not been scheduled.
What that means honestly: there is a working replacement, and the business has not switched to it. That is a normal place for a project to pause — migrations disrupt a working sales channel, and they get scheduled around the quiet season rather than around the developer's readiness.
04 — Why it is worth doing anyway
The argument for moving
Three things change when a site like this moves off a builder onto WordPress the business controls.
The quote data becomes the business's. Right now, an estimate request lives in a third-party service. Afterwards it lives in a database the business owns, and can be exported, searched and reported on.
The site becomes an asset rather than a subscription. It can be hosted anywhere, moved, or extended by any developer — none of which is true when the site exists only inside somebody else's product.
Search structure becomes possible. A builder gives you pages. It does not give you control over markup, structured data for a local service business, or the internal linking that lets a services page and a gallery page reinforce each other.
None of that is a traffic claim. It is what changes about ownership, which is the actual reason for the project.
Page templates built
8 increase
Each written for its job
Enquiry systems
2 increase
Quote capture and appointment booking
Third-party embeds
0 increase
Quote and booking are part of the site
Migration status
Not done no change
Live site still on a hosted builder
Technologies used
- WordPress
- Custom theme
- PHP
- JavaScript
- Custom post types
Want results you can check?
Tell us what you are trying to fix and we will tell you honestly whether we can measure it.