How EyeSpyR Vendor Verification Actually Works

A vendor becomes "Verified" on Weddings.io through a specific, three-step review process: they submit real work photos through their profile, a human reviewer checks those photos against the vendor's claimed city and category, and — if approved — the verified badge appears on their public profile immediately. No waiting period, no batch processing overnight. The moment a reviewer clicks approve, the badge is live.

That's the short answer. Here's what actually happens at each step, because "verification" gets used loosely enough across wedding platforms that it's worth being specific about what it means here.

How does a vendor submit for verification?

A vendor who wants the verified badge submits through EyeSpyR, the visual review layer built into their profile. The submission isn't just a checkbox — it's photos. Real setup photos, event photos, or work-in-progress shots tied to the vendor's actual city and category, plus optional notes explaining what a reviewer is looking at. A florist submitting from Brampton, Ontario in the "Wedding Planner" category is expected to submit photos that plausibly match that claim — an 800-guest mandap setup, a Sangeet-to-Reception flip, whatever the vendor's specialty actually is.

This matters because the whole point of verification is closing the gap between what a vendor claims on their profile and what they can actually show. A text bio saying "15 years of experience with South Asian weddings" is a claim. A photo of an actual mandap this vendor built is evidence.

What happens after a vendor submits?

The submission lands in a queue with a status of "pending." It sits there — not visible on the public profile, not affecting the vendor's search ranking — until a reviewer with admin permissions looks at it. This is a real access-controlled step: the review queue checks that the person looking at it actually holds an admin role before showing a single submission, not just that they're logged in.

Reviewers see the submitted photos as a grid, alongside the vendor's business name, city, category, and any notes the vendor included. From there, a reviewer has two options: approve or reject. That's it — there's no partial-credit, no "verified with caveats." A submission either demonstrates real, relevant work or it doesn't.

What happens the moment a submission gets approved?

Two things happen at once. First, that specific submission's status flips to "verified," which becomes a permanent part of the vendor's review history. Second — and this is the part that actually matters to couples browsing the directory — the vendor's public profile updates immediately: a verified badge appears next to their business name, visible on their profile page and in directory search results.

There's no separate publish step, no sync delay. The badge going live is a direct consequence of the approval action, not a scheduled job that runs later. A vendor who gets approved at 2:47pm has a public verified badge at 2:47pm.

What happens if a submission gets rejected?

The submission's status flips to "rejected" and stays in the vendor's history — it doesn't just disappear. The vendor's profile stays exactly as it was before the submission: no badge, no penalty, no impact on their existing listing. Rejection isn't punitive; it just means that particular set of photos didn't clear the bar, and the vendor is free to submit again with different evidence.

Why does verified status affect search ranking?

Verified vendors are surfaced first in Weddings.io's vendor directory — search results are ordered by verified status before anything else, meaning a verified vendor with a modest track record still appears ahead of an unverified vendor with a flashier profile. This is deliberate. The directory is built around the idea that a couple planning an 800-guest, multi-day wedding six months out needs to trust that the vendor they're calling is real and reachable — not just well-photographed.

Who can actually review a submission?

Only accounts explicitly granted the admin role. This isn't a "logged-in users can moderate" system — the review interface checks a dedicated permissions table before it will show a single pending submission, and that check happens on every page load, not just once at login. A vendor account, even a verified one, has no access to anyone else's review queue.

Verified vs. unverified: what actually changes

| | Unverified vendor | Verified vendor |

| --- | --- | --- |

| Visible in directory | Yes | Yes |

| Badge on profile | No | ✓ Verified badge |

| Search ranking priority | Standard | Surfaced first |

| Review evidence on file | None required | Real photos matched to city/category |

| Who approved the claim | Self-reported only | Reviewed by an admin |

| Can re-submit after rejection | N/A | Yes, anytime |

Getting verified: the steps

1. Complete your vendor profile with your real city, category, and specialty.

2. Go to EyeSpyR on your profile and submit real work photos — setup shots, event photos, or in-progress work — that match your claimed category and location.

3. Add notes if the photos need context (e.g., "800-guest mandap setup, Brampton, October 2025").

4. Wait for admin review. There's no fixed SLA published, but review is manual, not automated — a real person looks at every submission.

5. If approved, your verified badge appears on your profile immediately, and your listing moves up in directory search.

6. If rejected, revise and resubmit — there's no limit on attempts and no penalty for a rejected submission.