Customer Sync - commercetools Connector

Data Pipeline Execution

1. Storefront Trigger (Subscription/External Queue)

• Stage 1 (CT-Queue Ingestion): Any customer creation or modification fires a native commercetools subscription event that pushes the notification payload out to an external `ct-queue`. Out of the box, the connector implements AWS Event Bridge for this layer, though it can be implemented with any other queues or subscriptions supported by commercetools. More details on commercetools subscription. 
• Stage 2 (Internal Queueing): The `CT Queue Listener` class constantly monitors and reads incoming messages directly from the `ct-queue` and pushes them directly to the internal Event Queue, which safely holds the transient event messages to prepare them for downstream evaluation.

2. Route Filtering & Message Routing

• Stage 3 (Message Routing): The internal Message Router evaluates the message name and `typeId` extracted from the Event Queue to pass it to the appropriate handler. In the case of customer updates, the message `typeId` resolves to `customer`, which dynamically triggers a match against the `commercetools.connect.customer.upsert` route.  Please refer commercetools Customer Messages for more information on supported messages.

3. Fluent API Delivery (GraphQL Mutation)

• Stage 4 (Handler Processing & Delivery): The Customer Updates Handler reads the payload from the internal queue. Based on the unique customer identifier, the handler extracts extra details from the core Commercetools-SDK (which interacts directly with commercetools APIs), transforms and maps the attributes to the Fluent data model, and dispatches the profile directly to Fluent Order Management.

Data Storage & Schema Mapping

Core commercetools Customer API Endpoints

• `GET : {{host}}/{{project-key}}/customers`
• `GET : {{host}}/{{project-key}}/customers/{{Customer-id}}`

Developer Extension Points

Message Routing Configuration (`application-connector.yml`)

1- route: "commercetools.connect.customer.upsert"
2     props:
3       name: "customer"
4       inclusion-filter:
5          - "ResourceUpdated"
6          - "ResourceCreated"

Custom Message Handler Implementation

1@Slf4j
2@Component
3@HandlerInfo(name = "FluentCustomerUpsert")
4public class FluentCustomerCreateHandler extends MessageHandler {
5    private static final String CUSTOMER_ATTRIBUTE = "customer";
6    // write your logic
7}

Customer Message Payload Reference

1{
2  "notificationType": "Message",
3  "projectKey": "fluent-ct-dev",
4  "id": "85c1c53e-75c8-413a-b8f5-08701292486e",
5  "version": 1,
6  "sequenceNumber": 3,
7  "resource": {
8    "typeId": "customer",
9    "id": "14a4ef54-957d-4148-b0be-de8d0fbc411d"
10  },
11  "resourceVersion": 3,
12  "resourceUserProvidedIdentifiers": {},
13  "type": "CustomerDeleted",
14  "createdAt": "2022-07-27T06:11:11.021Z",
15  "lastModifiedAt": "2022-07-27T06:11:11.021Z"
16}