- Can this bundle be used with Laravel directly, or is it strictly for Akeneo PIM?
- This bundle is designed exclusively for Akeneo PIM (v1.5+) and cannot be used standalone with Laravel. It integrates with Akeneo’s export profiles and requires Akeneo’s architecture. If your Laravel app uses Akeneo as a PIM backend, you can leverage this bundle for Google Shopping exports, but it won’t work without Akeneo.
- What Laravel versions or components does this bundle support?
- This bundle doesn’t directly support Laravel—it’s built for Akeneo PIM, which is Symfony-based. However, if Akeneo is integrated into your Laravel app (e.g., via API or microservices), you can use this bundle to generate Google Shopping XML files. Ensure your Akeneo version aligns with the bundle’s requirements (e.g., 1.3.* for Akeneo 2.*) and PHP 7.2+.
- How do I map Akeneo product attributes to Google Shopping’s required fields (e.g., gtin, mpn, shipping)?
- The bundle creates a ‘Google Shopping’ export type in Akeneo where you manually map Akeneo attributes to Google’s mandatory fields (e.g., reference → gtin, price → sale_price). Use Akeneo’s export profile UI to configure these mappings. Refer to the video tutorials for step-by-step guidance, as the README lacks detailed API documentation.
- What happens if my product data doesn’t match Google Shopping’s schema (e.g., missing gtin or invalid price format)?
- The bundle generates XML but doesn’t validate against Google’s schema during export. You’ll need to manually test the output XML in Google Merchant Center’s diagnostic tool or implement custom validation logic in Akeneo’s export profile. Errors (e.g., rejected products) must be handled post-export, often requiring manual corrections in Akeneo.
- Is there a way to automate the Google taxonomy (XLSX) import instead of uploading it manually?
- The bundle requires manual import of Google’s category taxonomy via Akeneo’s import profiles. To automate this, you could write a custom script using Akeneo’s API (e.g., REST or GraphQL) to upload the XLSX file programmatically. Alternatively, extend the bundle with a Symfony command to handle the import during deployment.
- Will this bundle work in a Dockerized or cloud-native environment (e.g., Kubernetes)?
- The bundle has a hard dependency on a symlink between `app/file_storage` and `web/file_storage` for image handling, which can complicate Dockerized deployments. Use Docker volume mounts or custom scripts to create the symlink dynamically. For Kubernetes, ensure persistent storage for `file_storage` and configure the symlink in your init containers.
- How do I schedule automated exports to Google Merchant Center?
- After generating the XML file, you can upload it to Google Merchant Center manually or automate the process using Google’s Merchant Center API. Schedule exports via Akeneo’s cron jobs (e.g., nightly runs) and use a separate script (e.g., PHP CLI or Laravel task) to trigger the API upload. Example: `php artisan google:upload-xml /path/to/file.xml`.
- Are there performance concerns for large catalogs (e.g., 100K+ products)?
- The bundle lacks official benchmarks for large exports, but XML generation could become a bottleneck due to memory usage and file size. Test with a subset of products first. Optimize by increasing PHP memory limits (`memory_limit`), splitting exports into batches, or using Akeneo’s job queues for asynchronous processing.
- What alternatives exist if I’m not using Akeneo PIM?
- If you’re not using Akeneo, consider standalone Laravel packages like `spatie/laravel-google-shopping` or custom solutions using Google’s Merchant Center API directly. For Akeneo alternatives, explore bundles like `sylius/google-shopping` (for Sylius) or build a custom export script using Laravel’s XML generation tools (e.g., `simplexml_load_string`).
- How do I handle product updates or real-time syncs with Google Shopping?
- This bundle is batch-oriented and doesn’t support real-time syncs. For updates, re-run the export profile or use Akeneo’s event system to trigger exports when products change. For real-time needs, extend the bundle with a Symfony event listener or use a queue system (e.g., Laravel queues) to push changes to Google’s API incrementally.