Capsule PPF — Warranty Platform & Dealer CRM
Capsule is a premium automotive paint protection film brand. Their product is applied by a network of certified installers, sold through dealers, and comes with a warranty the end customer needs to be able to trust.
That last part is the whole problem.
The problem
A paint protection warranty is only worth something if it can be verified. The customer paid for a product they cannot see, applied by someone they met once, backed by a promise on a piece of paper.
Meanwhile, three different groups need three different things from the same system. Dealers manage inventory and orders. Installers register the work they have done. Admins need to see across all of it. And the end customer needs one thing: to type in a number and find out whether their warranty is real.
Those are four separate products sharing one database, and building them as four separate things would have been four times the work and one guaranteed source of data that disagrees with itself.
What we built
A single platform with role-based access, where each group sees the interface built for them and nothing else.
Warranty verification portal. The customer-facing side. A product is registered when it is applied; the customer can verify it and see its status. No account, no friction — the point is to answer one question fast.
Product registration, in real time. Installers register applied product at the point of work. The registration is what creates the warranty, which means the warranty record and the physical reality stay in step by construction rather than by someone remembering to update a spreadsheet.
Warranty tracking with dynamic status. A warranty is not a static document — it has a state that changes over time. The system tracks it and reflects it wherever it appears.
Admin CRM. Product inventory, orders, and analytics in one place. Built for the people who run the business, not adapted from a generic dashboard.
Multi-role architecture. Dealers, installers, and admins log into the same system and get entirely different views and permissions. One codebase, one source of truth, three products.
Why it was built this way
The obvious shortcut is a separate warranty lookup bolted onto a normal website, with the CRM somewhere else, and someone syncing between them.
That works until it does not — and when it fails, it fails at the worst possible moment: a customer checking a warranty gets an answer that contradicts what the dealer sees. Trust in the warranty is the product. A system where two screens can disagree about the same warranty is not a technical flaw, it is a business risk.
So the platform was built as one system from the start, with permissions rather than separation. There is one record of what exists. Everyone sees the part of it they are entitled to see.
Result
A platform where a customer can verify their warranty in seconds, an installer can register work in the field, a dealer can manage stock and orders, and an admin can see the whole picture — all from the same data, with no synchronisation step to go wrong.
Capsule also runs a separate closed B2B store for partner ordering, which we built alongside this platform.
Built by DAKER — design, development, deployment.
