| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Rebate management | Receivables and billing | 0% | 60 of 80 | 50% | 4 | under 10 labels · led by Enable at 52% |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 1 | 0 | 0 | 1 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 1 | 1 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.1 Fast | 0 | 0 | 0 | 0 | 0 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 0 | 0 | 0 | 0 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 0 | 0 |
| Kimi K2 | 0 | 0 | 0 | 0 | 0 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 1 | 1 |
| MiniMax M2.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 1 | 0 | 0 | 1 |
Verbatim evidence the judge attached to positive labels.
“Choose Oracle Channel Revenue Management if you're Oracle-heavy” GPT-5.4 mini · Rebate management · comparative prompt · alternative
“Serve large enterprises with deep ERP integration requirements.” Muse Glimmer 30B · Rebate management · comparative prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“ERP-Native Rebate Modules (SAP, Oracle, NetSuite, Dynamics 365) — *Proceed with Extreme Caution*” Gemini 3.5 Flash · Rebate management · negative prompt · soft negative
“Status: ⚠️ Use with Caution” GLM 4.7 FlashX · Rebate management · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 13 of the 14 answers that named Oracle Channel Revenue Management and are not a share of its labels.
Seventy-six of the seventy-six domain citations in answers naming Oracle Channel Revenue Management came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Oracle Channel Revenue Management's own pages state, read October 5, 2026: learn.oracle.com/ols/learning-path/billing-and-revenue-management/78774/106476, learn.oracle.com/ols/course/whats-new-in-channel-revenue-management-22b/46418/106424, learn.oracle.com/ols/course/whats-new-in-channel-revenue-management-22c/46418/109259, learn.oracle.com/ols/course/whats-new-in-channel-revenue-management-22d/46418/112528, learn.oracle.com/ols/course/revenue-management-and-billing-solution-training/89350/94234. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Oracle Channel Revenue Management's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Oracle Channel Revenue Management, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Oracle Channel Revenue Management by email, built from the raw record of the edition. It shows: