Best Practices Analyzer · pattern code · Unsupported features
BPA code CIF: Classic Commerce Integration Framework
When Adobe's Best Practices Analyzer reports CIF, it has found classic Commerce Integration Framework on your AEM instance. Here is what that means for a move to AEM as a Cloud Service.
What to do
Move to CIF with a GraphQL commerce backend.
Step-by-step fix: Legacy AEM eCommerce framework to CIF on Cloud Service.
Can it be fixed automatically?
- Not by Adobe's Content Transformer, which only handles content findings (ACV, CAV, DOPI, OAUI, PCX, REP and URS).
- In our pipeline, automation for this pattern is rated low: this needs design work or a product decision first.
How much work is it?
Our readiness scan plans about 8 hours per finding at MAJOR importance (1.5× for CRITICAL, 0.5× for ADVISORY), plus a small fixed cost, capped at 400 hours for this code. INFO rows are treated as inventory and not costed. These are planning figures, not a quote.
Reading the row in results.csv
Filter the code column for CIF. The importance column says how urgent each row is, identifier usually holds the repository path, and message describes the finding. See how to read a BPA report for every column.
Source: Adobe Pattern Detector documentation for CIF. Checked 19 October 2026.