From 23f651e4235cb2abd9e4a6df8f464e950399be02 Mon Sep 17 00:00:00 2001
From: Bhavika Sehgal <133744950+Bhavika42@users.noreply.github.com>
Date: Mon, 24 Mar 2025 19:18:29 +0530
Subject: [PATCH] Update Order.yaml

Added Order.state field to track order lifecycle stages
---
 schema/Order.yaml | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/schema/Order.yaml b/schema/Order.yaml
index 3253c4cf..837a9363 100644
--- a/schema/Order.yaml
+++ b/schema/Order.yaml
@@ -17,6 +17,17 @@ properties:
       - ACTIVE
       - COMPLETE
       - CANCELLED
+  state:
+    description: The current state of the order in the order lifecycle. Helps track order progress beyond just status.
+    type: string
+    enum:
+      - CREATED
+      - PACKED
+      - SHIPPED
+      - DELIVERED
+      - RETURN_REQUESTED
+      - RETURNED
+      - FAILED
   type:
     description: This is used to indicate the type of order being created to BPPs. Sometimes orders can be linked to previous orders, like a replacement order in a retail domain. A follow-up consultation in healthcare domain. A single order part of a subscription order. The list of order types can be standardized at the network level.
     type: string
@@ -100,4 +111,4 @@ properties:
   tags:
     type: array
     items:
-      $ref: "./TagGroup.yaml"
\ No newline at end of file
+      $ref: "./TagGroup.yaml"