Fluent Commerce Logo
Docs

Basic Knowledge

Essential knowledge articles on Connect SDK

Consignment Updates - commercetools Connector

Essential knowledge
The Consignment Updates module tracks shipping and delivery events from Fluent Order Management and synchronizes them to commercetools. When fulfillment actions conclude on the backend, the module processes outbound consignment statuses using secure webhooks. The connector captures these real-time operational milestones to automatically generate matching delivery structures, parcel data, and tracking identification links within the storefront interface.
  • What You Will Learn: You will understand how the connector processes Fluent Order Management consignment webhooks, translates data into storefront delivery objects, and injects parcel carrier tracking data.
  • Structural Entity Mapping: The consignment entity on the Fluent Order Management side maps directly onto the fulfillment entity model, which translates into native delivery records within commercetools.
  • Two-Stage Processing Framework: Inbound webhook payloads undergo initial signature verification and parameter validation in Stage 1 before passing to an internal queue. Stage 2 executes the specific named handler logic asynchronously.
  • Data Enrichment Mechanism: Because inbound webhooks transmit minimal data payloads to minimize overhead, the connector performs an automated backend GraphQL query to pull comprehensive shipment attributes from Fluent Order Management.
  • Granular Architectural Extensibility: Developers can extend code functionality or override default logic by registering custom message handlers within the `commercetools-connector` framework to track specialized downstream data points.

Connect SDK - Fluent Webhooks Integration

Essential knowledge
The Fluent Connect SDK offers seamless integration with Fluent Webhooks, enabling you to receive messages and perform various actions based on incoming calls. This document provides an overview of the core features of the Fluent Connect SDK and outlines the steps to integrate it into your application. Go here to read about Fluent Webhooks.
  • Standardized Webhook Ingestion: You will learn how the Connect SDK natively exposes a dedicated endpoint (`/api/v1/fluent-connect/webhook`) to receive inbound HTTP calls from Fluent Webhooks, automatically transforming raw payloads into the SDK's internal message queue format for scalable processing.
  • Automated Signature Verification: To protect the authenticity and integrity of system interactions, the SDK automatically runs signature validation checks on all incoming messages using environment-specific public keys pre-configured within the `application.yml` file.
  • Routing & Handler Dependencies: An important operational consideration is that an inbound webhook payload will only execute successfully if its event name explicitly corresponds to a designated internal message handler and an active, matching configuration route.
  • Local Development Tunnels: Because local execution environments (`localhost:8080`) are isolated from the internet, developers testing live Fluent workflows locally must utilize a secure tunneling utility like `ngrok` to create a publicly accessible URL that safely routes traffic back to the local webhook endpoint.

Connect SDK Libraries

Essential knowledge
The Connect SDK Libraries comprise a modular software development framework designed for building integrations with Fluent Order Management. The architecture centers around a mandatory core module that handles foundational communication, configuration storage, and routing capabilities. Implementation teams can extend this baseline engine using specialized, pluggable add-on libraries to introduce web frameworks, security filters, specific cloud or infrastructure adapters, and isolated simulation testing suites.
  • What You Will Learn: You will understand the structural purpose of each component within the Connect SDK framework and learn how to select the appropriate core, web, cloud infrastructure, or testing dependencies for your implementation project.
  • Mandatory Core Requirement: The `connect-sdk-core` library is a mandatory dependency for all SDK-based implementations. It houses the baseline engine components, including the REST and GraphQL API client, authentication management for sensitive credentials, message routing, and the configuration manager.
  • Asynchronous Processing Boundary: All transactional endpoints and internal processing steps handled by the SDK execute asynchronously in the background. The explicit exception to this design rule is product availability processing, which runs synchronously.
  • Pluggable Architecture Strategy: Advanced technical capabilities are intentionally isolated into decoupled modules. Developers append specialized add-ons like `connect-sdk-core-web-security` for Spring Security filters, `connect-sdk-core-aws` for Amazon Web Services (AWS) deployment services like Amazon Simple Queue Service (SQS) and AWS Secrets Manager, or `connect-sdk-core-kafka` for Apache Kafka support.
  • Isolated Testing Frameworks: The SDK segregates quality assurance utilities into specific test scopes. Teams deploy `connect-sdk-test-core` to mock external API calls with Wiremock, or utilize the AWS and Kafka test extensions to run integration tests inside software containers alongside LocalStack or virtual Kafka brokers.