- What Laravel/Symfony versions does baks-dev/ozon-support support?
- The package requires PHP 8.4+ and is designed for Laravel/Symfony projects. While it aligns with modern PHP features, there are no explicit guarantees for Laravel 10+. Always validate compatibility with your specific version by checking the package’s changelog or running tests.
- How do I install and configure baks-dev/ozon-support for Ozon API integration?
- Install via Composer with `composer require baks-dev/ozon-support`, then register the Ozon Support profile type using the Artisan command `php artisan baks:users-profile-type:ozon-support`. Configure OAuth2 credentials and required scopes (e.g., `Orders.ReadWrite`) in your `.env` or service provider.
- Does this package handle Ozon webhooks, and how do I verify their security?
- Yes, the package abstracts Ozon webhook processing, but you must validate payload signatures and handle edge cases like failed signatures or rate-limiting. Test with real-time updates (e.g., order cancellations) and ensure dead-letter queues are configured for failed webhooks.
- Are there any Laravel-specific dependencies or custom migrations included?
- The package follows Laravel’s service container pattern and may include migrations if database schema changes are required. Run `php artisan migrate:status` to check for conflicts. No framework-specific dependencies beyond core Laravel are documented, so verify compatibility with your existing setup.
- How do I test the Ozon integration before deploying to production?
- Run the provided PHPUnit tests with the group flag: `php bin/phpunit --group=ozon-support`. For deeper validation, add integration tests for critical workflows like order creation, refunds, and payment processing to uncover hidden dependencies (e.g., Guzzle HTTP client version).
- What OAuth2 scopes are required for Ozon API v3 compatibility?
- The package assumes standard scopes like `Orders.ReadWrite` and `Payments`, but always cross-reference Ozon’s API documentation for the latest requirements. Validate your OAuth2 configuration in the package’s `OzonAuthService` or equivalent class to ensure token refresh logic and credential storage align with Laravel Vault or your preferred method.
- Is baks-dev/ozon-support suitable for multi-marketplace strategies, or is it Ozon-specific?
- While the package is highly specialized for Ozon, its modular design (profile-type system) allows it to coexist with other marketplace integrations in a Laravel/Symfony app. However, no built-in support for other platforms exists—customize or extend as needed for broader use cases.
- Are there any known risks or limitations with the latest version (v7.4.16)?
- The package lacks detailed release notes for versions 7.4.14–7.4.16, raising risks of undocumented changes. Fork the package immediately to control updates and document assumptions. Monitor for PHP 8.4+ dependencies (e.g., strict typing) and localize region-specific logic like tax IDs or payment methods if needed.
- How does this package handle rate-limiting and failed API requests?
- The package abstracts Ozon’s API interactions but does not explicitly document retry logic or rate-limiting strategies. Test edge cases like throttled requests or failed webhooks to ensure resilience. Consider implementing custom middleware or decorators for advanced error handling.
- What alternatives exist for Ozon API integration in Laravel if this package lacks documentation?
- Alternatives include building a custom wrapper using Ozon’s official API SDK or leveraging community packages like `ozon-api` (if available). However, these may require more effort for webhooks, OAuth2, and workflow automation. Forking `baks-dev/ozon-support` and extending it is often the fastest path for tailored solutions.