Skip to main content

Product spotlights

Warranty Document Portal for Photos & Contracts

Product spotlights9 min readMay 21, 2026By Gabriel, who runs a working PPF and detailing shop in Canada
A dark shop-software document library grid showing tagged install photos, contract and warranty PDFs, with a share-link panel and a private-bucket lock badge.
Illustration

The short version

  • The Document Portal is a searchable library for install photos, contracts and warranties, with first-class tags and filters by kind.
  • Files are filed to the record they belong to — customer, vehicle, job, quote or invoice — and surface right on those pages.
  • You share documents with customers through expiring, revocable links that carry view telemetry, sent over the same compliance-gated text and email rail as everything else.
  • Uploads go straight into a private storage bucket, and previews are served through short-lived signed links, never public URLs.
  • Every document action lands on an audit trail, so a sensitive contract or warranty has a paper trail of its own.

Where your paperwork actually lives right now

A customer calls two years after a full front asking for their warranty paperwork, and you're digging through a phone, an email thread, and a folder on the shop laptop. The document should have been one tap away, tagged and tied to that car. That's what a real document portal is for.

Be honest about where your files sit today. The install photos are on somebody's phone — maybe the tech who shot them, maybe a phone that walked out the door when he did. The signed contract is a scanned PDF buried in an email chain, and you're not totally sure which reply it's attached to. The warranty is in a folder on the front-desk computer called something like WARRANTIES FINAL, next to WARRANTIES FINAL 2, and neither one is searchable by the customer's name because you saved it as scan_0047.pdf at four in the afternoon on a busy Friday.

None of that is a character flaw. It's what happens when the paperwork lives in three tools that were never meant to talk to each other. The camera roll is for pictures of your kids, not for evidence. Email is for messages, not for filing. A desktop folder is where documents go to be forgotten. The system works fine right up until the one moment it has to work — a warranty claim, a chargeback dispute, an insurance adjuster asking you to prove the panel was already scratched at intake — and in that moment you're on the back foot, scrolling, sweating, hoping the file still exists.

The fix isn't a tidier folder or a stricter naming rule that nobody follows past week two. It's treating a document like a record that belongs to a customer and a car, not a file that belongs to a device. Let me walk you through what that looks like on the shop floor.

One library, tagged and searchable

Start with the thing you interact with every day: the library itself. In Service VIN, the document portal is a single /documentsview that holds everything — install photos, walk-around video, warranty PDFs, signed contracts, care sheets, release forms. It belongs to the shop, not to whoever's phone shot the picture, and that distinction matters the day a tech leaves.

Two things make it a library instead of a pile. First, every file carries a kind — photo, video, PDF, contract, signature — and its own tags. Second, you can search by name and filter by tag or kind, so finding a file is a search, not an excavation. Type warranty, filter to PDFs, and you're looking at every warranty in the shop in about three keystrokes. Click the #beforetag and every intake photo you've ever shot lines up. The warranty from last spring is a filter away, not a thirty-minute scroll through a camera roll.

And you don't have to download a thing to check it. Images, PDFs and video preview inline, right in the app, so you can glance at a contract to confirm it's the signed copy without pulling it down to your desktop first. That sounds like a small convenience until you realize how much of the day-to-day scramble is just opening files to see which one is the right one. The preview kills that whole errand.

A quick note on what a shop's library actually tends to hold, because it shapes how you'll want to tag it. The mix below is an illustrative example — a sample, not measured data from any real shop — but it matches the shape of what most of us accumulate: photos are the bulk of it, warranties and contracts are fewer files but the ones you can least afford to lose.

What's in a shop's document library (illustrative)Illustrative example
  • Install photos45%
  • Warranties25%
  • Contracts / releases20%
  • Invoices / other10%

Illustrative example of document types in a shop library — a sample mix, not measured data from any real shop.

