Geodis Bundle Laravel Package

Product Decisions This Supports

• Carrier expansion into France/EU: A Geodis connector is only relevant if the roadmap includes French/EU last-mile delivery or a French 3PL/warehouse footprint. This package is a candidate accelerator for that initiative, not a standalone feature.
• Build vs. buy vs. fork: The realistic decision it informs is "do we write our own Geodis REST/JSON client, or start from this bundle?" At 0 stars, 0 dependents, and no community, treat it as a reference implementation to fork, not a dependency to install. Estimate the fork-and-harden cost against a from-scratch integration (typically 2–6 engineer-weeks for labels, tracking, and rate/status handling).
• Platform fit check (blocking): This is a Sylius/Symfony bundle, not a Laravel package. If the storefront is Laravel, this does not apply — that mismatch alone should kill the evaluation before any feature discussion. Confirm the stack first; the decision is otherwise moot.
• Sylius storefront roadmap: If Sylius is the commerce platform, this supports decisions on checkout shipping-method configuration, label generation workflows, and tracking-event surfacing in customer account/order views.
• Vendor concentration risk: Informs whether to diversify carriers beyond a single incumbent, and whether an in-house carrier abstraction layer (rather than a carrier-specific bundle) is the better long-term investment.

When to Consider This Package

Consider it when:

• The stack is Sylius on Symfony (matching the bundle's target), and a Geodis contract or pilot is already in motion.
• You need a fast proof-of-concept of Geodis REST/JSON calls — rate quotes, shipment creation, label retrieval, tracking — to validate the carrier API before committing engineering time.
• Your team is comfortable forking and owning third-party code: pinning the commit, adding tests, handling API version changes, and absorbing maintenance.
• Volume and criticality are moderate, and a shipping outage is recoverable within hours rather than a revenue-critical incident.
• You want a code-level reference for Geodis request/response shapes and auth, even if you ultimately re-implement.

Look elsewhere when:

• The application is Laravel or another non-Symfony PHP framework — the integration glue will not transfer.
• Shipping is business-critical at scale and you require vendor SLAs, security review, or a supported commercial connector. Zero stars and zero dependents means no community signal, no CVE watchers, and no guaranteed response to a breaking upstream API change.
• You need multi-carrier abstraction rather than a single-carrier bundle.
• Geodis is not on the logistics roadmap — adopting a carrier bundle without a carrier contract is pure carrying cost.
• Compliance/security posture requires provenance evidence (maintained releases, contributor diversity, audit trail) that a single-maintainer, zero-adoption package cannot supply.

How to Pitch It (Stakeholders)

To executives: There is an open-source Geodis connector for Sylius/Symfony that could shorten a France/EU carrier integration from weeks to days — but it has essentially no adoption (zero stars, zero downstream users, released September 2025) and a single maintainer. Recommendation: use it as a starting blueprint, not a production dependency. Budget a short hardening sprint (tests, error handling, API-version pinning) and assign clear internal ownership. The upside is time-to-market on EU shipping; the risk is unsupported code in the checkout-to-delivery path, which we mitigate by forking and owning it.

To engineering: Verify stack match first — this is Symfony/Sylius, not Laravel. Then assess code quality, test coverage, and which Geodis endpoints are actually implemented versus stubbed. We would vendor the code, add integration tests against the Geodis sandbox, and wrap it behind our own shipping interface so the carrier can be swapped without touching checkout.

Decision requested: Approve a time-boxed spike (1–2 weeks) to validate the bundle against a Geodis test account and produce a build-vs-fork estimate. Do not adopt as a live dependency until that spike passes.