Ecommerce events specification ambiguity for Checkout Started properties order_id

[OmG3r]

Summary

the Ordering section in Ecommerce events specification denotes the steps of how the spec considers an order sequence (Checkout Started is before Payment Info Entered)

Currently the event Checkout Started requests an order_id with description "Order ID or transaction ID, whichever is applicable" ( which is not logical to me because an order is not yet created at this stage on most ecommerce platforms).

then Checkout Step Viewed & Checkout Step Completed requests checkout_id with a description "Checkout transaction ID" (which is logical for me because an order is not yet created).

Payment Info Entered requests a checkout_id and an order_id (which is logical to me because an order is most likely created on most ecommerce platforms at this stage), additionally why is there a separation between checkout_id and order_id here, but not Checkout Started

I want to confirm that the order_id in Checkout Started is intentional (could not find confirmation throughtout the publicly available operational source code (cdp)).
if it is not a technical limitation or intentional, maybe we an rename the order_id to a checkout_id on Checkout Started event or add both fields

What kind of request is this?

• New docs page / feature
• Update to existing page
• Not sure

Which product is this for?

• Product OS (e.g. platform features)
• Product analytics
• Session replay
• Feature flags
• Experiments
• Surveys
• CDP
• Data warehouse
• Other (e.g. open source specific)

Is there a deadline for this change?

• Yes (please specify)
• No