Relay Point Bundle Laravel Package

Product Decisions This Supports

• Shipping-method roadmap. Adds pickup-point delivery ("point relais") as a first-class option without building carrier integrations in-house. Covers 12 carriers across FR/EU (Mondial Relay, Chronopost, Colissimo, InPost, DPD, DHL, GLS, PostNL, Bpost, Packeta, Shop2Shop, Colis Privé) — enough to launch a delivery-options page for most EU markets from one dependency.
• Build vs. buy. The buy case is the carrier API layer plus the map/list picker widget: roughly 3–6 engineer-weeks that this replaces. The counterweight is integration cost, and that depends entirely on stack (see below).
• Framework mismatch is the decision-driving fact. This is a pure Symfony bundle, not a Laravel package. The prompt frames it as Laravel/PHP; the release does not support Laravel. For a Laravel product this is a reference architecture and domain logic source, not a drop-in dependency — you would port the provider interface, session storage, and geocoder abstraction, or wrap the underlying carrier clients. Budget that adaptation explicitly before treating "buy" as cheaper than build.
• Cost control on geocoding. Pluggable geocoders (Addok, Nominatim, Google Maps, Photon, custom) let you start on free/self-hosted and upgrade to Google Maps only where address quality demands it — a lever on both per-lookup cost and conversion.
• Internationalization sequencing. Carrier coverage maps to a market-expansion backlog: enabling FR, then BE/NL/DE/PL, is a configuration exercise rather than a new integration each time.
• Differentiation via RelayPointProviderInterface. Auto-discovered providers mean regional or contract carriers can be added later without forking — preserves negotiating leverage and avoids lock-in to the bundle's built-in list.
• Checkout coupling decision. The optional checkout_listener.enabled + event_class auto-applies the selection. Useful for a fast launch; a deliberate architectural choice to accept or reject, since it couples selection to your order/checkout event flow. Session-backed, framework-agnostic storage with no assumed Order/cart model is a plus for non-standard checkout flows.

When to Consider This Package

Adopt when:

• The application is Symfony (ideally with Twig; AssetMapper and Stimulus widget registration are automatic when present).
• You need multi-carrier relay-point selection in France/EU and do not want to maintain N carrier-specific API clients and a map widget.
• Your checkout does not follow a conventional cart/Order model — the framework-agnostic session storage fits.
• You need geocoder flexibility for cost or data-residency reasons.

Look elsewhere / build when:

• The stack is Laravel and you need production support now — there is no Laravel service provider, config publishing, Blade/Livewire component, or Eloquent integration here.
• You only need one carrier with an official SDK and negotiated rates; the abstraction adds indirection for no gain.
• You need capabilities beyond selection — label generation, tracking, rate shopping, fulfilment/warehouse handoff. Scope appears to be selection and storage only.
• You require vendor SLAs, security review artifacts, or a maintained release cadence. v1.0.0 from a single maintainer (note the keirontw Packagist vendor vs. BastienMesnil repository — clarify ownership/provenance in diligence) is a supply-chain risk to record.

How to Pitch It (Stakeholders)

To executives: This is a mature-enough (v1.0.0) open-source component that gives us pickup-point delivery across 12 European carriers in one dependency instead of 3–6 engineer-weeks of bespoke carrier work. It lowers time-to-market for new EU markets and keeps geocoding costs tunable. Two caveats to state plainly: it is Symfony-only, so on a Laravel stack the value is the design and carrier coverage, not plug-and-play install; and it is a single-maintainer v1.0.0, so we should pin the version, wrap it behind our own interface, and accept a maintenance contingency.

To engineering: Composer-installable Symfony bundle. Carriers auto-register via RelayPointProviderInterface (tagged services, no manual wiring). Geocoding is an injected strategy — swap Addok/Nominatim/Google/Photon or supply your own. Selection persists in session with no Order model dependency, and an optional checkout_listener bridges to your checkout event via a configurable event_class. Frontend ships as a Stimulus controller with CSS-variable theming and Twig block overrides; AssetMapper registration is automatic. Integration risk is concentrated in (a) the checkout listener contract, (b) geocoder rate limits and fallback behaviour, and (c) the absent Laravel bridge if we are not on Symfony. Recommend an interface wrapper on our side so carrier coverage and the bundle itself remain replaceable.