ERP Roadmap 27

- **Roadmap Continuation**  
  - **Inventory Module (98% Complete)**  
    - Prerequisite: Ensure `stock mutation` and `stock level` APIs are stable and fully exposed for marketplace sync service consumption.  
    - Constraint: Must be completed before proceeding to the next phase.  

  - **Omnichannel Marketplace Module (45% Complete)**  
    - Immediate next step: Develop **channel-specific sync adapters** (Shopee, Tokopedia, TikTok, Lazada).  
    - Key requirements:  
      - Use **queue-based pattern** to avoid blocking operations.  
      - Implement **idempotency key** to prevent duplicate inventory syncs.  
    - TODO: Finalize adapter architecture and test non-blocking behavior.  

  - **Enterprise Backend Hardening (Phase 2)**  
    - Mandatory pre-deployment tasks:  
      - Add **Correlation ID** for traceability in logs.  
      - Integrate **Structured Logger** for consistent monitoring.  
      - Enforce **Idempotency** for webhook handling (e.g., stock update callbacks from marketplaces).  
    - Constraint: Required to ensure retry-safe operations and debugging capabilities for live sync.  
    - Unresolved: No mention of specific timelines for Phase 2 completion.  

- **Constraints & Dependencies**  
  - Inventory Module must be fully stable before marketplace sync adapters can function reliably.  
  - Sync adapters depend on queue-based infrastructure and idempotency logic to align with scalability and reliability goals.  
  - Backend hardening (Correlation ID, Structured Logger) is critical for debugging and compliance with marketplace webhook requirements.  

- **Action Items**  
  - Finalize Inventory Module API stability and endpoint exposure.  
  - Prioritize development of queue-based sync adapters for Shopee/Tokopedia/TikTok/Lazada.  
  - Implement idempotency keys in all adapters to avoid duplicate syncs.  
  - Schedule backend hardening tasks (Correlation ID, Structured Logger) for Phase 2 before live deployment.  

- **Unresolved Issues**  
  - No clear timeline provided for Phase 2 (backend hardening).  
  - Uncertainty about how to handle edge cases in idempotency logic (e.g., partial failures, conflicting updates).  
  - Missing details on how to test and validate retry-safe webhook handling in Phase 2.

Jawab singkat 3 poin: roadmap marketplace inventory sync harus dilanjutkan dari modul apa?

## Roadmap: Marketplace Inventory Sync — Lanjut dari 3 Modul Ini

1. **Inventory Module (98%)** — Pastikan stock mutation & stock level API sudah stable dan expose endpoint yang bisa di-consume oleh marketplace sync service. Ini fondasi utama.

2. **Omnichannel Marketplace Module (45%)** — Ini modul yang langsung dikerjakan: bangun **sync adapter** per channel (Shopee/Tokopedia/TikTok/Lazada) dengan pattern queue-based agar tidak blocking, plus idempotency key untuk prevent double-sync.

3. **Enterprise Backend Hardening (Phase 2)** — Sebelum sync ke marketplace live, wajib ada: **Correlation ID + Structured Logger + Idempotency** karena webhook marketplace (stock update callback) butuh traceability dan retry-safe handling.