Weave Code
Budbee Bundle Laravel Package
setono/budbee-bundle
Symfony bundle from Setono that adds Budbee home delivery to your e-commerce checkout, letting customers select Budbee shipping options and handling the related delivery data. Easy to install, though it has seen little community adoption so far.
Setono Budbee Bundle provides a Symfony integration for Budbee, the last-mile delivery service. It wraps Budbee’s API in configurable services so your application can offer Budbee delivery options, register shipments, and keep tracking information in sync with your order and fulfilment workflows.
- Configurable Budbee API client
- Shipping/delivery method integration
- Order registration and tracking updates
- Symfony DI-based configuration
- Extensible services for custom workflows
Frequently asked questions about Budbee Bundle
- Can I use setono/budbee-bundle in a Laravel application?
- No. setono/budbee-bundle is a Symfony bundle that ships a Bundle class, a DI extension, and Symfony service definitions, so it cannot be installed and consumed as-is in Laravel's container and provider model. The realistic Laravel path is to depend on the underlying Budbee PHP SDK directly and write a Laravel-native adapter with a service provider, config file, and queued jobs. Treat this repository as a reference for which SDK version to pin and which Budbee concepts you need to map.
- How do I install setono/budbee-bundle?
- Run composer require setono/budbee-bundle, register the bundle in config/bundles.php, and configure your Budbee API credentials and environment under config/packages. The bundle then auto-wires the Budbee client service for injection into your own services. This installation flow only applies to Symfony applications, not Laravel.
- Does setono/budbee-bundle support Symfony 7 and current PHP versions?
- The last release noted in the package assessment is 2024-03-06, so you should check the composer.json Symfony and PHP constraints before assuming Symfony 7 compatibility. Symfony major bumps can invalidate a bundle even when the upstream carrier API has not changed, which is a real upgrade risk here. Inspect the require section and, if needed, test on a branch before committing.
- How do I configure Budbee API credentials with this bundle?
- Symfony bundles of this type expose a configuration tree consumed under config/packages, typically covering API key, secret, and a sandbox or production base URI. Keep the secrets in environment variables and reference them from the bundle config rather than committing them. Mirror those same key names if you later replicate the setup in a Laravel config/services.php file.
- Which Budbee features does the bundle actually cover?
- The stated scope is home delivery integration: shipping options, checkout integration, and order handling, with flexible last-mile delivery choices for customers. Whether shipment creation, label generation, tracking, returns, pickup-point selection, and webhooks are exposed depends on the pinned Budbee SDK version and any thin wrapper logic the bundle adds. Confirm each capability against the SDK's source before designing your checkout flow around it.
- What is the best way to integrate Budbee into Laravel without this bundle?
- Pin the upstream Budbee PHP SDK, then author a BudbeeServiceProvider that binds a configured client singleton and mirrors the bundle's config keys in config/services.php and .env. Wrap carrier calls in queued jobs such as CreateBudbeeShipment and FetchBudbeeTracking so carrier latency never blocks checkout or order placement. Map Budbee DTOs onto your own Shipment, TrackingEvent, and PickupPoint models rather than leaking SDK objects into your domain.
- Is setono/budbee-bundle safe to run in production?
- It is MIT licensed and technically sound as Symfony glue, but adoption signals are weak: the assessment reports zero stars and zero dependents, single-vendor maintenance, and a small maintainer team. There is no SLA and no evidence of wide production usage, so you own the risk. If Budbee is business-critical, budget for pinning the SDK version and writing your own integration tests around it.
- Does this bundle include Sylius support?
- Setono is a Sylius-focused agency and a separate setono/sylius-budbee-plugin is likely to exist, so Sylius-specific behavior probably lives outside this bundle. Check Packagist and the repository's composer.json before assuming Sylius resources, configuration, or shipping method rules are included here. For a plain Symfony app, the bundle is the intended integration point.
- How do I test a Budbee integration without creating real shipments?
- Use Budbee's sandbox or test mode if your account provides one, and point the client at the sandbox base URI via configuration. In application tests, bind a fake or mocked Budbee client into the container and assert on the calls your jobs make rather than hitting the network. The assessment does not confirm a test suite or CI in the bundle itself, so do not rely on it for coverage of your own integration.
- How should I verify Budbee webhooks if I adapt this for Laravel?
- The bundle's authentication and webhook model is an open question in the assessment: it is unclear whether Budbee/Instabee uses API keys, OAuth, or HMAC-signed callbacks. Register a dedicated webhook route and verify signatures or shared secrets in middleware before touching order state. Always make webhook handlers idempotent and queue the actual processing so retries from the carrier cannot double-apply status changes.
Weaver
How can I help you explore Laravel packages today?