@clidey/dory 0.1.0 → 0.3.0

package/docs/usage/ui-workflows/demand-planning.mdx

@@ -1,210 +0,0 @@
----
-title: 'Demand Planning'
-description: 'Accessing and using planning tools, forecasts, breakdowns, and metrics to manage product demand.'
----
-
-# Demand Planning Service and Web UI Component
-
-## 1. Purpose and Scope
-
-The Demand Planning module encompasses the backend service (`DemandPlanService`) and the frontend React components (e.g., `DemandPlanContent`, `DemandPlanning`) responsible for managing the full lifecycle of demand planning. It provides an end-to-end solution for generating, adjusting, summarizing, and refreshing sales forecasts and demand plans for a team.
-
-This module addresses demand forecasting challenges by integrating historical sales data, forecasts, and product information to produce actionable demand plans with monthly granularity. It supports both planned and actual sales tracking, provides detailed revenue breakdowns by supplier and Shopify categories, and enables manual adjustments with granular controls.
-
-### System Boundaries and Architectural Context
-
-- The Demand Planning Service is a NestJS injectable that interacts with the database and external domain services (InventoryService, SalesOrdersService, TeamsService, ForecastService, WorkflowService, EmailService).
-- The frontend React components form part of the Genie Web application and use React Hook Form and multiple API endpoints to present and update demand plan data.
-- Demand plan data is persisted and queried from PostgreSQL tables (demand_plan, demand_plan_item, demand_plan_item_monthly_sales).
-- The service integrates tightly with the Workflow subsystem to handle asynchronous generation and update of plans.
-
-
-## 2. Technical Overview
-
-### High-Level Architecture
-
-```mermaid
-flowchart TD
-  subgraph Backend["Backend - NestJS Service"]
-    DPService["DemandPlanService"]:::service
-    InventoryService["InventoryService"]:::service
-    SalesOrdersService["SalesOrdersService"]:::service
-    TeamsService["TeamsService"]:::service
-    ForecastService["ForecastService"]:::service
-    WorkflowService["WorkflowService"]:::service
-    EmailService["EmailService"]:::service
-    DB["PostgreSQL DB"]:::database
-  end
-
-  subgraph Frontend["Frontend - React Web UI"]
-    DPPage["DemandPlanning Component"]:::frontend
-    DPContent["DemandPlanContent Component"]:::frontend
-    API["Demand Plan API Endpoints"]:::api
-  end
-
-  DPService -->|"reads/writes"| DB
-  DPService -->|"calls"| InventoryService
-  DPService -->|"calls"| SalesOrdersService
-  DPService -->|"calls"| TeamsService
-  DPService -->|"calls"| ForecastService
-  DPService -->|"starts workflows"| WorkflowService
-  DPService -->|"sends emails"| EmailService
-
-  DPPage -->|"uses"| DPContent
-  DPContent -->|"calls"| API
-  API -->|"calls"| DPService
-
-  classDef service fill:#d1e7dd,stroke:#0f5132,color:#0f5132,stroke-width:1px
-  classDef api fill:#cfe2ff,stroke:#084298,color:#084298,stroke-width:1px
-  classDef frontend fill:#f8d7da,stroke:#842029,color:#842029,stroke-width:1px
-  classDef database fill:#fff3cd,stroke:#664d03,color:#664d03,stroke-width:1px
-```
-
-### Key Technologies and Frameworks
-
-- **Backend:** NestJS framework with Dependency Injection for modular services.
-- **Data Access:** TypeORM with PostgreSQL.
-- **Validation:** Zod schemas for DTOs.
-- **Frontend:** React, React Hook Form for form state management.
-- **API:** React Query hooks for data fetching and mutations.
-- **UI Components:** Custom Jasmine component library for design consistency.
-
-## 3. Core Concepts and Responsibilities
-
-### Key Concepts
-
-- **DemandPlanEntity:** Represents a demand plan instance linked to a team, with lifecycle statuses such as `Generating` and `Ready`.
-- **DemandPlanItemEntity:** Represents inventory variants within a demand plan including sale and cost prices.
-- **DemandPlanItemMonthlySalesEntity:** Holds monthly sales data per demand plan item, including forecast, adjusted, previous period, and actual sales quantities.
-- **Breakdown Types:** Revenue breakdowns can be viewed by supplier or Shopify category.
-- **WorkflowService:** Manages asynchronous workflows for generating plans, refreshing forecasts, and updating actuals.
-
-### Responsibilities
-
-- **DemandPlanService:** Primary service managing demand plan lifecycle, data generation, adjustments, refreshes, and notifications.
-- **Frontend Components:** Render the demand planning UI, showing plan summaries, revenue breakouts, product-level forecasts, and providing user actions.
-
-### Ownership and Logging
-
-- Maintained by the Forecast and Planning engineering team.
-- Uses NestJS Logger for structured logs.
-- Catches and reports errors using custom `GenieException` and `captureException` for observability.
-
-### Non-Functional Requirements (NFRs)
-
-- **Performance:** Batch processing for demand plan item creation and monthly sales insertion ensures scalability.
-- **Reliability:** Transactional operations used in demand plan refresh to maintain data consistency.
-- **Security:** Access control presumed implemented at broader application layer (not detailed in context).
-- **Scalability:** Asynchronous workflows scale demand plan generation and actual updates across teams.
-
-## 4. Code Structure
-
-### Major Files and Folders
-
-- **Backend Service:** 
-  - `apps/api/src/forecast/services/demand-plan.service.ts` — Core business logic and data handling.
-- **Frontend:** 
-  - `apps/web/src/components/pages/demand-planning/demand-plan-content.tsx` — Detailed demand planning UI and form management.
-  - `apps/web/src/components/pages/demand-planning/index.tsx` — Page entry point managing demand plan lifecycle views.
-  - `apps/web/src/components/pages/demand-planning/hooks.ts` — Hooks for aggregated summary and feature flag checks.
-
-### Key Execution Flows
-
-- **Demand Plan Generation:**
-  - Initiated by mutation `useGenerateDemandPlanMutation` on frontend.
-  - Backend `startGeneratingDemandPlan()` creates a new demand plan in `Generating` status.
-  - Items are populated in batches from inventory.
-  - Monthly sales generated using forecast and historical sales data.
-  - When complete, backend marks demand plan as `Ready` and triggers actual sales update workflow and notifications.
-
-- **Demand Plan Refresh:**
-  - Triggered via `refreshForecast` mutation.
-  - Creates a new `Generating` demand plan, deactivates old one.
-  - Starts regeneration workflows.
-
-- **Adjusting Sales Quantities:**
-  - User edits quantities in the frontend form.
-  - On submit, dirty fields are mapped and sent to `updateDemandPlanItemQuantitiesMutation`.
-  - Backend updates adjustedQuantity fields in monthly sales.
-
-### Representative Code Snippet: Adjust Monthly Sales (Backend)
-```ts
-async adjustMonthlySales({ teamId, adjustments }: { teamId: string; adjustments: AdjustDemandPlanMonthlySalesRequestDto; }) {
-  // Validate demand plan items belong to current ready demand plan.
-  const demandPlan = await this.ensureCurrentDemandPlanInStatus({ teamId, status: DemandPlanStatus.Ready });
-
-  // Find related monthly sales and update adjustedQuantity.
-  const monthlySalesToUpdate = adjustments.map((adjustment) => {
-    const monthlySale = relatedMonthlySales.find(item => item.demandPlanItemId === adjustment.demandPlanItemId && item.month === adjustment.month);
-    if (!monthlySale) throw new GenieException("Monthly sale not found", { /* details */ });
-    monthlySale.adjustedQuantity = adjustment.adjustedQuantity;
-    return monthlySale;
-  });
-
-  await this.dataSource.getRepository(DemandPlanItemMonthlySalesEntity).save(monthlySalesToUpdate);
-}
-```
-
-### Representative Code Snippet: Frontend Submit Handler
-```tsx
-const onSubmit = handleSubmit((values) => {
-  const dirtyItems = values.items
-    .map((item, i) => ({
-      ...item,
-      sales: item.sales.filter((_, si) => dirtyFields.items?.[i]?.sales?.[si]?.adjustedQuantity),
-    }))
-    .filter(item => item.sales.length > 0);
-
-  const mapped = mapToAdjustDemandPlanMonthlySalesRequestDto({ items: dirtyItems });
-  updateDemandPlanItemQuantities(mapped);
-});
-```
-
-## 5. API and Interfaces
-
-### Demand Plan Summary Endpoint
-- Returns current demand plan metadata plus monthly aggregates (planned, previous period, actuals).
-
-### Revenue Breakdown Endpoints
-- Provide monthly revenue breakdown by Shopify category or supplier.
-
-### Mutation Endpoints
-- `updateDemandPlanItemQuantities`: Accepts adjusted monthly sales per item.
-- `refreshShopifyPrices` and `refreshForecast`: Trigger price and forecast updates respectively.
-
-### Data Schemas
-- Demand plan date ranges use 12 months starting from plan start date.
-- Sales quantities are integers, with adjusted quantities nullable.
-
-### Failure Modes
-
-- Exceptions thrown if invalid demand plan status or missing entities.
-- Validation errors if duplicate months for same item adjusted.
-- Errors during workflow start rollback demand plan state.
-
-## 6. Environment & Configuration
-
-- Environment configuration details not provided.
-- Service depends on database connectivity, external services for inventory, forecast, and workflows.
-
-## 7. Testing, Monitoring, and Deployment
-
-- No explicit testing or CI/CD details provided.
-- Logging and error capture integrated via `Logger` and `captureException` utilities.
-
-## 8. Troubleshooting & Known Issues
-
-- Generation or refresh failure leads to demand plan deletion and rollback.
-- Warnings logged when SKU counts mismatch or invalid periods detected.
-
-## Additional Notes
-
-- Frontend components implement polling for generation status with refetchInterval.
-- Demand plan modal dialogs for refreshing forecasts provide user feedback.
-- Dashboard includes detailed breakdown components and product-level forecasts.
-
-## References
-- [DemandPlanService Source Code](apps/api/src/forecast/services/demand-plan.service.ts)
-- [DemandPlanContent React Component](apps/web/src/components/pages/demand-planning/demand-plan-content.tsx)
-- [DemandPlanning Page Component](apps/web/src/components/pages/demand-planning/index.tsx)
-- [Demand Planning API Exports](apps/web/src/api/resources/demand-plan/index.ts)

