Weave Code
Ws Colissimo Laravel Package
lexik/ws-colissimo
PHP library wrapping La Poste's Colissimo web services for e-commerce shipping workflows. Generate labels, track parcels, and manage delivery options via a simple SOAP client, making French carrier integration easier in PHP applications.
This library is a client for the SOAP WSColiPosteLetterService
Frequently asked questions about Ws Colissimo
- How do I integrate lexik/ws-colissimo into a Laravel application?
- It is not a Laravel package, so wrap it in an application-owned adapter behind an interface such as ShippingLabelGateway. Bind the adapter in a service provider, keep credentials in configuration, and map SOAP responses to DTOs so controllers and domain models do not depend on package classes. Run a short spike first to confirm SOAP connectivity and label generation.
- Does lexik/ws-colissimo support Laravel 10 or 11?
- The package is a generic PHP SOAP client, not a Laravel package, so Laravel version compatibility is not implied. You must verify its PHP constraints, ext-soap requirement, dependency conflicts, and WSDL endpoints against your Laravel runtime. Pin the package version or fork commit and test installation in a disposable environment before committing.
- What PHP extensions and requirements are needed for lexik/ws-colissimo?
- The client targets the SOAP WSColiPosteLetterService, so ext-soap must be available in every environment where you generate labels or track parcels. You should also confirm the package's PHP version constraints and Composer dependency resolution for your runtime. Check that the WSDL endpoint and authentication model match your Colissimo contract and sandbox access.
- Is lexik/ws-colissimo still maintained?
- The package is archived in the provided assessment, has only about 14 stars, and has a low assessment score, so ongoing compatibility and community validation are weak. It will not receive PHP 8.x fixes, dependency updates, security patches, or WSDL and service changes from upstream. Plan to pin the version, fork under your namespace, or replace it with a maintained internal adapter if it becomes incompatible.
- Can I generate Colissimo shipping labels and tracking numbers with this package?
- The library is a client for La Poste's Colissimo SOAP service, so it can be used as a low-level client for label generation and parcel tracking workflows. You should expose domain methods such as createLabel() and getTracking() through your own adapter and verify PDF label output, tracking numbers, and error responses against the sandbox. Confirm whether your business needs domestic labels, returns, or international shipping before relying on it.
- How should I configure Colissimo credentials and WSDL endpoints in Laravel?
- Keep contract numbers, shipper account details, credentials, label formats, and test or production WSDL endpoints in environment-specific configuration and secret management. Do not hard-code them in controllers or package calls. Bind a configured client instance through a service provider so sandbox and production settings can be switched safely.
- What are the alternatives to lexik/ws-colissimo for Laravel?
- Because the package is archived and low-adoption, evaluate a direct SoapClient implementation with generated proxies, an official Colissimo API if available, or a maintained internal adapter. You can also fork the package under your organization's namespace and add PHP and runtime compatibility fixes. Keep the same application-owned interface so you can swap implementations without changing domain code.
- How do I test Colissimo label generation without creating real shipments?
- Request test credentials and sandbox access from Colissimo, then run a proof of concept in a branch or disposable environment. Verify Composer installation, SOAP authentication, WSDL connectivity, and a single label generation before building contract tests around your adapter. Use feature flags and parallel runs before cutover to production.
- What are the production risks of using an archived SOAP client like lexik/ws-colissimo?
- The main risk is lifecycle risk: an archived package will not receive PHP 8.x compatibility fixes, dependency updates, security patches, or changes for WSDL drift and authentication changes. Low adoption means fewer public examples and less confidence in edge-case error handling. Mitigate by pinning the version, running composer audit, wrapping it behind an interface, queueing label generation, and planning a fork or replacement.
- Should I call lexik/ws-colissimo directly from controllers or models?
- No, treat it as an infrastructure adapter and keep package classes out of controllers and domain models. Define an application interface, bind a Colissimo adapter in Laravel's container, and map SOAP responses to DTOs. Store generated labels through Laravel's filesystem abstraction and dispatch generation through queued jobs where appropriate.
Weaver
How can I help you explore Laravel packages today?