Process Path Integration Documentation

Overview

This documentation describes how the Process Path bounded context integrates with all related domains in the Paklog fulfillment platform. Process Path is the strategic routing and orchestration system that determines how shipments flow through picking, packing, and shipping operations.

Quick Navigation

Event Catalog

API Contracts

Integration Specifications

Architecture Overview

System Overview

flowchart TD
    subgraph ProcessPath["PROCESS PATH CORE"]
        ROUTING[Routing Service]
        ORCH[Orchestration Service]
    end

    subgraph Paths["PATH SERVICES"]
        SINGLES[Singles Path<br/>Direct Pack]
        AFE[AFE Path<br/>Sorter-Based]
        BATCH[Batch/Flow Path<br/>Wave-Based]
    end

    subgraph Final["COMPLETION"]
        SLAM[SLAM Operations<br/>Label & Manifest]
        SHIP[Carrier Handoff]
    end

    ROUTING --> SINGLES
    ROUTING --> AFE
    ROUTING --> BATCH
    ORCH -.->|capacity signals| ROUTING

    SINGLES --> SLAM
    AFE --> SLAM
    BATCH --> SLAM
    SLAM --> SHIP

End-to-End Event Flow

sequenceDiagram
    participant OM as Order Management
    participant ROUTING as Routing Service
    participant ORCH as Orchestration Service
    participant PATH as Path Services
    participant SLAM as SLAM Operations
    participant SHIP as Transportation

    OM->>ROUTING: OrderReleasedToWarehouseEvent
    Note over ROUTING: Evaluate path options<br/>based on capacity & SLA

    ROUTING->>ORCH: Query capacity state
    ORCH-->>ROUTING: Capacity snapshot

    ROUTING->>PATH: ShipmentRoutedToPathEvent
    Note over PATH: Execute pick/pack<br/>operations

    PATH->>SLAM: Packing completed
    SLAM->>SHIP: SLAMCompletedEvent
    Note over SHIP: Manifest & carrier handoff

Path Service Integration

flowchart LR
    ROUTING[Routing Service] -->|ShipmentRoutedToPathEvent| FILTER{Path Type?}

    FILTER -->|SINGLES| SINGLES[Singles Path Service]
    FILTER -->|AFE| AFE[AFE Path Service]
    FILTER -->|BATCH| BATCH[Batch Flow Service]

    SINGLES -->|PackingCompletedEvent| SLAM[SLAM Operations]
    AFE -->|RebinCompletedEvent| SLAM
    BATCH -->|ConsolidationCompletedEvent| SLAM

    SLAM -->|SLAMCompletedEvent| SHIP[Transportation]

Integration Patterns Used

Published Language

Used when the upstream context owns the contract and we consume their well-defined events.

• Order Management: Orders and SLA requirements
• Wave Planning: Wave release and batch composition

Conformist

Used when we adapt to the upstream context’s model without negotiation.

• Inventory Service: Item properties and allocation data
• Workload Planning: Capacity forecasts and labor data
• Location Master: Warehouse topology and zone configuration

Customer-Supplier

Used when we provide services to downstream consumers.

• Task Execution Service: Work assignment coordination
• Shipment Transportation: SLAM completion and manifest data

Partnership

Used for bidirectional collaboration with shared goals.

• Pick Execution Service: Pick flow and throughput signals
• Pack & Ship Service: Packing triggers and completion events
• WES Orchestration Engine: Work release and capacity coordination
• Robotics Fleet Management: Robot task coordination

Open Host Service

Used when we expose a standardized interface for multiple consumers.

• Pack & Ship Service: Standardized packing triggers

Event Streaming

Used for continuous flow of operational events.

• Physical Tracking Service: Real-time location updates

Technology Stack

Key Metrics

Document Conventions

Event Naming

• Format: com.paklog.{context}.{aggregate}.{action}.v{version}
• Example: com.paklog.processpath.shipment.routed.v1

API Versioning

• Path-based: /api/v1/...
• Header-based for minor versions: X-API-Version: 1.1

Kafka Topics

• Format: {context}.{aggregate}.{event-type}
• Example: process-path.routing.events

Implementation Status

The following table shows the implementation status of each Process Path service integration.

Services Implemented

Events Published (12 Total)

Events Consumed (20 Total)

Shared Components (process-path-commons)

The commons library provides shared infrastructure:

Change Log