For providers

Listing cover for sale

How a product you already underwrite becomes something a stranger can find, compare and buy on iqava.com — and what reaches you after they do.

Selling on iqava is not a listing site with a contact form attached. A published cover is wired into the same platform that runs your back office: the buyer's answers become a real application, a purchase becomes a real policy on your real ledger, and the documents land in their wallet. Which is also why the listing deserves more care than a brochure would.

ProductListingWhat buyers comparePublishOrdersPolicy

The short version

  1. Build the product first
    Product Studio — the product, its rating and its proposal form. A listing with no product behind it can take applications but can never issue a policy.
  2. Create the listing
    Marketplace → Studio — title, category, summary, highlights, price and the countries it may be sold in. Link it to the product from step one.
  3. Fill in what buyers compare
    The six fields and the exclusions list that let a shopper put you beside a competitor. The sum insured is the one that matters most.
  4. Publish
    Live on iqava.com and in the app immediately. There is no approval queue between you and a buyer.
  5. Watch Marketplace → Orders
    Every sale, its state, and the policy it became. Bound policies appear in Underwriting exactly like ones your own team wrote.

What it costs to list

Publishing cover on iqava.com carries no commission on any plan — we take no cut of what you sell. The plan you are on governs how many users and active policies you can hold, not whether you can reach buyers, and it starts at $3 a month after a 14-day trial. See pricing.

Writing the listing

Two fields do most of the work, and both are easy to write for the wrong reader.

The title is what appears in search results. Say the cover, not the brand — “Comprehensive Motor — Private” rather than “MotorPlus Gold”. Somebody searching does not yet know your product names.

The summary is one line on the card, and it is the only sentence most people read. “Comprehensive cover for private vehicles, including theft and third-party” beats “Section A/B/C cover with optional extensions”. The legal wording still belongs in the description; it is just not the first thing anyone should meet.

An empty country list means everywhere

Countries restrict where a cover may be sold. Leaving the list empty does not mean “nowhere yet” — it means the cover is offered to buyers in every country. If you are licensed in one market, say so.

Categories are shared

Categories drive the buyer-facing filters across every provider. Use an existing one if it fits. Inventing a category splits the aisle and makes your own product harder to find — and a category with a single product in it looks empty.

What buyers compare

Under Product Studio → What buyers compare there are six fields and a list. They are what the comparison page lines up when a shopper puts your cover beside a competitor's, and they appear as Key terms on your own detail page.

FieldWhat it is
Sum insuredThe most this cover will pay out.
Cover periodMonths. Usually 12 — travel and device cover are not.
Excess — fixed amountWhat the insured bears on each claim.
Excess — percentOr a percentage of the sum insured, as motor often uses.
Waiting periodDays after inception before a claim can be made.
Claim settlementWhat you commit to once a claim is agreed.
Key exclusionsOne per line. What this policy will not pay for.

Fill in the sum insured, if you fill in nothing else

It decides whether your premium can be compared at all. A premium is marked best only when every cover in the table insures the same amount. Cheaper cover for less cover is not cheaper, and saying otherwise would send a buyer to a policy that will not pay their claim. So when sums insured differ — or when any of them is blank — no premium wins, and the buyer is told why.

That cuts both ways. Leave it blank and your keenly-priced cover can never be shown as the cheaper one. State it, and against a competitor charging more for the same cover, you win the row.

A blank is shown, not hidden

Every field is optional, and anything you leave out appears in your column as “Not stated”, beside a competitor's number. Nothing is guessed, defaulted or quietly dropped — a gap is information about the seller, and buyers read it that way. The exclusions list carries its own note: a blank there means the provider has not listed exclusions, not that there are none.

The two excess fields

Set either, or both — both is common in motor (“2.5% or KES 10,000, whichever is greater”). A percentage is never compared against a flat amount: they are different kinds of number, and converting one needs a sum insured that may not be there. If your excess really is a flat figure, give the amount and leave the percentage blank so it can compete.

Rows that are never a contest

