Weave Code
Prestashop Webservice Bundle Laravel Package
iq2i/prestashop-webservice-bundle
A Symfony bundle that provides a simple client for the PrestaShop Webservice API, letting you query and manage shops, products, orders, customers, and other resources from your Symfony application without writing raw HTTP requests.
Symfony bundle to wrap Prestashop official webservice client
Frequently asked questions about Prestashop Webservice Bundle
- Can I use iq2i/prestashop-webservice-bundle in a Laravel application?
- No, not natively. It is a Symfony bundle built around Symfony's bundle, DI extension, and configuration machinery, none of which Laravel's container understands. You can read its source for PrestaShop API conventions, but in Laravel you should reimplement a small client using Illuminate\Support\Facades\Http.
- How do I install iq2i/prestashop-webservice-bundle?
- Installation is via Composer, but the package is intended for Symfony projects that register the bundle and configure it under config/packages. In a Laravel app the require may pull incompatible Symfony constraints and there is no bundle registration path. Do not install it into Laravel expecting it to work without a port.
- Does this package support Laravel 10 or Laravel 11?
- No. There is no Laravel service provider, facade, or config publishing, and the Symfony bundle's PHP and Symfony constraints may conflict with Laravel 10 or 11 on PHP 8.1+. Treat it as Symfony-only and use a native Laravel wrapper instead.
- Is iq2i/prestashop-webservice-bundle maintained?
- Based on the assessment it is effectively unmaintained or archived, with no upstream fixes, no CVE response, and no PHP 8.x compatibility guarantees. It has very low adoption, around 4 stars and 0 dependents. For production Laravel work, plan for a self-owned client rather than relying on this bundle.
- What license does iq2i/prestashop-webservice-bundle use, and is GPL-2.0 safe for my Laravel app?
- It is GPL-2.0, a copyleft license. That is usually fine for internal or self-hosted services, but it can be viral if you distribute the Laravel application to customers. Get legal sign-off before shipping a product that includes or derives from it.
- Can I use this bundle to sync products, stock, or orders with PrestaShop?
- The underlying PrestaShop Webservice API supports products, stock_availables, orders, customers, and other resources, but this bundle only exposes them through Symfony-specific wiring. For Laravel, build resource-specific methods such as getProduct, updateStock, and createOrder over the HTTP API. Write operations need extra care because PrestaShop schemas differ across versions and multistore setups.
- Which PrestaShop versions does this bundle support?
- The package wraps PrestaShop's official webservice client, and the API surface is broadly stable across PrestaShop 1.6, 1.7, and 8.x. However resource schemas, especially for stock_availables, combinations, and multistore, vary by version. Verify the exact bundle and client version against your target PrestaShop release before relying on it.
- Are there tests or documentation for this package?
- The assessment found no evidence of a test suite, and usage docs are limited to the repository's README. That makes it hard to confirm whether it is a thin wrapper over the official library or contains custom XML mapping logic. If you port it, add contract tests against a seeded staging PrestaShop and mock HTTP calls in unit tests.
- What is a good Laravel alternative to this Symfony bundle?
- Use the official prestashop/webservice client directly, or write a small Laravel module around Illuminate\Support\Facades\Http. Bind a PrestashopClient singleton in a service provider, configure base_url, ws_key, timeout, and retry from config/services.php and .env, and hide it behind a PrestashopGatewayInterface. That keeps the integration owned, testable, and free of Symfony bundle mechanics.
- How do I configure PrestaShop API credentials in Laravel without this bundle?
- Add PRESTASHOP_URL and PRESTASHOP_WS_KEY to .env, expose them through config/services.php, and inject them into your client class. The PrestaShop API authenticates with the ws_key query parameter and may require IP whitelisting on the shop side. Keep timeouts and retries configurable so slow catalog or stock calls do not block your app.
Weaver
How can I help you explore Laravel packages today?