What's in a shop's document library (illustrative)
SegmentValueShare
Install photos4545%
Warranties2525%
Contracts / releases2020%
Invoices / other1010%

Files that live on the record

Here's the part that actually saves you, and it's not the search — it's where the documents live. A file in Service VIN doesn't just sit in the library. It files to the record it belongs to, through a system that can attach one document to a customer, a vehicle, a job, a quote or an invoice. Then it surfaces on that record's page, right where the work happens.

Sit with what that means for a warranty. The warranty and the before-and-after photos don't live in a folder named after a month you'll never remember. They live on the customer and vehicle record— on the exact car they belong to. So two years from now, when that customer calls, you don't start with "let me go dig." You open their car in the garage, and the paper trail is already sitting there: the contract they signed, the warranty you registered, the delivery shots from the day it left.

One file can be filed under more than one record, too, which matches how the work really flows. The signed install agreement belongs to the customer andto the job it covers, so it shows up on both. And filing is not the same as trapping — unfiling a document from a record never deletes it; it stays in the library. You're organizing, not risking the file every time you tidy up.

The reason I harp on this is that a document you can't find at the moment you need it may as well not exist. A warranty in a folder nobody can locate isn't protection — it's a rumor. Filing it to the car turns it from a rumor into something you can produce on the phone, one-handed, while the customer is still talking.

Sharing without losing control

Eventually you have to hand a document to the customer, and this is where most shops quietly create a problem for themselves. You attach the warranty PDF to an email or a text, hit send, and now there's a permanent, uncontrolled copy of your paperwork living in a stranger's inbox forever. You can't expire it. You can't pull it back. You have no idea if they ever opened it. If it gets forwarded, it just keeps going.

The portal does this differently. When you share a document with a customer, you send an expiring, revocable link over the same compliance-gated text and email rail everything else goes out on — the one that respects opt-outs and messaging rules on every send. The customer taps it and lands on a clean, read-only page with your shop's name on it. No account, no app, no login. And you keep the controls: the link expires on its own, you can revoke it in one click, and it carries view telemetry so you can see whether they actually opened it and when.

That last bit changes the whole texture of a conversation. "Did you get the warranty?" stops being a question you have to ask, because you can see the link was opened twice this morning. And if a deal goes sideways, or a customer parts ways on bad terms, you're not stuck knowing a live copy of your contract is floating around out there. You revoke the link and it's dead. You're sharing access, not surrendering the file.

Private by default, audited always

Contracts and warranties are exactly the kind of documents you don't want sitting behind a guessable public URL, so the plumbing underneath matters more here than it does for, say, a stock photo.

Uploads go straight into a private storage bucket. There are no public links to your files — not even for you. When you preview a document, the system mints a short-lived signed link, valid for a little while and then gone, only after it has confirmed you're allowed to see that file. Same for the customer-facing share page: what the customer opens is a temporary, permissioned view, not a permanent address anyone who guessed the path could reach. Every shop's files are isolated from every other shop's at the database level, so there's no world where your neighbor's warranties and yours end up in the same drawer.

And every document action lands on an audit trail. Uploads, renames, filing to a record, shares, revokes, deletes — each one is written to the log, with who did it and when. For most files that's just good hygiene. For a signed contract or a warranty registration, it's the difference between "we're pretty sure we sent that" and a timestamped record you can point at. When the document is the evidence, the history of the document is evidence too.

The two-year test

Here's the only benchmark that matters for a document system: pick a car you wrapped or filmed two years ago and try to produce its signed contract, its intake photos and its warranty in under a minute. If you can't, the paperwork isn't protecting you — it's just taking up space until the day it fails you. File it to the car now and the two-year test becomes a lookup instead of a scramble.

Why this protects a warranty claim

All of this stops being abstract the day something goes wrong on a car, because that's when a document's only job is to be found and be trusted. Two situations come up over and over in this trade, and the portal is built for both.

