Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Inbound | POST  | /orders/search

Summary Copy to clipboard

  • This API allows the POS system to fetch order details.

  • The POS system can fetch orders of different statuses from SFS. The useful order statuses are ACCEPTED, PARTIALLY_ACCEPTED, PICKING_STARTED, and PICKING_COMPLETED.

  • This feature helps users quickly filter and locate orders that require attention. Users can do billing in POS based on order status.

Description

This API can be used to search the orders of a store based on these parameters:
i) locationCode
ii) eventTypes

 

Request

Code Block
languagejson
{
  "locationCode": "loc1",
  "minId": 123,
  "batchSize": 500,
  "eventTypes": [
    "OUTWARD_ORDER_COMPLETE"
  ]
}

Store Order Event Type

Code Block
{
    OUTWARD_ORDER_COMPLETE,
    OUTWARD_ORDER_CANCEL,
    OUTWARD_ORDER_PARTIAL_CANCEL,
    OUTWARD_ORDER_CREATE,
    OUTWARD_ORDER_DELIVER,
    SUBORDER_CREATE,
    SUBORDER_COMPLETE,
    SUBORDER_CANCEL,
    SUBORDER_DELIVER,
    SUBORDER_PARTIAL_CANCEL,
    PICK_LIST_RELEASE,
    PICK_LIST_UPDATED,
    ACCEPTED,
    REJECTED,
    PARTIALLY_ACCEPTED,
    PICKING_STARTED,
    PICKING_COMPLETED,
    PACKED
}

...

Parameter Name

Data Type

Description

Mandatory

locationCode

String

Location code of the warehouse in which we are searching the orders

yes

minId

String

Minimum event id greater than which the event (particularly for orders) will be searched

yes

batchSize

String

Max results the caller want, default value is 5000

no

eventTypes

String[]

The type of events for which orders in store can be searched(find the list of valid event types above)

yes

 

 

Response

Code Block
languagejson
{
  "searchStoreOrderDataList": [
    "eventId": 123,
    "locationCode": "loc1",
    "eventTime": "2023-04-24T05:55:35+05:30",
    "eventType": "PICKING_COMPLETED",
    "channelOrderId": "ch_id1",
    "channelId": "ch1"
  ]
}

...