# Order Event Notifications Fynd Konnect's event-driven notification system enables real-time order and return updates to your OMS, WMS, ERP, or POS systems whenever critical state changes occur for a shipment in Fynd Commerce. Instead of relying on periodic API polling, our notification system pushes shipment data instantly to your configured endpoints, significantly reducing latency and improving operational efficiency. #### Why Use Konnect's Order Event Notifications? * **Instant Data Sync**: Your systems receive updates immediately instead of waiting for scheduled cron jobs or manual polling intervals * **Reduced Latency**: Process orders faster by receiving notifications the moment they are placed, invoiced, canceled, or dispatched * **Lower Server Load**: Eliminate continuous API polling, reducing infrastructure costs and API rate limit concerns * **Event-Driven Architecture**: Build reactive systems that respond instantly to order lifecycle changes * **Improved Customer Experience**: Faster order processing translates to quicker fulfillment and delivery times ## Available Event Triggers Configure notification subscriptions for any of the following order lifecycle events: | **Event Trigger** | **Event Description** | **Equivalent GET Orders' `orderStatus` query param** | | --- | --- | --- | | `new` | Upcoming order on Fynd OMS | CREATED | | `placed` | Order placed by customer on storefront or marketplace and received by Fynd | CREATED | | `cancelled_customer` | Order canceled by customer before store confirmed fulfillment | CANCELLED | | `cancelled_fynd` | System-initiated cancellation by Fynd (e.g., inventory mismatch, business rules) | CANCELLED | | `store_reassigned` | Order reassigned to alternate fulfillment location due to the lack of inventory in the original fulfillment location | CREATED | | `bag_confirmed` | Store/warehouse confirms order after inventory check and begins picking | CONFIRMED | | `bag_invoiced` | Invoice generated for the packed order | PROCESSING | | `dp_assigned` | Delivery partner (courier) assigned to the order | PROCESSING | | `bag_packed` | Packing complete; bag is boxed and ready for courier pickup | COMPLETED | | `handed_over_to_dg` | Package handed over to delivery group/logistics network (when aggregator sends dispatch call via Order Dispatch API) | TRANSIT | | `bag_picked` | Courier picks up packaged order from store (when Fynd marks dispatched after receiving bag-pick call from delivery partner) | TRANSIT | | `delivery_done` | Bag successfully delivered to customer | DELIVERED | | `return_initiated` | Customer initiates return request after delivery | RETURN_PROCESSING | | `return_in_transit` | Return package picked up by courier and in transit back to store | RETURN_PROCESSING | | `return_bag_delivered` | Return package arrived back at store/warehouse | RETURN_DELIVERED | | `return_accepted` | Return stockpoint accepts return bag after QC | RETURN_COMPLETED | | `rto_initiated` | Return-to-origin process initiated by courier due to failed delivery | RETURN_PROCESSING | | `rto_in_transit` | RTO shipment in transit back to origin store/warehouse | RETURN_PROCESSING | | `rto_bag_delivered` | RTO package delivered back to store/warehouse | RETURN_DELIVERED | | `rto_bag_accepted` | Store/warehouse accepts RTO package after QC | RETURN_COMPLETED | | `credit_note_generated` | Credit note (reverse invoice) generated after successful return or RTO acceptance | CREDIT_NOTE_GENERATED | ## How It Works? #### Notification Flow 1. **Event Occurs**: Order state changes in Fynd OMS (e.g., `bag_confirmed` → `bag_invoiced`) 2. **Notification Triggered**: Fynd Konnect sends a POST request with shipment payload to your configured endpoint 3. **Your System Processes**: Your OMS/WMS/ERP/POS receives and processes the data in real-time 4. **Response**: Your endpoint returns a success status to acknowledge receipt #### Request Structure - **HTTP Method**: `POST` - **Headers**: - Optional: Custom authentication headers (if configured) - **Payload**: Complete Fynd Konnect order payload in JSON format ## Configuration Steps 1. **Access Fynd Konnect Channel**: Navigate to your **Fynd Commerce** panel and click **Extensions** from the left sidebar. Locate and click **Fynd Konnect** from the channels list. Fynd Konnect Channel center em Figure 1: Fynd Konnect Channel br 1. **Manage Channels**: From the Fynd Konnect dashboard, click **Manage Channels** to view all configured seller channels. Creating New Channels To create a new OMS/WMS/ERP/POS channel, contact the Fynd Konnect team Manage Channels center em Figure 2: Manage Channels br 1. **Configure Your Channel**: Identify your target channel and click the **Configure** button. Configure Your Channel center em Figure 3: Configure Your Channel br 1. **Activate Selling Locations**: In the channel configuration page, navigate to the **Selling Location** tab. Activate the fulfillment locations for which you want to enable event notifications. Only shipments originating from selected locations will trigger notifications. Activate Selling Locations center em Figure 4: Activate Selling Locations br 1. **Configure Event Triggers**: Click the **Event Triggers** tab to view all available events. Select the event you want to subscribe to (e.g., `placed`, `bag_confirmed`, `delivery_done`). Configure Event Triggers center em Figure 5: Configure Event Triggers br 1. **Set Up Notification Endpoint**: In the event configuration screen: * **Destination URL**: Enter your system's notification endpoint URL * **Custom Headers** (optional): * Enable the Custom Header checkbox if authentication is required * Add header key-value pairs (e.g., `Authorization: Bearer token`) * Click **+ Add more** for additional headers * **Activate**: Toggle the event configuration to enable * **Save**: Click Save to apply the configuration Set Up Notification Endpoint center em Figure 6: Set Up Notification Endpoint ## Notification Payload #### Key Response Fields #### Example Notification Payload (`placed` Event) ```json { "returnInvoiceNumber": "", "forwardId": "17619157236111900000", "sellerInvoiced": false, "orderStatus": "CREATED", "fulfillmentType": "marketplaceFulfilled", "orderItems": [ { "quantity": 1, "itemTags": [], "onHold": false, "productId": "FYND22940", "orderItemId": "46559821", "imeiSerialNumberNeeded": false, "title": "KonnectTest1234", "imeiSerialNumber": [], "returnConfig": { "time": 14, "unit": "days", "returnable": true }, "productIdentifiers": { "ean": "FYND22940" }, "shippingMethodCode": "STD", "marketplaceOrderItemId": "46559821", "packetNumber": 0, "variantId": "XL", "locationCode": "TEST02", "sku": "FYND22940", "orderItemPrice": { "couponDiscount": 0, "giftWrapCharges": 0, "sellingPrice": 1750, "cashOnDeliveryCharges": 0, "totalMarkedPrice": 2000, "marketplacePromotionDiscount": 0, "shippingCharges": 0, "sellerPromotionDiscount": 0, "discount": 250, "currency": "INR", "totalItemPrice": 1750, "transferPrice": 0 }, "gstDetails": { "taxPercentage": { "SGST": 2.5, "CGST": 2.5 }, "taxAmount": { "SGST": "41.67", "CGST": "41.67" } }, "status": "placed", "customAttributes": { "_display": [] } } ], "paymentType": "COD", "lockStatus": false, "orderBusinessType": "B2C", "additionalInfo": "You can add additional info here", "invoiceNumber": "", "orderPrice": { "orderTotalAmount": 1750, "codAmount": 1750, "currency": "INR" }, "id": "17619157236111900000", "invoiceGenerationDate": "", "marketplaceOrderId": "FY6904B34B1321FD3258", "multiPackShipment": false, "orderingChannel": "TESTCHANNEL", "shipmentTags": [], "sla": "2025-11-02T24:02:04+05:30", "packages": [ { "packageWidthCm": 34.29, "packageId": "P1", "packageLengthCm": 43.18, "packageWeightGms": 3000, "packageHeightCm": 11 } ], "pickUpSlots": [], "awbNumber": [], "orderTags": [], "journeyType": "forward", "cFormProvided": false, "is_self_ship": true, "modifiedDate": "2025-10-31T18:32:04+00:00", "shippingAddress": { "country": "India", "pincode": "400093", "city": "Mumbai", "phone": "9999999999", "name": "John Doe", "addressLine1": "Fynd, WeWork Vijay Diamond", "state": "Maharashtra", "email": "test@gmail.com" }, "taxExempted": false, "billingAddress": { "country": "India", "pincode": "400093", "city": "Mumbai", "phone": "9999999999", "name": "John Doe", "addressLine1": "Fynd, WeWork Vijay Diamond", "state": "Maharashtra", "email": "test@gmail.com" }, "orderDate": "2025-10-31T18:32:04+00:00" } ``` ## Event Analytics & Monitoring The **Order Analytics** section provides comprehensive visibility into all event notifications between Fynd Platform and your integrated systems. This centralized dashboard enables you to track, troubleshoot, and analyze real-time data exchanges, ensuring quick resolution of any notification delivery issues. Event logs are retained for up to **1 month**, providing sufficient historical data for debugging and audit purposes. 1. **Accessing Order Analytics**: From the Fynd Konnect dashboard, click **Order Analytics** to access the Event Reports section where all notification activity is logged. Accessing Order Analytics center em Figure 7: Accessing Order Analytics br 1. **Viewing Event Reports**: The Event Reports table displays all notification payloads with the following information: * **Channel**: The configured integration channel (e.g., TEST Channel) * **Category**: Channel type (e.g., ERP Integrations, POS Integrations) * **Report Label**: Event type (e.g., `placed`, `bag_picked`, `delivery_done`) 2. **Search and Filter Options** * **Search by Shipment Id**: Enter shipment identifier to view all triggered events for that shipment * **Search by Label**: Filter by event name to see all shipments for a specific event type * **Category**: Filter by channel category * **Status**: Filter by SUCCESS or FAILED events * **Date Range**: Select custom date range to narrow results Event Reports center em Figure 8: Event Reports br 1. **Comprehensive Log Details**: Click the **info icon (ⓘ)** in the **Comprehensive Log** column for any event to view: * **Request URL**: Target notification endpoint * **Request Parameters**: All custom headers sent * **Request Body**: Complete JSON payload sent to your system * **Response**: Response received from your endpoint (visible for both success and failures) * **Status**: SUCCESS or FAILED badge for quick identification Comprehensive Log center em Figure 9: Comprehensive Log #### Retrying Failed Notifications For failed notification deliveries: 1. **Automatic Retries**: Fynd Konnect automatically retries at scheduled intervals 2. **Manual Retry**: Click **Retry Event** button in the Action column to immediately resend the notification 3. **Exhausted Retries**: If the Retry Event button is disabled, automatic retry attempts have been exhausted. Contact Fynd Support team to manually re-emit the notification ## Best Practices * **Endpoint Reliability**: Ensure your notification endpoint has high availability and responds within 5 seconds * **Idempotency**: Design your system to handle duplicate notifications gracefully using the shipment `id` as a unique identifier * **Error Handling**: Return appropriate HTTP status codes (200-299 for success, 4xx/5xx for failures) to enable automatic retries * **Security**: Always use HTTPS endpoints and implement authentication via custom headers * **Monitoring**: Regularly review the Event Analytics dashboard to identify and resolve delivery issues promptly