The first is the pre-existing damage dispute. A customer comes back swearing a rock chip or a scratch happened in your bay. If your intake photos are tagged #before, timestamped, and filed to that job, the conversation is over before it starts — you pull the job, you show the panel as it arrived, and everybody moves on. That documentation is only as good as your ability to produce it on demand, which is exactly what filing photos to the record buys you. This is also why the capture end matters: when your guided install photos flow straight from the bay into the same library, the evidence is complete without anyone playing photographer after the fact.

The second is the real warranty claim. Any good film comes with a warranty — I run STEK day to day and stand behind the coverage — but a warranty is only worth what you can prove. When the before-and-after photos and the signed contract are all tagged to the VIN and sitting on the car's record, a claim is a clean, defensible package: here's the vehicle, here's what we installed, here's the paperwork, here's the condition on the day. That's the difference between a claim that gets honored and a claim that turns into a week of arguing over what you can't document. Scattered paperwork loses claims. A tagged, filed, auditable record wins them.

Setting up your document library

You don't need an elaborate system to get the payoff — you need a handful of tags you'll actually use. Start narrow. A kind tag for the stage (#before, #after, #delivery), a kind tag for the document type (#warranty, #contract, #care), and maybe a service tag (#ppf, #tint, #ceramic) if you run more than one line. That's it. Tag the batch as you upload, file it under the job or the customer while it's fresh in your head, and the library organizes itself from the work instead of from a filing session you keep putting off.

The habit that makes it stick: file at the moment of the work, not at the end of the month. Shoot the intake photos before the car goes on the lift and file them to the job right then. Register the warranty and file it to the customer the day it's issued. Send the contract as a share link instead of an attachment so you keep the controls from the start. Do that on every car and you're never reconstructing a paper trail after the fact — it built itself while you worked.

The document portal is part of the core shop OS, included on every plan from the entry tier up — you can see pricing and the free trialto start filing your own paperwork. Get your evidence out of the shoebox and onto the car, where you'll actually look for it. The next warranty claim that walks in the door will be the easiest one you've ever handled, and that's worth a lot more than a tidy desktop folder.

Frequently asked questions

Can I attach a document to a specific vehicle, not just a customer?

Yes. Documents file through a polymorphic attachments system to customers, vehicles, jobs, quotes or invoices, and they surface on that record's page. So a warranty and the install photos live on the exact car they belong to, which is where you'll go looking two years later.

How do I share a warranty with a customer safely?

You send an expiring, revocable share link over the compliance-gated text or email rail. The link expires on its own, you can revoke it in one click, and it carries view telemetry so you know whether the customer actually opened it. You're never emailing a permanent, uncontrolled copy into someone's inbox.

Where are the files stored, and who can see them?

Uploads go directly into a private storage bucket, and previews are served through short-lived signed links rather than public URLs. Shops are isolated from each other, and every document action is written to an audit trail, so there's a record of what happened to a sensitive contract or warranty.

Can I find a document without remembering exactly where I put it?

Yes. The library has first-class tags, filters by kind, and name search, plus inline previews for images, PDFs and video. You filter or search instead of digging through folders, and you can preview a file to confirm it's the right one without downloading it first.

Gabriel headshot

Gabriel, who runs a working PPF and detailing shop in Canada

Runs a working PPF and detailing shop in Canada · builder of Service VIN

Gabriel runs a working PPF and detailing shop in Canada and built Service VIN. He got his start detailing and wrapping his own car, taught himself color PPF, and spent his day job in digital marketing and SEO before building the shop software he could never find. Six years in, he writes to help other owners get out of the bay and actually run their business.

Keep reading

The newsletter

Get the next one in your inbox

Pricing, quoting, hiring and margin — written from the bay and the books. We send new posts and nothing else.

New posts about twice a month. No sales blasts, unsubscribe in one click.

Run your shop on Service VIN

Quote for margin, book without double-booking, and put your follow-up on autopilot. Try every feature free for 14 days — no credit card required.