- What is splash/shippingbo and what is it used for?
- splash/shippingbo is a Composer-installable OpenAPI connector that wraps the ShippingBo OMS/WMS API for managing orders, shipments, stock and fulfillment data. In a Laravel application it acts as an outbound client for ShippingBo, not as a domain-rich package with Eloquent models or queue integration. Treat it as a vendor SDK that is useful only if ShippingBo is already your system of record for order orchestration and logistics.
- How do I install splash/shippingbo with Composer?
- It is distributed from a GitLab VCS repository rather than Packagist, so you add a Composer repository entry and provide GitLab credentials via auth.json or CI-scoped tokens. Because there is no visible semver metadata, pin the dependency to an exact commit SHA or tag and mirror the repository into your own organisation. Expect the first setup step to be authentication plumbing on every developer machine and build agent.
- Which PHP and Laravel versions does splash/shippingbo support?
- The package exposes no meaningful PHP or Illuminate/Laravel version constraints in its public metadata, so compatibility cannot be assumed. Check the composer.json of the exact commit you pin and run your own test matrix against your Laravel version. Treat framework auto-discovery and Laravel-specific integration as unconfirmed until you verify the source.
- Is splash/shippingbo an official Laravel package with a service provider and config publishing?
- No evidence indicates this is an idiomatic Laravel package. The Bundle naming and thin OpenAPI-generated client design suggest a framework-agnostic HTTP transport plus DTOs, so do not expect facades, publishable config, queue integration or Eloquent models. Plan to bind it yourself in your own service provider behind an internal interface.
- How does splash/shippingbo authenticate with the ShippingBo API?
- The public metadata does not document the authentication model, so you must inspect the generated client to determine whether it uses API keys, OAuth client credentials or per-tenant tokens. Confirm how bearer tokens are stored, refreshed and redacted from logs before using it in production. Ask the maintainer directly if the repository does not disclose this.
- Does splash/shippingbo handle API rate limits, 429 responses and retries?
- There is no documented retry, backoff or Retry-After handling in the package metadata. Because it is a generated OpenAPI client, rate-limit behavior depends on the underlying PSR-18 or Guzzle transport and any handwritten middleware. Verify idempotency before enabling retries on order or shipment creation calls, and wrap the client with your own resilience layer if necessary.
- How should I integrate splash/shippingbo into a Laravel application architecture?
- Do not call the package directly from controllers, jobs or models. Define ports in your own namespace, such as ShipmentGateway, StockReader and OrderSubmitter, and implement them with an adapter that wraps splash/shippingbo. Bind the adapter in a service provider so downstream code depends only on your interfaces, making a future swap to raw HTTP or another SDK a one-class change.
- Does splash/shippingbo support ShippingBo webhooks or only polling?
- The available overview mentions syncing fulfillment workflows but does not confirm webhook or subscription support. Since this is a generated OpenAPI client, webhook handling is likely outside its scope and may require your own routes, signature verification and queue jobs. Confirm with the maintainer whether ShippingBo offers subscriptions and whether the connector exposes them.
- How can I test code that uses splash/shippingbo?
- If the client is built on PSR-18 and PSR-7 with Guzzle underneath, you can inject a mock HTTP client and use Guzzle's MockHandler to return canned ShippingBo responses. Keep your adapter behind an interface so application tests can use an in-memory fake instead of the real client. Add contract tests against recorded payloads and persist raw request and response samples for reconciliation.
- What are the alternatives to splash/shippingbo and what are the maintenance risks?
- Check whether ShippingBo publishes an official SDK or API client before adopting this agency-published connector; an official client is usually preferable. The package shows zero stars, no dependents and no visible release cadence, so abandonment and generated-code drift are real risks. If you must use it, fork and mirror the repository, pin an exact commit, and isolate it behind your own adapter so you can replace it quickly.