Configure base rate, category and age multipliers, coverage caps, deductibles and preliminary tests, then issue insurance policies on customer devices with automatic premium calculation and a policy PDF. Enterprise plan feature.
From Company > Services > Device insurance, a feature reserved for companies on the Enterprise subscription plan, your repair center software turns into a genuine in-house insurance engine: you can configure the parameters of the policies offered to customers and issue new coverage with automatic premium calculation based on the device data, its age, and the results of preliminary technical tests, generating a policy PDF ready to hand to the customer.
Why it matters for a repair center
A smartphone and PC repair shop that sells new, refurbished, or used devices has a natural opportunity to offer a high-value add-on service: accident-damage coverage, often cheaper and simpler to activate than third-party insurance, because it's managed directly by the same shop that will later carry out any warranty repair. For the repair center this means an extra revenue stream and stronger customer loyalty, since the customer knows they can come back to the same shop in case of damage, without having to deal with external insurance companies. To be credible, though, this kind of service needs to rest on a serious premium calculation and a device condition check at subscription time — exactly what the Device Insurance module provides.
In practice
In the service configuration you set the policy's base annual rate (a percentage applied to the device's declared value) and the multipliers that adjust it based on the device category (for example smartphone, tablet, laptop) and its age, automatically derived from the model's release year when linked to the brand-and-model catalog, or entered manually by staff. You also configure the maximum number of claims allowed per year, the reimbursement cap for each claim, the deductibles the customer can choose between, and any premium discounts. You can define multiple available coverage durations (for example 12 or 24 months) for the customer to choose from at subscription time.
The module's strength lies in linking premium calculation to a real technical check of the device: before issuing a policy, staff can run a series of preliminary tests (drawn from a configurable checks catalog — for example screen condition, battery, buttons, camera function) and record a pass or fail result for each. Every failed (KO) test is automatically turned into a coverage exclusion, meaning a pre-existing defect that won't be covered in a future claim: this protects both the shop and the customer from disputes over damage that already existed before the subscription. Photos of the device taken during the check can also be attached, staying linked to the policy as proof of condition at issuance.
Once all the data is entered, the system automatically calculates the premium to apply, combining the device's declared value, the base rate, the category-and-age multipliers, the chosen coverage duration, and the selected deductible: the calculation is transparent and shows a breakdown of how the final amount is reached, so you can explain to the customer why the premium is what it is. Upon confirmation, the policy receives a unique public code and a document number sequential per year, and a downloadable policy PDF is generated. From the "Issued documents" tab you can search and view your company's already-issued policies at any time, filtering by shop or search text (document number, device description, serial, IMEI, or customer name), and void a policy if needed, for example due to an issuing error or a customer request.
Quick guide
- Go to Company > Services > Device insurance (visible only with an active Enterprise plan).
- Enable the service and configure the base rate, multipliers by device category and age, maximum number of claims, coverage cap, deductibles, premium discounts, and available coverage durations.
- To issue a new policy, select the device and enter the customer's data.
- Run the preliminary tests defined in the checks catalog, marking each item as pass or fail.
- Upload photos of the device to document its condition at issuance.
- Check the breakdown of the automatically calculated premium and issue the policy.
- Download or print the policy PDF and hand it to the customer.
- View or search already-issued policies from the "Issued documents" tab, voiding them if needed.
Real-world use cases
Selling a refurbished smartphone with coverage included. A repair shop that also sells refurbished devices offers the customer, at the time of purchase, an accident-damage policy: it runs the preliminary tests on the device (screen, battery, cameras), finds no issues, issues the policy with a premium calculated on the sale value, and hands over the PDF along with the receipt.
A device with a pre-existing defect noted on the policy. During preliminary tests on a tablet a customer brings in for insurance, the technician finds the volume button doesn't respond correctly: the test is marked as failed and automatically becomes a coverage exclusion, so if the customer later files a claim related to exactly that button, the policy can correctly exclude it, avoiding disputes.
A customer comparing different coverage durations. A customer torn between a 12-month and a 24-month policy asks the shop how much the premium changes: thanks to the automatic calculation and the premium breakdown shown on screen, staff can display both figures in real time and help the customer choose the option that fits best.
Tips and best practices
Always run the preliminary tests before issuing a policy, even when they're not mandatory in the configuration: documenting the device's real condition protects both the shop and the customer from future disputes. Always attach a few photos of the device at issuance, so you have visual proof of its starting condition. Periodically review the base rate and multipliers based on the claims actually handled, to keep premiums balanced with the service's real costs. Communicate clearly to the customer which exclusions result from the preliminary tests, so they know exactly what is and isn't covered.
Common mistakes to avoid
Don't issue a policy without first checking that the service is actually enabled for your company: without an Enterprise plan the module stays locked. Don't skip preliminary tests on used or refurbished devices: an undocumented pre-existing defect can turn into a claim disputed by the customer later on. Don't forget to set a realistic coverage cap relative to the value of the devices you handle: too low a cap makes coverage practically useless, too high a cap relative to the configured rate can make the service run at a loss. Don't confuse this module with warranty extension, found in the same Services section but with different logic and purpose (covering malfunctions beyond the standard warranty, not accidental damage).
Frequently asked questions
Who can use the Device insurance feature? It's a feature reserved for companies with an active Enterprise subscription plan.
How is a policy's premium calculated? The system calculates it automatically by combining the device's declared value, the base rate, the multipliers configured for device category and age, the chosen coverage duration, and the selected deductible, showing a full breakdown of the calculation.
Do I always need photos or tests before issuing a policy? It's not technically mandatory, but strongly recommended: every failed test becomes a coverage exclusion recorded on the policy, protecting both the shop and the customer.
What happens if a preliminary test fails? The detected defect is automatically added as a coverage exclusion on the policy: any future claim related to that same defect won't be covered.
Can I view policies issued in the past? Yes, from the "Issued documents" tab you can search by shop or text (document number, device, serial, IMEI, or customer) and view the details or the PDF at any time.
Can I cancel a policy after issuing it? Yes, you can void a policy from its detail page, for example in case of an issuing error or a customer request.