Some rows have no winner by design, so there is nothing to game. Cover period — a month of travel cover is right for a month's travel. Exclusions — a longer list may be a meaner policy or a more honest one, and no table can tell which. Anything across currencies — two prices in different currencies are not compared, in either direction.

The comparison page also tells buyers how complete it is — “these providers have filled in 60% of the comparable details” — so a half-filled listing is visible as one. Above the table, iqava's assistant writes a short plain-English note on what differs. It is built only from the figures you published: it explains, and it never recommends.

Pricing by vehicle value

A published price answers “from how much?”. It does not answer the question every motor buyer actually has, which is what their car costs. Publish a rate under Product Studio → Price by vehicle value and the cover page grows a calculator:

premium = max(rate% × vehicle value, minimum premium) + statutory levies

The levies — training levy, PCF and stamp duty — are added by the same code that produces a bound policy's debit note, so the figure a buyer decides on is the figure they are charged. The buyer sees the whole build-up, not just a total.

Set a minimum premium

Without one, a rate alone will quote a very cheap car at a price you would not write. When the floor bites, the buyer is told so explicitly — otherwise the calculator looks broken as the number stops moving.

Bounds are a referral, never a decline

The lowest and highest values you quote do not turn business away. Outside them the buyer is asked to apply so you can quote individually, because a marketplace refusing a risk on your behalf loses you business you may well have wanted.

Leave it blank for flat-priced cover

Third-party-only motor is a flat premium and is not rated on value — leaving these empty is correct, and the calculator simply does not appear. It is an estimate either way: the page says plainly that the final premium is yours to confirm, since no-claims discounts, usage and driving history are yours and not ours to guess at.

Publishing

draft — nobody sees it. published — live on iqava.com and in the app immediately. archived — gone from search; policies already sold are unaffected.

Before you publish, read your own detail page as a stranger on a phone:

  • Does the summary say what this covers, in one line?
  • Is the price the real starting price, or an optimistic one you will argue about at claim time?
  • Do the highlights match the policy wording?
  • Would you buy it without ringing anyone?

An unattended listing still sells

There is no queue between a buyer and a purchase. Anything your referral rules accept is bound automatically — that is the point of straight-through processing, and it is also the trap. If there is a case you want to see first, write the rule; do not rely on noticing the order. If you are not ready to write the business, leave the listing in draft.

After a sale

A purchase runs in one go:

OrderPaymentPolicy boundSchedule + debit notePosted to your ledgerIn the buyer's wallet

Marketplace → Orders is the seller's view of that loop. Underwriting → Policies holds the policy itself, indistinguishable from one your own team bound — same ledger treatment, same documents, same renewal path. The premium, levies and any platform fee are already posted in Finance.

Renewals happen without you

Cover inside 30 days of expiry appears in the buyer's wallet as renewable, priced at your current listing price rather than last year's. Both figures are shown, so a price rise is visible rather than sprung. Withdraw the listing and existing policies stop being renewable — the buyer is told to contact you rather than left to lapse silently.

Claims answer to the date of loss

A buyer can claim against any policy that was in force on the date the loss happened, including one that has since expired or been renewed. Photos and PDFs arrive attached. The claimant's own figure is recorded as an estimate — it is not a reserve, and it does not touch your P&L until a handler assesses it.

Things that catch people out

  • The listing takes a snapshot. Editing the product's proposal form does not change a live listing. Update the listing to pick up the new form.
  • A blank comparison field is not neutral. It reads as “Not stated” next to a competitor's number, and without a sum insured your premium can never be marked the better one.
  • Taking money needs your gateway keys. Payment credentials are set per provider in the console. Without them an order stops at AWAITING_PAYMENT and you settle it by hand — everything else in the chain still runs.

The same catalogue, over the API

Every published cover is on a no-auth JSON API — GET /api/marketplace/listings, /listings/{id} including the proposal form, and POST /listings/{id}/apply. It is the surface the mobile app and partner integrations consume, so a cover published here reaches all of them at once. See Product Studio & Marketplace for the wider distribution picture.