Panels, coverage & products
Understand how vendors are qualified by geography and product type, and how that drives vendor suggestions for an order.
When an order needs a vendor, OmniValVMS suggests the ones who are qualified for it. Qualification comes down to three things: geographic coverage, product compatibility, and capacity. This guide explains the first two and how to manage them.
What makes a vendor a match
| Factor | Meaning |
|---|---|
| Geographic coverage | The vendor works in the order's state/county/zip |
| Product compatibility | The vendor is licensed/configured for the appraisal product |
| Capacity | The vendor isn't overloaded with active work |
| Pricing | A contract-based fee exists for the product |
These same factors drive the suggested-vendor list you'll see when assigning an order — see Assign a vendor.
Product coverage
A vendor's products define what they can do. From the client side, you manage which of a vendor's products are part of your relationship.
| Action | Endpoint |
|---|---|
| List a vendor's products | |
| List subscribed vendor products (your panel) | |
| Add a product to a subscribed vendor | |
| Find vendors who offer a product |
Geographic coverage
Coverage is defined per state and refined per county and product type.
| Action | Endpoint |
|---|---|
| Get a vendor's state coverage | |
| List a vendor's county products | |
| Bulk-add county products |
When matching a vendor to an order, coverage is evaluated from most specific to least specific (zip → county → state). A vendor qualified at the county level for the right product type is a stronger match than one only covering the state broadly.
Per-client product configuration
You can also configure product relationships specific to a client–vendor pair.
| Action | Endpoint |
|---|---|
| List vendor–client products | |
| Add a vendor–client product |
Next
- Fees & contracts — pricing for these products
- Assign a vendor — coverage in action