package/docs/usage/ui-workflows/favorites.mdx

@@ -1,167 +0,0 @@
----
-title: 'Favorites & User Preferences'
-description: 'Managing favorite inventory items and quick-access preferences to enhance productivity.'
----
-
-# Favorites & User Preferences
-
-## Overview
-
-The Favorites feature in the Genie app provides users with a dedicated workflow to manage their preferred products efficiently. It enables users to mark inventory variants as favorites, maintain a curated list, export favorite items, and create or add to purchase orders directly from this set of prioritized products.
-
-This system is integrated tightly within the inventory management domain and serves to enhance user productivity by offering filtered views, quick actions, and seamless data export related to favorite items.
-
-## Purpose and Scope
-
-This documentation covers the Favorites feature implementation within the Genie web application, detailing its UI components, hooks, integration with API resources, and their interaction with the inventory subsystem.
-
-It is intended for developers maintaining the Favorites workflows and related API services.
-
-## Architectural Context
-
-The Favorites functionality is implemented as a React UI feature connected to backend services using GraphQL or REST APIs exposed by the Genie platform. It uses React hooks for state management, server mutations, and querying filtered inventory data.
-
-It leverages shared data types from `@genie/shared` and common utility modules for operations like CSV export and notifications.
-
-### Key system boundaries:
-
-- **UI Layer:** React components and hooks managing Favorites state, triggers, and rendering.
-- **API Layer:** Mutations and queries to mark/unmark favorites, fetch filtered favorite inventory items, and interact with purchase orders.
-- **Data Layer:** Inventory entities with a `favourite` property representing if the item is marked as a favorite.
-
-## Technical Overview
-
-Favorites management is primarily handled through hooks such as `useFavoritesActions` and `useFavoritesData` located within the Favorites page directory.
-
-These hooks coordinate with API mutations for:
-
-- Adding/removing inventory items as favorites
-- Creating purchase orders from favorite variants
-- Exporting favorites subset to CSV
-
-The UI layer (`Favorites` page component) uses these hooks to present filtering, searching, pagination, and action controls to users.
-
-### Integration Points:
-
-- Inventory API to fetch inventory items filtered by the favorite flag.
-- Inventory mutation endpoints for toggling favorite states.
-- Purchase order API for creating purchase orders from selected favorites.
-
-These API integrations are wrapped by custom React Query mutations, ensuring data consistency and mutation side-effect handling (e.g., UI notifications).
-
-## Core Concepts and Responsibilities
-
-- **Favorite Inventory Item:** Inventory variant marked by the user to indicate priority or preference.
-- **SelectedProductVariants:** The current set of variant IDs that the user has selected for batch operations.
-- **FavoriteAction:** Determines the next toggle action, between "Favorite" and "Unfavorite" depending on the current items' states.
-
-### Design Assumptions:
-
-- Favoriting is a user/team level setting stored in the product variant entity.
-- Bulk operations (toggle, export, create PO) operate on currently selected variants.
-- The UI supports filtering and sorting to assist users in managing favorites.
-
-### Ownership & Maintenance:
-
-- The Favorites feature is primarily owned by the web frontend team.
-- Backend services track favorite state changes and onboard events through the `FavouritesService`.
-
-## Code Structure
-
-### Key Files & Components:
-
-- **`apps/web/src/components/pages/favorites/index.tsx`**
-  - Entry component for the Favorites page.
-  - Renders UI including headers, filters, favorites list, action buttons, and pagination.
-  - Uses hooks `useFavoritesActions`, `useFavoritesData`, and `useInventoryItemsFilterProps`.
-
-- **`apps/web/src/components/pages/favorites/hooks.ts`**
-  - Contains hooks managing favorite items state, selection, mutations, and data fetching.
-  - Key hooks:
-    - `useFavoritesActions` handles selection, export, favorite toggling, and purchase order creation.
-    - `useFavoritesData` provides paginated, filtered inventory data scoped to favorites.
-    - `useInventoryItemsFilterProps` defines filtering properties and options.
-
-- **`apps/web/src/api/resources/inventory-items/favourites.ts`** (implied from exports)
-  - API mutations and queries related to favorites management.
-
-- **`apps/api/src/pim/services/favourites.service.ts`**
-  - Backend service managing database updates for favorite flags on product variants.
-  - Tracks onboarding events when favorites are set.
-
-### Example: Favorite toggle mutation call
-```ts
-const onFavouritesToggle = useCallback(() => {
-  const variantIdsToChange = selectedProductVariants;
-  if (nextFavouriteAction === FavouriteAction.Favourite) {
-    mutateAddFavourites(variantIdsToChange);
-  } else {
-    mutateRemoveFavourites(variantIdsToChange);
-  }
-}, [mutateRemoveFavourites, mutateAddFavourites, nextFavouriteAction, selectedProductVariants]);
-```
-### Example: Exporting favorites to CSV
-```ts
-const onExportSelectedItemCSV = useCallback(() => {
-  const exportedInventoryItems = inventoryItems.filter(item =>
-    selectedProductVariants.includes(item.variantId)
-  );
-  const csv = prepareFavoritesCSVData(exportedInventoryItems);
-  const filename = `Favorites-${formatDate(new Date())}.csv`;
-  exportToCsv(csv, filename);
-}, [inventoryItems, selectedProductVariants]);
-```
-
-## API and Interfaces
-
-### Mutations
-- **`useAddInventoryItemsFavouritesMutation`**: Adds specified product variants to favorites.
-- **`useRemoveInventoryItemsFavouritesMutation`**: Removes specified product variants from favorites.
-- **`useCreatePurchaseOrderMutation`**: Creates a purchase order from a list of variant IDs.
-
-### Queries
-- **`useGetInventoryItemsQuery` with favorite filter**: Retrieves inventory items marked as favorites.
-
-### Backend Service: FavouritesService
-- Responsible for efficient batch updates of favorite flags on product variants.
-- Implements differential updates (adds and removes) to sync user's current favorite selections.
-
-## Environment & Configuration
-
-No explicit environment variables or secrets related to Favorites are detailed in the provided context.
-
-## Testing, Monitoring, and Deployment
-
-No specific information on testing, monitoring, or deployment practices related to the Favorites feature is provided.
-
-## Troubleshooting & Known Issues
-
-No documented issues or troubleshooting steps are available for this component.
-
-## Usage Example
-
-Users interact with the Favorites page to:
-
-- Search and filter favorite products using pre-configured filter options.
-- Select multiple favorite variants using UI cards.
-- Toggle favorite state for selected items in bulk.
-- Export selected or all favorites to CSV.
-- Create new or add to existing purchase orders from selected favorites.
-
-## Summary
-
-The Favorites & User Preferences feature provides an integrated and streamlined approach for users to manage their priority inventory items efficiently. It leverages React hooks and modular API operations to maintain state and synchronize with backend services while providing typical inventory actions specialized for favorites.
-
-This functionality is crucial for workflows that prioritize commonly used or monitored products, easing downstream operations such as procurement.
-
----
-
-## References
-
-- [Favorites Component Source](apps/web/src/components/pages/favorites/index.tsx)
-- [Favorites Hooks](apps/web/src/components/pages/favorites/hooks.ts)
-- [Favorites Backend Service](apps/api/src/pim/services/favourites.service.ts)
-- [Inventory Actions Hook](apps/web/src/hooks/use-inventory-actions.ts)
-- [Inventory Table Actions](apps/web/src/components/pages/inventory/table-actions.tsx)
-
----

