Skip to content

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 DescriptionEquivalent GET Orders' orderStatus query param
newUpcoming order on Fynd OMSCREATED
placedOrder placed by customer on storefront or marketplace and received by FyndCREATED
cancelled_customerOrder canceled by customer before store confirmed fulfillmentCANCELLED
cancelled_fyndSystem-initiated cancellation by Fynd (e.g., inventory mismatch, business rules)CANCELLED
store_reassignedOrder reassigned to alternate fulfillment location due to the lack of inventory in the original fulfillment locationCREATED
bag_confirmedStore/warehouse confirms order after inventory check and begins pickingCONFIRMED
bag_invoicedInvoice generated for the packed orderPROCESSING
dp_assignedDelivery partner (courier) assigned to the orderPROCESSING
bag_packedPacking complete; bag is boxed and ready for courier pickupCOMPLETED
handed_over_to_dgPackage handed over to delivery group/logistics network (when aggregator sends dispatch call via Order Dispatch API)TRANSIT
bag_pickedCourier picks up packaged order from store (when Fynd marks dispatched after receiving bag-pick call from delivery partner)TRANSIT
delivery_doneBag successfully delivered to customerDELIVERED
return_initiatedCustomer initiates return request after deliveryRETURN_PROCESSING
return_in_transitReturn package picked up by courier and in transit back to storeRETURN_PROCESSING
return_bag_deliveredReturn package arrived back at store/warehouseRETURN_DELIVERED
return_acceptedReturn stockpoint accepts return bag after QCRETURN_COMPLETED
rto_initiatedReturn-to-origin process initiated by courier due to failed deliveryRETURN_PROCESSING
rto_in_transitRTO shipment in transit back to origin store/warehouseRETURN_PROCESSING
rto_bag_deliveredRTO package delivered back to store/warehouseRETURN_DELIVERED
rto_bag_acceptedStore/warehouse accepts RTO package after QCRETURN_COMPLETED
credit_note_generatedCredit note (reverse invoice) generated after successful return or RTO acceptanceCREDIT_NOTE_GENERATED

How It Works?

Notification Flow

  1. Event Occurs: Order state changes in Fynd OMS (e.g., bag_confirmedbag_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
Figure 1: Fynd Konnect Channel

  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
Figure 2: Manage Channels

  1. Configure Your Channel: Identify your target channel and click the Configure button.
Configure Your Channel
Figure 3: Configure Your Channel

  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
Figure 4: Activate Selling Locations

  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
Figure 5: Configure Event Triggers

  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
Figure 6: Set Up Notification Endpoint

Notification Payload

Key Response Fields

idstring

Unique shipment identifier. Use this to track the shipment across all order operations

forwardIdstring

Forward shipment ID. Same as id for forward orders; a unique shipment ID is created for returns and cancellations

marketplaceOrderIdstring

Marketplace or webstore specific order identifier generated by the sales channel

returnInvoiceNumberstring

Credit note or return invoice number generated for returns/RTOs (empty for forward orders)

orderStatusstring

Current status of the entire shipment (e.g., CREATED, CONFIRMED, PROCESSING, DELIVERED, RETURN_DELIVERED)

orderDatestring(date-time)

UTC timestamp when the order was placed by the customer

modifiedDatestring(date-time)

UTC timestamp of the last status change for this shipment

invoiceGenerationDatestring(date-time)

UTC timestamp when the invoice was generated (empty if not yet invoiced)

shippingAddressobject

Customer's delivery address details where the order will be shipped

billingAddressobject

Customer's billing address (same structure as shippingAddress)

orderPriceobject

Shipment-level pricing and payment details

orderItemsArray of objects

List of product items (bags) included in this shipment

paymentTypestring

Payment method used (COD for Cash on Delivery, PREPAID for online payment)

fulfillmentTypestring

Fulfillment mode (marketplaceFulfilled or sellerFulfilled)

sellerInvoicedboolean

Indicates if the seller has generated an invoice for this shipment

invoiceNumberstring

Forward invoice number (empty if not yet invoiced)

packagesArray of objects

Physical package dimensions and weight information

multiPackShipmentboolean

Indicates if the shipment contains multiple packages

awbNumberArray of strings

List of Air Waybill numbers for tracking (populated after courier assignment)

orderingChannelstring

Sales channel name where the order originated (e.g., FYND, ECOMM, marketplace names)

journeyTypestring

Order journey type: forward (customer delivery) or return (return to seller)

is_self_shipboolean

Indicates if this is a self-ship order where seller manages logistics

slastring

Service Level Agreement - Order processing Turn Around Time deadline

lockStatusboolean

Indicates if the order is locked for processing (prevents modifications)

orderBusinessTypestring

Business transaction type (B2C for consumer, B2B for business orders)

taxExemptedboolean

Indicates if the shipment is tax-exempted

additionalInfostring

Additional notes or information about the shipment

shipmentTagsArray of strings

Configurable (on Fynd Commerce) tags or labels associated with the shipment (e.g., Hyperlocal, Express)

orderTagsArray of strings

Order-level tags for categorization or filtering

pickUpSlotsArray of objects

Available pickup time slots (for customer pickup orders)

cFormProvidedboolean

Indicates if C-Form has been provided for inter-state B2B sales

Example Notification Payload (placed Event)

{
  "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
Figure 7: Accessing Order Analytics

  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
Figure 8: Event Reports

  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
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