When a marketplace promises "verified vendors", the buyer reads that as a guarantee. When the marketplace's operations team uses the same word, they mean a five-layer check that takes weeks to set up and never stops running. The gap between the two readings is the source of half the disappointment customers experience with repair platforms. This post — useful for buyers who want to know what to demand, and for vendors considering joining a platform — walks through what verifying an IT repair vendor actually involves in India, what the platform's ongoing operating discipline looks like, and what gets a vendor offboarded.
What 'verified vendor' has to actually mean
There are five layers that, taken together, constitute a verified vendor on a serious platform. A platform claiming verification while skipping any of these is using the word loosely.
- Identity and address verification — the vendor is who they say they are, lives where they say they live.
- Background verification — no criminal history, no fraud history relevant to the service.
- Skill grading — the vendor can actually fix what they claim to fix, with category-level granularity.
- Business legitimacy — GST registration where applicable, billable as a legitimate entity, parts-sourcing capability.
- Performance scoring — once active, ratings, completion, on-time arrival, and re-work rate measured and surfaced.
Layers 1, 2, and 4 are upfront; layer 3 is partly upfront and partly continuous; layer 5 is continuous. The continuous layers are what separate a one-time verification (which can rot quickly) from a maintained one.
Background and identity verification
The first set of checks for any vendor onboarding:
- PAN verification — confirms identity against tax records.
- Aadhaar OTP-based verification — confirms current contact and a basic identity match. Many platforms use the Digi-Locker or Aadhaar e-KYC flow.
- Address proof — utility bill, rent agreement, or business address proof matching the operating area.
- Photo verification — selfie video matched against the ID photo, to prevent third-party impersonation.
- Criminal background check — typically run through a verification aggregator. Court record search, police verification where feasible. This is the layer that platforms most often skip in early stages because it's slow and not free.
For vendors who will be physically inside customer offices or homes, the background check is non-negotiable. For pure offsite/pickup vendors, the bar can technically be lower — but in practice, vendor pools mix and a platform that runs two tiers of verification creates confusion.
Skill grading by device category
"Verified" without skill grading is misleading. A vendor who is a Dell-laptop expert may know nothing about MacBook repair, and a printer technician may have never disassembled a desktop PC. Real platforms maintain skill flags per device category — typically: laptop (with sub-flags for Windows, MacBook, ChromeOS), desktop, all-in-one, printer (with sub-flags for laser, inkjet, MFD), peripheral, server-class hardware, ruggedised devices.
Skill is established and re-established through:
- Initial demonstration. A practical test — diagnose a deliberately-faulty unit, walk through the repair plan, explain parts sourcing.
- Reference checks with prior employers or customers.
- First-tickets monitoring. The first 5–10 tickets a new vendor takes are watched closely by ops, with photos and customer feedback reviewed per ticket.
- Category-specific re-certification at 6–12 month intervals, especially for fast-moving categories like Apple Silicon MacBook repair.
A vendor's profile on the platform reflects this granularity: not "verified", but "verified for laptop repair (Windows: yes, MacBook: no), printer repair (laser: yes, MFD: no), with 87 completed tickets across these categories at a 4.6/5 average rating".
Parts handling and warranty
The repair itself is half the job. Parts sourcing, warranty handling, and post-repair support are the other half. Platforms vetting vendors on this dimension check:
- Parts source. OEM authorised reseller, regional distributor, or compatible-parts supplier? Some platforms maintain an approved parts list per category.
- Warranty on the work. The vendor offers a written warranty on labour and parts (typically 30–90 days). No warranty offered is a flag.
- Bill of materials transparency. The vendor's invoices itemise parts by HSN code, brand, and origin. Round-number "service charges" are flagged.
- Re-work handling. The vendor will return to address a failed repair within the warranty period at no additional labour cost.
A vendor who fails on parts integrity is, in the long run, more damaging to a platform than a vendor who fails on punctuality. The platform's reputation is built on the device working two months after the repair, not on the vendor arriving on time.
Performance routing and ratings
Once a vendor is active, a rolling performance score determines how many tickets they get and what kind. The score typically combines:
- Customer rating (1–5 stars), weighted by recency.
- On-time arrival percentage, measured against the agreed window.
- First-visit completion percentage — was the repair completed in one visit or did it require a follow-up?
- Re-work rate — percentage of tickets that returned within the warranty window for the same issue.
- Acceptance rate — does the vendor accept tickets they're offered, or reject most of them?
- No-show rate — separately tracked, harshly weighted.
A high-scoring vendor gets priority assignment within their skill flags and geography. A declining score triggers a soft intervention (ops conversation, request for improvement plan), then a hard intervention (reduced ticket volume, smaller-fee tickets only), then offboarding.
The offboarding rule
A platform that won't offboard underperforming vendors is one that has the wrong incentive structure. The conditions that should reliably remove a vendor from the verified pool:
- Two-strike rule on customer-reported integrity issues — anything that looks like dishonest billing, parts substitution without disclosure, or attempted upsell of unnecessary services.
- Three-strike rule on no-shows within a 90-day window.
- Any DPDP-relevant violation — a vendor mishandling customer data, photographing a device's contents, or copying files. Single-strike offboarding.
- Sustained low rating — average drops below threshold (typically 4.0/5) for 30+ days despite intervention.
- Refusal to honour repair warranty — failing to return for a documented re-work within the warranty window.
Offboarding is messy when it's done quietly; that's fine. The platform's job is to keep the bar up for customers, not to maintain optics for vendors. A network that has never offboarded is one that hasn't pruned, and an unpruned network ends up unverified in practice.
How Fixr runs vendor onboarding
Fixr by Hives.cloud runs a structured five-layer onboarding before any vendor takes a customer ticket: identity verification, background check, skill demonstration by device category, business legitimacy (GST and billing verification), and an initial 5–10 ticket close-monitoring window. After onboarding, vendors are routed by skill flag and geography, with a rolling performance score that determines ongoing assignment priority. Offboarding criteria are written into the vendor agreement at onboarding, and the platform's Super Admin role intervenes when a vendor's metrics drift.
The economics of the relationship: customers pay nothing to the platform. Vendors bill the customer directly for the repair work, issuing their own GST invoice. The platform's role is routing, validation, real-time tracking, and audit — not transaction-fee collection. For vendors, the value of being on the platform is access to a steady ticket stream, validated requests (no wasted visits), and an audit-backed reputation system that rewards quality. If you're a verified IT repair vendor in India interested in joining the Fixr network, the application path runs through the Fixr product page.
What buyers should ask, what vendors should expect
For buyers, the questions to put to any platform claiming "verified vendors":
- Show me a sample vendor profile. What does the verification record look like?
- Walk me through what happens when a vendor underperforms.
- How many vendors have been offboarded in the last six months, and why?
- What's the average tenure of a vendor on the platform?
For vendors evaluating a platform to join:
- What's the upfront verification process and how long does it take?
- How does ticket assignment actually work? Pure algorithm, or operator-mediated?
- What does the platform charge me as a vendor? Per-ticket, monthly, or zero?
- What's the dispute path if a customer rating is unfair?
- What's the offboarding policy, and is it written?
A platform that answers all of these clearly on both sides is one that has built the operating system, not just the marketing site.
FAQs
Can I trust a 'verified' vendor without checking the platform's process? The label is only as good as the underlying process. Ask for the specifics. A platform that won't describe its verification beyond the marketing copy isn't running a serious one.
How long should verification take? Realistically 3–7 working days for the basic layers (identity, background, business legitimacy), plus another 1–2 weeks of skill demonstration and first-tickets monitoring. Platforms claiming sub-24-hour onboarding are skipping layers.
Do vendors pay to be on the platform? Depends on the model. Take-rate platforms charge a percentage of the invoice. Free-platform models (like Fixr) typically charge vendors a small fixed fee per accepted ticket, or earn through other revenue streams.
Can a vendor be on multiple platforms? Almost always yes. Vendors rarely commit to a single platform; they pick up tickets from whoever offers them volume and reasonable terms. A platform that demands exclusivity early is unusual and worth questioning.
What's the difference between this and just calling a local technician I know? Trust source. A known local technician is trusted because of your prior relationship; a verified platform vendor is trusted because of the platform's process. The platform model becomes valuable when you need depth (specific skill flags), reach (multiple cities), or auditability (an audit trail you can produce later).