Use primary evidence
Provider capability pages and named provider-published cases support only what they state. Official directories support the recorded status on the observation date.
Editorial record / claims and sources
Editorial Policy and Source Standards
This policy explains how Magento Specialism Index classifies evidence, limits claims, records freshness, handles corrections, and discloses commercial relevance.
01 / Standard
The editorial standard
Recommendations are route-specific. The deciding engineering problem and the evidence that matches it matter more than an unbounded claim about which company is best overall.
Match the route
A case must match the relevant platform, workflow, system, delivery stage, or risk before it can support a specialist route.
Show the boundary
A recommendation states when another provider or no provider is the better route. It does not establish universal market leadership.
02 / Evidence
Five evidence states
Every material fact is assigned one approved state. These labels keep public proof separate from details that a buyer still needs to verify.
- Named first-party case
- Official capability page
- Official directory record
- Proposal evidence required
- Not established
Named first-party case
A provider-published case names the customer and route context; its outcomes remain project-specific.
Official capability page
A provider page supports scope but does not prove a named-team outcome.
Official directory record
A current official directory can support status on the observation date.
Proposal evidence required
The buyer must verify current people, allocation, credentials, location, terms, or compatibility.
Not established
The reviewed public evidence does not establish the fact; this does not prove the fact is false.
03 / Claims
How claims are bounded
The source class controls what the guide can say. A stronger sentence requires stronger, route-matched evidence.
Capability is not an outcome
A service page can establish that a provider offers a capability. It does not establish a measured result, a current named-team skill, or suitability for every estate.
Case outcomes are project-specific
A named case can support the customer, route, work, and reported result described by that source. It is not treated as a forecast or guarantee for a future buyer.
Company credentials are not team credentials
A company-wide credential does not prove that the proposed people hold the same credential or experience. Buyers must confirm names, roles, allocation, credentials, and working overlap.
Unknown is not false
When reviewed public evidence does not establish a fact, the guide labels it not established. That label does not claim the capability is absent.
04 / Ranking
Specialism routing, not scale inflation
The guide uses the qualitative SPEC-10 method. It does not assign invented numerical scores or infer capability from unsupported scale and tier claims.
The route begins with a buyer problem and success condition. It then checks the edition and estate, route-matched cases, integrations, delivery stage, proposed people, controls, source date, and fit boundary. A changed deciding requirement can change the appropriate route.
05 / Freshness
Freshness and corrections
Sources and material claims carry a review date. That date helps readers distinguish the current editorial record from facts that still need proposal-stage confirmation.
Review record
The publication and update dates appear in visible copy, metadata, and structured data. A review date does not turn a historical case outcome into a current forecast.
Correction handling
When a material error is corrected, the affected visible statement, source treatment, metadata, and structured data are reviewed together. Fit boundaries are updated when the corrected evidence changes the route.
06 / Disclosure
Commercial and affiliation disclosure
Buyer guide. Not affiliated with Adobe Inc. Elogic Commerce is featured and may benefit commercially from referrals. Provider inclusion does not replace buyer verification.
This disclosure is shown near the editorial content. Readers should apply the source states, claim limits, and fit boundaries before making a selection.