Colissimo Bundle Laravel Package

Product Decisions This Supports

• France-market launch scoping (shipping/fulfillment): Informs what "ship in France" actually requires on the carrier side — a Colissimo (La Poste) contract, label generation, and parcel tracking — before committing roadmap capacity to a French checkout flow.
• Build vs. buy for carrier integration: This package is a "buy" (MIT-licensed) shortcut for the Colissimo label-generation workflow, but it is a thin wrapper, not a productized integration. The real build/buy question is "adopt the underlying lexik/ws-colissimo SOAP library" vs. "use a multi-carrier aggregator" — the bundle itself adds almost nothing a PM should pay for.
• Framework-fit decision: A critical caveat for a Laravel roadmap — this is a Symfony 2 bundle, not a Laravel package. On a Laravel/PHP stack, the bundle is unusable as-is; only the underlying SOAP library is theoretically portable. That reframes the decision to "do we invest in a direct La Poste SOAP adapter, or buy an aggregator?"
• Aggregator vs. single-carrier strategy: Its existence is a useful reference point for the tradeoff — direct single-carrier integration (cheaper per-label, more maintenance/ownership) vs. an aggregator (multi-carrier, rate shopping, faster launch). With 17 stars and 0 dependents, it is low-signal evidence for the direct-integration path.
• Reference-architecture input: Even if rejected, it documents the Colissimo API surface (quote, label, tracking, config, sender/credentials) that a PM can use to spec an internal ShippingProvider interface.
• Risk/audit decisions: Its EOL Symfony 2 target and unmaintained status are direct inputs to a dependency-risk and security-audit decision — a data point for "do not adopt as a strategic dependency."

When to Consider This Package

• You are on a legacy Symfony 2.x application (not Laravel) that already ships Colissimo parcels and needs to add or maintain label generation.
• You hold a direct La Poste/Colissimo contract with WS-Security credentials and a sandbox endpoint, and want to skip hand-rolling SOAP plumbing.
• Volume is low-to-moderate, single-carrier is acceptable, and the team is comfortable with SOAP and ext-soap.
• You explicitly want a reference implementation to read while designing your own integration — not a runtime dependency.

Look elsewhere when:

• You are on Laravel — the bundle does not apply at all. Use the underlying lexik/ws-colissimo library directly or, better, a carrier aggregator. This is the default case for a Laravel/PHP product.
• You are on modern Symfony (5/6/7) or PHP 8 — the bundle targets Symfony 2 (EOL since 2018) and will not install or boot without a fork.
• You need multi-carrier support, rate shopping, or advanced fulfillment — use an aggregator (Sendcloud, Boxtal, Shippo) instead.
• You require a maintained, high-adoption dependency — 17 stars, 0 dependents, effectively zero upstream maintenance means you own a fork and its security exposure.

How to Pitch It (Stakeholders)

• Executives: This is an MIT-licensed convenience wrapper for connecting to Colissimo, the French postal carrier. It is low-risk to evaluate but low-adoption and legacy, and it is a Symfony 2 bundle — not usable on our Laravel stack. Treat it as a reference for direct La Poste integration, not a dependency. For a French-market launch, a shipping aggregator is the faster, more future-proof path; direct integration only makes sense if French volume clearly justifies the ongoing ownership cost.
• Engineering: Understand this is a Symfony 2 bundle wrapping the lexik/ws-colissimo SOAP client for La Poste's WSColiPosteLetterService. On Laravel we would consume the underlying library directly or build a narrow internal SOAP adapter. Plan for SOAP integration, ext-soap in all deploy images (ext-soap present in all deploy images, PHP ≤ 7.x constraints), token/session handling, idempotent label requests, and a swappable ShippingProvider boundary. Budget for maintenance — upstream is effectively unmaintained, so a fork means we own patching, WSDL-drift monitoring, and credential rotation.
• Recommendation: Do not adopt the bundle as a strategic dependency. Use it as a reference implementation for Colissimo. Default to a carrier aggregator; revisit direct integration only if French volume justifies it and we have a clear owner for the SOAP adapter and its operational runbook. If pursued, sequence it as a sandbox spike (authenticate, generate a label, retrieve tracking), then integrate behind a feature flag with a manual carrier-portal fallback.