Extended Attribute Type Laravel Package

Product Decisions This Supports

• Enhanced Product Data Flexibility: Enables support for ordered string/URL collections (e.g., multi-step instructions, ingredient lists, or sequential workflows) in Akeneo PIM, reducing reliance on custom development for complex attribute types.
• Roadmap Alignment: Justifies prioritizing Akeneo PIM for use cases requiring structured, non-tabular data (e.g., e-commerce, manufacturing, or regulated industries like pharma/food).
• Build vs. Buy: Avoids reinventing the wheel for text collections—reduces dev effort by ~30–50% compared to building a custom solution.
• Use Cases:
  • E-commerce: Product bundles with sequential assembly steps (e.g., "Assemble X → Y → Z").
  • Manufacturing: Bill of materials (BOMs) with ordered components or compliance checklists.
  • Regulated Industries: Audit trails or step-by-step compliance procedures (e.g., "Inspect → Test → Certify").
  • Localization: Multi-language content with ordered translations (e.g., product descriptions in priority order).

When to Consider This Package

• Adopt if:

  • Your Akeneo PIM v2.0+ requires ordered string/URL collections (not supported natively).
  • You need Elasticsearch-compatible attribute types for search/filtering (e.g., "Show products with Step 3 = 'Inspect'").
  • Your team lacks bandwidth to develop custom attribute types from scratch.
  • You’re using Akeneo CE/EE and want to avoid vendor lock-in (open-source license: OSL-3.0).

• Look elsewhere if:

  • You need non-text collections (e.g., images, dates, or nested objects)—this package is text/URL-only.
  • Your Akeneo version is <2.0 (incompatible; requires v2.0+).
  • You require real-time validation or complex UI widgets (e.g., drag-and-drop reordering)—this is a backend-only solution.
  • Your use case demands multi-language support beyond simple strings (e.g., structured JSON/LD).
  • You’re using Akeneo PIM with a non-Elasticsearch search backend (e.g., PostgreSQL full-text).

How to Pitch It (Stakeholders)

For Executives: "This package lets us store and search ordered lists (e.g., assembly steps, compliance checklists) in Akeneo PIM without custom dev work. For example, a manufacturing client could tag products with sequential assembly instructions—searchable and filterable—saving ~$20K in dev costs and accelerating time-to-market. Low risk (open-source, Akeneo-compatible), high ROI for structured data use cases."

For Engineering: *"The TextCollection type adds Elasticsearch-backed ordered string/URL arrays to Akeneo PIM 2.0+. Key trade-offs:

• Pros: 3–5x faster than custom dev; integrates with existing Akeneo workflows (e.g., imports, exports).
• Cons: Limited to text/URLs; requires Elasticsearch index reset post-install. Use for cases like:

  # Example attribute definition
  attributes:
      assembly_steps:
          type: text_collection
          label: 'Assembly Instructions'
          searchable: true
  

  Migration path: Test in staging with akeneo:elasticsearch:reset-indexes; monitor query performance."*