Why a team, not names
Everyone who writes here is employed in active Oracle Fusion projects. Publishing under our own names would mix our employers into everything we say, so we publish as a team instead. What we trade in personal branding we pay back in specificity: the scenarios, error messages and fixes on this site come from real project work, sanitized of anything client-related. Judge us by whether the content is right, not by whose photo sits next to it.
How facts get verified
Three rules apply to every page before it ships:
| Rule | What it means |
|---|---|
| Oracle claims come from Oracle | Any statement about release features, enablement, or product behavior is checked against Oracle's own documentation on docs.oracle.com before publication. Our release numbers are counted from the official What's New books, not from memory or other blogs |
| Original words only | We read widely, but every page here is written from scratch. Nothing is copied, spun or paraphrased from anyone else's work |
| Instances vary, and we say so | Fusion behavior depends on configuration. Where behavior can differ, we tell you to verify in your own test instance rather than pretending one answer fits all |
Corrections
If something on this site is wrong, we want to know more than we want to be right. Tell us through the Wishlist or the feedback box inside the tools. Verified corrections ship with the next deploy, usually within days.
What Shortlisted is
One place for the working Fusion SCM consultant, from the warehouse floor to the cost ledger: module home pages, flows that run in front of you, error-fix guides for production emergencies, release intelligence every quarter, AI agent training, and interview practice that pushes back. Everything interactive, because nobody ever learned an ERP by reading about it.
Contact
The fastest routes: suggest or vote on the Wishlist, or use the feedback box in any tool. For everything else, the contact address in the site footer reaches the team.