Discover
Opportunity Engine
Purpose defined — implementation details being confirmedIdentifies actionable matches between retained buyer demand and merchant supply. A match surfaces as a reviewable next step — not automatic outreach. Match ≠ approval, payment or revenue.
The problem
Merchants know buyers have expressed interest, but cannot track every retained intent against a changing catalogue. Restock events, new listings and opened slots go unmatched to waiting buyers.
Who uses it
- ·Merchants with waiting lists or retained buyer intent
- ·Sellers who restock items with known buyer demand
- ·Service providers with variable availability
- ·Businesses wanting to match supply events to buyer conditions
Where Opportunity Engine sits in the system
Conversation
Captures need
Product Intent
Retains conditions
Catalogue
Supply
Opportunity Engine
Match
Pricing Engine
Valid terms
What it does
Specific functions
Intent–supply matching
Compares retained buyer conditions (category, size, budget) against available catalogue items.
Service slot matching
Matches retained service intent against newly opened calendar slots.
Reviewable next step
Matches surface as review cards — not automatic outreach. Merchant decides action.
Match eligibility display
Shows buyer conditions, matching item or slot, price vs. budget, and whether conditions are met.
Dismiss or act
Merchant can dismiss a match or proceed to contact buyer subject to channel rules.
Step-by-step scenario
Product intent match — illustrative example
Illustrative example. All figures fictional.
1
Buyer expresses intent
Ada tells a seller: "I'm looking for a Size 12 evening dress under ₦60,000." Intent retained in system with conditions: category=evening dress, size=12, budget≤₦60,000.
2
Intent stored
Product Intent record created for Ada. Not a cart. Conditions persist until matched, expired or removed.
3
New stock arrives
Merchant restocks: "Black Lace Evening Dress, Size 12, ₦55,000." Catalogue record published.
4
Match identified
Opportunity Engine evaluates Ada's intent against new stock. Conditions met: size matches, ₦55,000 ≤ ₦60,000 budget.
5
Match shown to merchant
"Ada's request · Size 12 evening dress · Budget ≤₦60,000 · New stock: ₦55,000 · Eligible." State: Review needed.
6
Merchant reviews and decides
Merchant reviews match card. If appropriate, reaches out to Ada — subject to channel consent rules. Match ≠ automatic message.
Match illustration
Opportunity match
Review needed
Buyer intent · Ada
Category: Evening dress
Size: 12
Budget: ≤ ₦60,000
Retained intent — not a cart
New stock · Catalogue
Product: Black Lace Evening Dress
Size: 12
Price: ₦55,000
Within budget ✓
Review match
Dismiss
Reviewing this match does not send a message to Ada. Outreach requires merchant action subject to channel rules.
Service intent match — illustrative example
Service opportunity
Review needed
Service intent · Buyer B
Service: Workspace photography
Day preference: Tuesday
Budget: ≤ ₦50,000
Newly opened slot
Tuesday 2:00 pm — now available
Service price: ₦45,000
Within budget ✓
Match ≠ confirmed booking. Merchant review required before any outreach.
Controls, approvals and outcome states
Match identified
Conditions met between intent and catalogue or slot. Review card surfaced to merchant.
Review needed
Merchant has not yet acted on the match. No outreach has occurred.
Dismissed
Merchant chose not to act on this match. Intent may still match future stock.
Acted
Merchant proceeded to contact buyer subject to channel rules. Match resolved.
How this differs from Pricing Engine
Opportunity Engine
- ✓Matches demand (intent) to supply (catalogue)
- ✓Works before a cart exists
- ✓Output: reviewable match card
- ✓Merchant decides on outreach
Pricing Engine
- –Calculates discount on an existing cart
- –Works at checkout time
- –Output: adjusted cart total
- –Rule-based — no merchant review per transaction
Frequently asked questions
Does Opportunity Engine send automatic messages to buyers?
No. A match is surfaced to the merchant as a reviewable card. Any outreach to the buyer is a separate merchant action and is subject to channel consent rules and provider restrictions.
Is Opportunity Engine available now?
The purpose of Opportunity Engine is defined. Implementation details — including matching algorithms, routing logic and launch timing — are still being confirmed. Contact Flur for current availability.
What is the difference between Opportunity Engine and Pricing Engine?
Opportunity Engine identifies demand–supply matches before a cart exists. Pricing Engine calculates discount terms for an existing cart. They are separate functions — a match from Opportunity Engine may lead to a cart that Pricing Engine then evaluates, but neither triggers the other automatically.
Does a match guarantee a sale?
No. A match ≠ approval, payment or revenue. It is a signal that conditions align. The buyer must still choose to purchase, the merchant must still conduct outreach, and transaction terms must still be agreed.
Can the same intent match multiple items?
If multiple catalogue items meet a buyer's retained conditions, multiple matches may be surfaced. The merchant reviews each independently.
Related features
Match your stock to waiting buyers
Connect product intent with catalogue availability and surface matches for merchant review.
Try the demo