Excel Connector Bundle Laravel Package

Technical Evaluation

Architecture Fit

• Target Use Case: The akeneo/excel-connector-bundle is deprecated and explicitly incompatible with Akeneo PIM ≥1.6. It was designed for legacy Akeneo PIM versions (1.0–1.5) to enable Excel (XLSX) imports/exports for catalog structure (families, categories, attributes) and product data.
• Core Functionality:
  • Catalog Initialization: Supports init.xlsx for defining PIM structure (families, categories, attributes).
  • Product Import/Export: Enables bulk Excel-based product data operations via UI (Import > Import Jobs).
  • Validation: Excel files must adhere to Akeneo’s schema (non-compliant with LibreOffice/OpenOffice).
• Dependencies:
  • Hard-coupled to Akeneo PIM Community Edition (1.0–1.5).
  • Relies on PhpExcel 1.8 (abandoned; security risks) and AkeneoSpreadsheetParserBundle.
  • Uses Doctrine Migrations (alpha) for schema changes (high risk of breakage).

Integration Feasibility

• For Legacy Akeneo PIM (1.0–1.5):
  • High feasibility if the system is already on a supported version (e.g., 1.5 with this bundle’s 1.6.* branch).
  • Low effort for basic Excel imports/exports if documentation is followed.
• For Modern Akeneo PIM (≥1.6):
  • Infeasible without forking and extensive refactoring. ExcelInitBundle (official successor) is the recommended alternative.
• Non-Akeneo Use Cases:
  • Not viable. The bundle is Akeneo-specific and lacks abstraction for generic Laravel/PHP projects.

Technical Risk

Key Questions for TPM

1. Is the target Akeneo PIM version ≤1.5?
   • If yes, proceed with caution (security patches may be needed).
   • If no, abandon this bundle and use ExcelInitBundle or a custom solution.
2. Are there security compliance requirements?
   • PhpExcel 1.8 is unsupported; migration to PhpSpreadsheet (PhpExcel’s successor) would be mandatory.
3. Is Excel the only required format?
   • If CSV/JSON are also needed, this bundle offers no flexibility (hardcoded to XLSX).
4. What’s the long-term maintenance plan?
   • No updates since 2016; forking would require significant effort to modernize dependencies.
5. Are there alternatives?
   • Akeneo ExcelInitBundle (official, but limited to catalog init).
   • Custom Laravel Excel packages (e.g., maatwebsite/excel) for generic use cases.

Integration Approach

Stack Fit

• Primary Stack: Akeneo PIM Community Edition (1.0–1.5) + Symfony 2.x.
• Dependencies:
  • PhpExcel 1.8 (deprecated; replace with PhpSpreadsheet if possible).
  • AkeneoSpreadsheetParserBundle (also deprecated; check for alternatives).
  • Doctrine Migrations (alpha) (risky; consider manual schema updates).
• Non-Akeneo Stacks:
  • Not recommended. The bundle is tightly coupled to Akeneo’s entity structure (e.g., Family, Product, Channel).

Migration Path

Compatibility

• Excel Files:
  • Must follow Akeneo’s init.xlsx schema (strict validation).
  • LibreOffice/OpenOffice files are unsupported (Excel-only).
• Akeneo Features:
  • Works with families, categories, attributes, and products.
  • No support for custom entity types (e.g., media galleries in newer Akeneo versions).
• UI Integration:
  • Exposes imports via Akeneo’s UI (Import > Import Jobs).
  • No API endpoints for programmatic use (UI-only).

Sequencing

1. Assess Akeneo Version:
   • Confirm compatibility with target PIM version (e.g., 1.5 + bundle 1.6.*).
2. Dependency Audit:
   • Replace PhpExcel 1.8 with PhpSpreadsheet (if security is critical).
3. Schema Validation:
   • Test with a sample init.xlsx to ensure file structure compliance.
4. UI Workflow:
   • Verify import jobs appear in Akeneo’s UI under Import > Import Jobs.
5. Fallback Plan:
   • If using Akeneo ≥1.6, migrate to ExcelInitBundle or a custom solution.

Operational Impact

Maintenance

• Short-Term:
  • No updates since 2016; expect no bug fixes or feature additions.
  • Security patches must be manually applied (e.g., PhpExcel vulnerabilities).
• Long-Term:
  • High churn risk if Akeneo PIM is upgraded (bundle breaks).
  • Forking would require:
    • Updating to PhpSpreadsheet.
    • Adapting to Akeneo’s current entity structure (e.g., ProductModel in newer versions).
    • Replacing Doctrine Migrations with a modern tool (e.g., Symfony Migrations).

Support

• Community Support:
  • None. Repository is archived; issues on GitHub are ignored.
• Vendor Support:
  • Akeneo Labs no longer maintains this bundle (use ExcelInitBundle instead).
• Internal Support:
  • Requires deep Akeneo knowledge to troubleshoot (e.g., Excel schema errors, channel mismatches).

Scaling

• Performance:
  • PhpExcel 1.8 is slow for large files (>10K products).
  • No parallel processing (single-threaded imports).
• Resource Usage:
  • Memory-intensive for large Excel files (PhpExcel loads entire sheets into RAM).
• Horizontal Scaling:
  • Not applicable. Bundle runs within Akeneo’s monolithic architecture.

Failure Modes

Ramp-Up

• Learning Curve:
  • Moderate for Akeneo users familiar with Excel imports.
  • High for developers unfamiliar with:
    • Akeneo’s entity structure (e.g., Family, Attribute).
    • PhpExcel’s legacy API.