Wildberries Orders Laravel Package

Technical Evaluation

Architecture Fit

• Modularity: The package is designed as a self-contained Laravel module, making it ideal for modular monoliths or microservices where Wildberries order processing is a distinct feature. Its focus on FBS/DBS-specific workflows aligns well with e-commerce platforms targeting Russian/CIS markets, but lacks broader marketplace support (e.g., Ozon, AliExpress).
• Domain Alignment: Directly addresses order lifecycle management (creation, cancellation, status updates), payments, and delivery profiles, reducing custom API development effort by 70–80%. However, it excludes inventory sync, analytics, and real-time webhooks, requiring complementary solutions for a full marketplace integration.
• Laravel Ecosystem Synergy: Leverages Doctrine ORM, Symfony Console, and Laravel’s service container, ensuring seamless integration for teams already using these tools. The reliance on Artisan commands for setup aligns with Laravel’s CLI-driven workflows but may introduce namespace collisions if the host system uses similar command structures.
• Event-Driven Gaps: While the package likely emits Laravel events (e.g., OrderCreated, PaymentProcessed), the host system may need custom event listeners or webhook integrations for real-time sync with Wildberries’ API (e.g., shipment tracking updates).

Integration Feasibility

• Console-Driven Setup: The package’s dependency on Artisan commands (baks:users-profile-type, baks:delivery, etc.) simplifies configuration but introduces risk of command namespace conflicts. Mitigation: Rename or alias commands (e.g., wb:delivery:fbs) or use a custom namespace prefix.
• Database Schema: Introduces Wildberries-specific tables (e.g., wb_orders, wb_payments) via migrations. Conflict risk exists if the host system has overlapping schemas (e.g., orders table with similar fields). Mitigation: Use table prefixes (e.g., wb_) or custom migration strategies.
• API Abstraction: Provides pre-built Wildberries API wrappers for FBS/DBS, but assumes the host system uses Guzzle or a compatible HTTP client. Custom adapters may be needed for non-standard authentication flows (e.g., OAuth2 with custom scopes).
• Payment/Delivery Integration: The package includes pre-configured payment and delivery profiles for FBS/DBS, but the host system must extend or override these to match its existing payment gateways (e.g., Stripe, YooMoney) or delivery services (e.g., DHL, CDEK).

Technical Risk

Key Questions

1. Host System Compatibility:

   • Does the Laravel app support custom profile types, payments, and deliveries via console commands?
   • Are there existing order/payment/delivery models that could conflict with the package’s schema?
   • How does the host system handle event-driven workflows (e.g., order status transitions)?

2. Workflow Integration:

   • Does the host system require bidirectional sync with Wildberries’ API (e.g., pushing order updates to Wildberries)?
   • Are webhooks needed for real-time events (e.g., shipment tracking, cancellations)?
   • How are payment failures or delivery exceptions currently handled?

3. Performance and Scaling:

   • Could the package introduce N+1 queries or blocking API calls during checkout?
   • What are the rate limits for Wildberries’ API, and how will they be managed (e.g., retries, caching)?
   • Is async processing (e.g., Laravel Queues) required for high-order volumes?

4. Localization and Compliance:

   • Does the host system need Wildberries-specific localization (e.g., Russian language, tax rules like NDS/VAT, address formats)?
   • Are there FBS/DBS compliance requirements beyond what the package provides?

5. Maintenance and Governance:

   • Is there a dedicated team to maintain the package, or will forks be necessary?
   • How will breaking changes (e.g., Wildberries API updates) be handled?
   • What is the rollback plan if the package introduces critical bugs?

6. Testing and Validation:

   • How will sandbox testing be conducted (e.g., Wildberries test API credentials)?
   • Are there automated tests for the package’s core functionality (e.g., order creation, cancellation)?
   • What edge cases need validation (e.g., partial refunds, delayed deliveries)?

Integration Approach

Stack Fit

• Primary Fit:
  • Laravel 10+ (PHP 8.4+): Optimized for modular monoliths or microservices where order processing is a Laravel app.
  • Doctrine ORM: Mandatory for migrations and entity management.
  • Symfony Console: Required for Artisan commands (mitigate collisions via custom namespaces).
• Secondary Fit:
  • Symfony 6.4+: Possible with Laravel Bridge or custom command adapters.
  • Lumen: Limited support due to missing Doctrine/Symfony Console.
• Non-Fit:
  • Non-PHP stacks (Node.js, Python, Java): Requires high-effort adapters for console commands, migrations, and service containers.
  • Legacy Laravel (<9.x): May require backporting or polyfills for PHP 8.4+ features.
• Dependencies:
  • Wildberries API: Assumes Guzzle or PSR-18 HTTP client; custom adapters needed for other clients.
  • Payment Gateways: Extends host system’s payment logic (e.g., Stripe, YooMoney).
  • Delivery Services: Integrates with host system’s delivery profiles (e.g., DHL, CDEK).

Migration Path

Phase 1: Pre-Integration (1–2 weeks)

1. Audit Host System:
   • Document existing order, payment, and delivery models.
   • Identify schema conflicts (e.g., overlapping table/column names).
   • Review event listeners and webhook handlers.
2. Environment Setup:
   • Isolate the package in a staging environment.
   • Backup the database and document current workflows.
3. Dependency Validation:
   • Verify PHP 8.4+ and Laravel 10+ compatibility.
   • Test Doctrine ORM and Symfony Console integration.

Phase 2: Installation (1 week)

1. Composer Install:

   composer require baks-dev/wildberries-orders
   

2. Console Setup:
   • Run commands for FBS/DBS (rename if needed):

     php bin/console wb:users-profile-type:wildberries-fbs
     php bin/console wb:payment:wildberries-fbs
     php bin/console wb:delivery:wildberries-fbs
     

3. Database Migrations:
   • Install assets and generate migrations:

     php bin/console baks:assets:install
     php bin/console doctrine:migrations:diff
     php bin/console doctrine:migrations:migrate
     

4. Configuration:
   • Add Wildberries API credentials to .env:

     WILDBERRIES_API_KEY=your_key
     WILDBERRIES_API_SECRET=your_secret
     

   • Bind custom services in config/app.php or a service provider:

     'bindings' => [
         WildberriesOrderService::class => fn($app) => new WildberriesOrderService(
             $app->make(GuzzleClient::