- How do I install slince/shopify-api-php in a Laravel project?
- Install it with Composer using composer require slince/shopify-api-php, then confirm the package's PHP and HTTP client constraints against your app. Because it is a standalone PHP SDK rather than a Laravel package, you should add your own service provider, config file, and adapter binding. Do not call the SDK directly from controllers or models.
- Does slince/shopify-api-php support Laravel 10 or Laravel 11?
- There is no documented Laravel-native support, so Laravel 10 or 11 compatibility depends on the package's PHP version and dependency constraints. Test it in a non-production branch with your exact Laravel and Guzzle versions before committing. Wrap it behind an application-owned interface so a version mismatch does not leak into domain code.
- How does slince/shopify-api-php handle Shopify authentication and OAuth?
- The SDK is described as simplifying Shopify Admin API authentication, but the available context does not confirm complete OAuth token exchange or refresh helpers. Verify token lifecycle behavior against a Shopify sandbox and be prepared to implement OAuth callback handling locally. Store shop credentials and access tokens in Laravel config or environment variables, never in code.
- Can slince/shopify-api-php sync Shopify products, orders, and customers?
- Yes, the SDK is intended for CRUD operations across products, orders, customers, and more, plus raw API calls. In Laravel, put it behind services such as ShopifyProductService or ShopifyOrderSyncService rather than exposing SDK classes to controllers and jobs. Start with one read-only sync use case to validate authentication, pagination, and error behavior.
- How do I handle Shopify API rate limits with slince/shopify-api-php?
- The package claims to handle rate limits, but you still need to confirm how it surfaces 429 responses and Shopify rate-limit headers. Use Laravel queues, exponential backoff, caching for read-heavy calls, and idempotency keys for writes. Monitor retries and alert on sustained throttling.
- Does slince/shopify-api-php support pagination for large Shopify stores?
- Pagination is part of the package's stated feature set, which matters for product and order listings. Validate cursor behavior, page size limits, and loop termination with real sandbox data before relying on it. Encapsulate pagination inside your adapter so you can fix or replace it without changing call sites.
- Can I use slince/shopify-api-php for Shopify webhooks in Laravel?
- There is no evidence in the provided context that the package includes complete webhook verification or delivery handling. Plan to verify Shopify HMAC signatures and enforce idempotency in your Laravel application, then process webhook payloads through queued jobs. Handle duplicate and missed deliveries with monitoring and a manual replay path.
- What are the alternatives to slince/shopify-api-php for a Laravel app?
- Alternatives include the official Shopify PHP SDK, Laravel-specific Shopify packages, or a thin in-house client around Shopify's REST or GraphQL Admin API. Compare API version coverage, OAuth and webhook support, maintenance activity, and dependency compatibility. Keep your integration behind an interface so switching clients does not require rewriting controllers or jobs.
- Is slince/shopify-api-php actively maintained and safe for production?
- The package has modest community traction, an unknown repository and maintainer profile, and no commercial support, so treat it as moderate risk. Pin the version, track upstream releases and Shopify API deprecations, and budget time for a fork or replacement. The MIT license lowers legal risk but does not remove maintenance risk.
- How should I test slince/shopify-api-php before using it in production?
- Run a time-boxed spike in a non-production branch using real Shopify sandbox credentials. Wrap the client behind an interface, implement one read-only use case, and test authentication, pagination, rate-limit handling, timeouts, and error responses. Only then add write operations, webhooks, and queued retries with monitoring.