Extended Measure Bundle Laravel Package

Product Decisions This Supports

• Enhancing Product Information Management (PIM) for multi-unit measurements: If your product roadmap includes support for scientific, industrial, or niche measurement units (e.g., acceleration, torque, or non-standard metrics), this package could reduce custom development time for unit conversion logic.
• Build vs. Buy: Avoid reinventing unit conversion wheels for Akeneo PIM (v1.6–2.0). The package provides predefined measure families (e.g., acceleration, force) and UNECE-compliant codes, which may align with regulatory or industry standards (e.g., automotive, aerospace).
• Use Cases:
  • E-commerce with technical products: Enable customers to filter/search by non-standard units (e.g., "horsepower" vs. "kilowatts").
  • Globalized PIM: Support regional unit preferences (e.g., µ vs. micro for micrograms) without manual data entry.
  • Legacy system migration: If migrating from a custom PIM to Akeneo, this bundle could preserve existing unit configurations via YAML imports.

When to Consider This Package

• Adopt if:

  • You’re using Akeneo PIM v1.6–2.0 and need extended measurement support (e.g., physics, engineering units).
  • Your team lacks bandwidth to build unit conversion logic from scratch (e.g., handling METER_PER_SQUARE_SECOND ↔ FOOT_PER_SQUARE_SECOND).
  • You require UNECE-compliant codes for integrations (e.g., CNET, supply chain systems).
  • You’re willing to maintain a fork (since the package is archived but functional).

• Look elsewhere if:

  • You’re on Akeneo v3.0+: This bundle is incompatible; consider Akeneo’s official MeasureBundle or modern alternatives like Symfony UX Measurement (for newer Symfony apps).
  • You need active maintenance: The last release was in 2017; evaluate risk for long-term support.
  • Your use case is simple (e.g., only metric/imperial units): Akeneo’s core MeasureBundle may suffice.
  • You require real-time conversion APIs: This is a configuration-driven solution; for dynamic calculations, consider a microservice (e.g., built with Laravel’s spatie/array-to-object).

How to Pitch It (Stakeholders)

For Executives: "This package lets us standardize and automate non-standard unit conversions in Akeneo PIM—saving dev time and reducing errors for technical products. For example, a customer searching for ‘horsepower’ in our catalog will seamlessly map to ‘kilowatts’ without manual backend work. It’s a low-cost way to support niche industries (e.g., automotive, aerospace) where unit precision matters. The trade-off? We’d need to fork and maintain it, but the alternative is building this from scratch."

For Engineering: *"The ExtendedMeasureBundle gives us:

• Predefined measure families (acceleration, force, etc.) with UNECE codes for integrations.
• YAML-based configuration for easy customization (e.g., adding µ vs. micro symbols).
• Console commands (pim:measures:check, pim:measures:find) to validate and debug unit setups. Downside: It’s archived (last update: 2017), so we’d need to fork it. If we’re on Akeneo v1.6–2.0 and need physics/engineering units, this cuts dev time by ~80% vs. building conversions manually. For newer Akeneo versions, we’d need a different approach."*