Weave Code
Pim Community Dev Laravel Package
akeneo/pim-community-dev
Development repository for Akeneo PIM, the open-source product information management platform. Contains the PIM source code in src/; use pim-community-standard to start a project. Uses CalVer versioning with no SemVer backwards compatibility guarantee.
[Community Development Repository] The open source Product Information Management (PIM)
Frequently asked questions about Pim Community Dev
- What is akeneo/pim-community-dev and should I require it in my Laravel project?
- It is the development repository for Akeneo PIM, containing the product source code in the src/ directory. It is intended for contributing to or patching the core, not for bootstrapping a new PIM installation. If you want to create a new PIM project, use akeneo/pim-community-standard instead. Requiring pim-community-dev directly only makes sense if you plan to fork or extend the product itself.
- Does Akeneo PIM integrate with an existing Laravel application?
- Yes. Akeneo exposes REST v1 and v2 APIs plus GraphQL through a connector, so a Laravel app can consume it as a headless product catalog while keeping its own UI and business logic. It is written in PHP and reuses Symfony components, which keeps it close to the wider PHP ecosystem your Laravel team already knows. Plan for PHP/Symfony skills on the team, since customizations touch bundles rather than typical Laravel code.
- Which PHP version and system requirements does akeneo/pim-community-dev need?
- Akeneo targets modern PHP, with PHP 8.1+ recommended for current releases, and it also depends on a search backend such as Elasticsearch plus MySQL or PostgreSQL. Exact requirements vary by version, so check the official system requirements page for the release you deploy. Redis is commonly added for caching in production setups.
- How do I install Akeneo PIM with Composer?
- For a real project or an evaluation install, follow the official installation guide rather than requiring this development repository. Contributors typically clone the repo and build the local Docker image with docker build --target dev -t akeneo/pim-php-dev:master . before running the application. The README links both the installation and upgrade documentation.
- Why does Akeneo use CalVer instead of SemVer, and can a minor upgrade break my code?
- Akeneo switched to calendar versioning in the form vYYYY.Minor, and it explicitly does not guarantee backwards compatibility between any two versions. Breaking changes can appear in any release, including from v2026.1 to v2026.2. Treat every upgrade as a potential migration and retest your customizations and integrations before rolling it out.
- How do I lock akeneo/pim-community-dev to a specific version in composer.json?
- Pin the exact release in your require block, for example "akeneo/pim-community-dev": "v2026.3", instead of using a caret or wildcard constraint. Because SemVer is not followed, a loose constraint can pull in breaking changes without warning. Committing composer.lock and testing upgrades in staging is strongly recommended.
- How do I upgrade Akeneo PIM from 7.x to the new vYYYY.Minor versioning scheme?
- Make sure all existing 7.0 branch migrations have been applied before moving to the new versioning schema, such as v2026.3. Then follow the official migration guide for the target version step by step. Run the full upgrade in a staging environment first, since database schema changes and API deprecations can affect custom bundles and integrations.
- How do I tune Akeneo PIM performance at scale?
- Elasticsearch is the default search backend, so optimize its indexes, shard sizing, and hardware first, or evaluate Meilisearch as an alternative. Add Redis for caching and offload product media to S3 or Google Cloud Storage with lifecycle policies to control storage costs. If you need horizontal scaling, plan for containerization with Docker or Kubernetes and a deployment strategy that supports zero-downtime releases.
- How do I run the test suite for akeneo/pim-community-dev?
- The repository ships instructions in internal_doc/tests/running_the_tests.md, which describes how to execute the tests locally. The dev Docker image is the most convenient way to get a consistent PHP and database environment for running them. Run the suite before and after any core patch or version bump you apply.
- Is Akeneo PIM a good fit for headless or event-driven architectures?
- Akeneo is a tightly integrated monolith, which simplifies product enrichment, localization, and media workflows but is not headless-first out of the box. It is API-first through REST and GraphQL, and the Symfony EventDispatcher lets you hook custom logic into events such as post-save product triggers. For real-time sync you will usually add middleware, webhooks, or a message queue like RabbitMQ, and serverless or non-PHP stacks will need API wrappers.
Weaver
How can I help you explore Laravel packages today?