- How do I install webapix/laravel-mygls in a Laravel application?
- Install it with Composer using the package name webapix/laravel-mygls, then check the README for any required service provider registration or config publishing steps. Laravel package auto-discovery may handle the provider, but verify that against your Laravel version. After installation, confirm whether the package publishes configuration or migrations before wiring it into fulfilment code. Keep the package pinned in Composer once the integration is validated.
- How do I configure MyGLS credentials for laravel-mygls?
- The package is described as configurable, so MyGLS credentials will likely be supplied through a published config file and environment variables. Store those values in your secret management system and make sure Laravel config caching is handled correctly in deployment. Confirm the required MyGLS account type, authentication model, and sandbox credentials in the package documentation before going live.
- Which Laravel and PHP versions does webapix/laravel-mygls support?
- Check the package composer.json and README for the exact Laravel and PHP support matrix, because the provided overview does not list versions. Verify HTTP client compatibility, service-provider auto-discovery, config publishing, queue serialization, and whether migrations are published. Test the package against your application runtime before committing to it, and pin the version you validate.
- Can laravel-mygls create parcels and print GLS shipping labels?
- Yes, the package overview says it lets you create parcels, print shipping labels, and track GLS deliveries from a Laravel application. The real integration work is mapping your order, address, and parcel data into package calls and persisting shipment IDs, label references, and tracking numbers. Confirm label formats and printer output compatibility with your warehouse operations during a sandbox spike.
- Does webapix/laravel-mygls support GLS tracking webhooks or only polling?
- The overview confirms tracking support but does not state whether MyGLS tracking updates arrive through webhooks or require polling. Check the README and MyGLS API documentation, then design your tracking reconciliation workflow around the available mechanism. If webhooks are not supported, plan scheduled polling with rate-limit awareness and store status history.
- Is there a MyGLS sandbox I can use to test laravel-mygls?
- The provided context does not confirm sandbox availability, so verify MyGLS account options and package documentation first. Run a time-boxed spike that creates a label, retrieves tracking, cancels a shipment, and exercises error responses and rate limits. Add contract tests against the sandbox where possible and avoid adopting the package without that validation.
- Does laravel-mygls support COD, pickup points, insurance, multi-piece shipments, and returns?
- The package description only calls out parcels, labels, and tracking, so do not assume coverage for COD, insurance, pickup points, multi-piece shipments, cancellations, reprints, or returns. Confirm each required MyGLS endpoint against the package README and a sandbox spike. If coverage is incomplete, keep a direct MyGLS HTTP fallback behind your own adapter.
- How should I handle errors, retries, and idempotency with laravel-mygls?
- Wrap package calls in your own service layer so you can translate exceptions, apply retry policies, and record shipment status history consistently. Use Laravel queues with backoff for label and tracking jobs, and confirm whether the package or MyGLS API supports idempotency keys for create operations. Handle rate limits explicitly and avoid blind retries on non-idempotent parcel creation.
- Is webapix/laravel-mygls safe to use in production?
- Code-level risk is likely low to moderate because the package is MIT-licensed and Laravel-native, but vendor and community risk is moderate given limited adoption and a small maintainer base. Treat it as an accelerant rather than a strategic dependency: pin versions, monitor releases, and keep a fork or direct HTTP fallback option. Put it behind a feature flag per carrier or region and test operational workflows before production rollout.
- Should I call laravel-mygls directly or wrap it in a carrier adapter?
- Wrap it behind an internal ShippingGateway or CarrierAdapter interface so controllers, jobs, and admin tooling never depend directly on MyGLS package classes. That keeps your checkout and order domain independent of the carrier and lets you swap in a direct MyGLS HTTP client or another shipping integration without changing domain logic. Use the package only inside the Laravel fulfilment service and expose your own interface to the rest of the application.