package/docs/usage/ui-workflows/inventory-management.mdx

@@ -1,179 +0,0 @@
----
-title: 'Inventory Management'
-description: 'How to manage inventory items, views, filters, and performing actions like excluding products or changing status.'
----
-
-## Inventory Management Service
-
-### Purpose and Scope
-The **InventoryService** is a core backend module responsible for managing inventory data within the Genie application. It handles the retrieval, filtration, enrichment, and export of inventory items for a given team. This service solves challenges around accurate and efficient access to inventory metrics, stock status, historical data, and integration with purchase orders.
-
-This service is situated within the Product Information Management (PIM) subsystem and interfaces directly with database repositories (e.g., `InventoryItemEntity`, `InventoryItemHistoryEntity`), other domain services such as purchase orders, assets, and email, and external Shopify integrations.
-
-
-### Technical Overview
-
-The service uses the NestJS framework and TypeORM for database access. It codifies complex business logic primarily through database views (e.g., `inventory_item` view) and sophisticated TypeORM query builders.
-
-Key dependencies:
-- TypeORM Repositories: Inventory items, Product Variants, Inventory Item History.
-- Other services: `PurchaseOrdersService`, `EmailService`, `AssetsService`.
-- Shared utilities and types from the `@genie/shared` package.
-
-The service encapsulates queries with filter and sort capabilities, supports bulk operations on ignored variants, handles inventory history synchronization, and supports item export functionality.
-
-#### Key Technologies & Patterns
-- **NestJS**: Modular dependency injection and service structure.
-- **TypeORM**: SQL view-based entities and complex dynamic query building.
-- **SQL Views**: Centralized inventory item state computation in `inventory_item` view.
-- **Batch Processing**: For large exports and history sync operations.
-
-### Core Concepts and Responsibilities
-
-- **Inventory Items:** Represent products or product variants with stock quantities, sales data, status (e.g., running low, out of stock), and metadata (e.g., suppliers, locations).
-
-- **Filters and Sorting:** Custom filters support multiple operators and field types, allowing precise querying.
-
-- **Historical Data:** Maintains snapshots of inventory state over time for reports and analysis.
-
-- **Stock Metrics:** Calculates key metrics such as days to out of stock, days to order, grading levels, and stock status.
-
-- **Integration Points:** Interfaces with purchase order data for in-transit quantities, supplier data, and Shopify inventory levels.
-
-- **Exports:** Supports asynchronous export of full inventory lists to CSV stored in S3, with email notification.
-
-
-### Code Structure
-
-- **InventoryService (apps/api/src/pim/services/inventory.service.ts):**
-  Primary service class implementing all core inventory functions.
-
-- **InventoryItemEntity (apps/api/src/pim/entities/inventory-item.entity.ts):**
-  TypeORM view entity mapping to the `inventory_item` SQL view for inventory data.
-
-- **Migrations (in `apps/api/src/migrations/db/`):**
-  Manage schema and view updates related to inventory data, e.g., adding suppliers, locations, and adjusting stock calculations.
-
-- **Supporting Components:**
-  Includes repositories for entity persistence and utilities for filtering and processing.
-
-**Example of bulk action method for getting inventory items:**
-```ts
-async getInventoryItems<T extends InventoryItemSelect[]>(
-  teamId: string,
-  options: GetInventoryItemsRequestDto
-): Promise<[InventoryItem<T>[], number]> {
-  // Performs queries with filtering, sorting, pagination
-}
-```
-
-### API and Interfaces
-
-- **getInventoryItems(teamId, options):**
-  Fetch inventory items by team with options for filters, sorting, pagination, search terms, and selected fields.
-
-- **getToBuyInventoryItems(teamId, request):**
-  Retrieve inventory variants that need to be restocked, with sorting and filtering tailored to buying criteria.
-
-- **addToBuyIgnore(teamId, variantIds, ignoreUntil):**
-  Mark specific variants to be ignored in to-buy calculations until a specified date.
-
-- **removeFromToBuyIgnore(teamId, variantIds):**
-  Removes variants from the ignore list.
-
-- **syncHistory(teamId):**
-  Sync persistent inventory snapshots from current live data to history table for trend analysis.
-
-- **exportAllInventoryItems(teamId, userEmail, columns):**
-  Initiates export of all inventory items data to CSV in S3 and emails download link to user.
-
-**Request/Response shapes are strongly typed using `@genie/shared` DTOs and Types.**
-
-### Environment & Configuration
-
-The service relies on environment and config such as:
-- `DATA_SYNC_TIMEZONE` used in history synchronization for consistent time zones.
-- S3 bucket config via `AssetsService` for exporting CSV files.
-
-Specific env vars beyond this are not present in the context.
-
-### Testing, Monitoring, and Deployment
-
-Testing and monitoring strategies are not detailed in provided info.
-
-### Troubleshooting & Known Issues
-
-No explicit troubleshooting guidance or known issues are documented in the current context.
-
-### Inventory Item View (`inventory_item`)
-
-The `InventoryItemEntity` is based on a complex SQL view that consolidates data from product variants, supplier info, purchase orders, tags, locations, and other metadata to provide a comprehensive snapshot of inventory status.
-
-Key calculated fields include:
-- **quantity:** Adjusted for synced and unsynced stock quantities.
-- **daysToOutOfStock:** Estimated days until stock depletion, considering incoming shipments.
-- **daysToOrder:** Days to reorder based on safety buffers.
-- **gradingLevel/Percent/Value:** Performance grades based on configurable strategies.
-- **status:** Overall stock health (e.g., RUNNING_LOW, OUT_OF_STOCK, OVERSTOCKED).
-- **incomingQuantity:** Stock expected from purchase orders.
-- **locationQuantities:** Stock quantities segmented by physical locations.
-- **suppliers:** List of associated suppliers.
-
-This view is maintained via multiple migration scripts enhancing it progressively to include new metrics like gross margin, location quantities, suppliers, product shopify categories, and more.
-
-### Integration Overview
-
-- Interacts closely with **PurchaseOrdersService** to enrich inventory data with in-transit quantities and upcoming shipments.
-- **EmailService** is used to deliver export notifications.
-- **AssetsService** handles persisting CSV files in S3.
-- Queries integrate with **Shopify API** for accurate product and inventory information.
-
-### Mermaid Diagram
-
-```mermaid
-flowchart TD
-  subgraph "API Layer"
-    InventoryService["InventoryService"]:::service
-  end
-
-  subgraph "Database Layer"
-    InventoryItemEntity["InventoryItemEntity (inventory_item view)"]:::database
-    InventoryItemHistoryEntity["InventoryItemHistoryEntity"]:::database
-    ProductVariantEntity["ProductVariantEntity"]:::database
-    ProductVariantBuyIgnoreEntity["ProductVariantBuyIgnoreEntity"]:::database
-    TeamEntity["TeamEntity"]:::database
-  end
-
-  subgraph "Supporting Services"
-    PurchaseOrdersService["PurchaseOrdersService"]:::service
-    EmailService["EmailService"]:::service
-    AssetsService["AssetsService"]:::service
-    ShopifyProductsService["ShopifyProductsService"]:::service
-  end
-
-  InventoryService -->|reads/writes| InventoryItemEntity
-  InventoryService -->|reads/writes| InventoryItemHistoryEntity
-  InventoryService -->|reads/writes| ProductVariantEntity
-  InventoryService -->|manages ignore list| ProductVariantBuyIgnoreEntity
-  InventoryService -->|fetches team config| TeamEntity
-  InventoryService -->|enriches data| PurchaseOrdersService
-  InventoryService -->|sends export notifications| EmailService
-  InventoryService -->|uploads export files| AssetsService
-  PurchaseOrdersService -->|relies on| InventoryItemEntity
-  InventoryService -->|integrates for product info| ShopifyProductsService
-
-  %% Click Events for navigation
-  click InventoryService "apps/api/src/pim/services/inventory.service.ts"
-  click InventoryItemEntity "apps/api/src/pim/entities/inventory-item.entity.ts"
-  click PurchaseOrdersService "apps/api/src/purchase-order/services/purchase-orders.service.ts"
-  click EmailService "apps/api/src/email/services/email.service.ts"
-  click AssetsService "apps/api/src/asset/services/assets.service.ts"
-  click ShopifyProductsService "apps/api/src/shopify/services/shopify-products.service.ts"
-
-  classDef service fill:#ffcc00,stroke:#333,stroke-width:1.5px,color:#000
-  classDef database fill:#66ccff,stroke:#333,stroke-width:1.5px,color:#000
-
-  %% Style guide
-  class InventoryService,PurchaseOrdersService,EmailService,AssetsService,ShopifyProductsService service
-  class InventoryItemEntity,InventoryItemHistoryEntity,ProductVariantEntity,ProductVariantBuyIgnoreEntity,TeamEntity database
-```