Repository navigation
Conversation
Add optional fields to fulfillment_event.json that connect post-purchase tracking events back to checkout fulfillment selections: - fulfillment_method_id: references the method selected at checkout - fulfillment_option_id: references the specific option (e.g. express) - estimated_delivery: earliest/latest delivery window, revisable over time All fields are optional — backwards compatible. Closes Universal-Commerce-Protocol#347
Moves Checkout fulfillment carry-through from append-only fulfillment events to Order expectations, following the optional Checkout-snapshot pattern established by list_price (Universal-Commerce-Protocol#1016 / Universal-Commerce-Protocol#1031) and purchase_option (Universal-Commerce-Protocol#890): - Restore fulfillment_event.json to main. - Add optional earliest_fulfillment_time and latest_fulfillment_time (RFC 3339) on expectation.json for the current ready or arrival window. - Add optional fulfillment_option snapshot ( fulfillment_option.json) on expectation.json for the Checkout selection as it stood at purchase. - Document the normative snapshot contract in docs/specification/shopping/order/index.md.
|
Thanks @hemanth for opening #347 and putting up this PR, and sorry for the delay getting review eyes on it. Because I merged
We are flagging #347 / #617 as our featured Community Contribution in this Friday's Shopping Tech Council (Nov 20) to confirm direction and check whether |
Closes #347
Carries the Checkout fulfillment selection and delivery window onto Order expectations, the buyer-facing promise that exists from order creation (fulfillment events remain an append-only shipment log).
Changes
source/schemas/shopping/types/expectation.json:fulfillment_option($ref: "fulfillment_option.json"), a snapshot of the fulfillment option selected for these items at Checkout. Never updated if the promise changes, and itsidneed not still resolve. Ordertotalsremain authoritative.earliest_fulfillment_timeandlatest_fulfillment_time(RFC 3339) for the ready or arrival window, initially matching the selected Checkout option's window and updated if the promise changes (same field names asfulfillment_optionand foodorder_confirmationin feat: Introduce Food Checkout Capability and Fulfillment & Tip Extensions #897).docs/specification/shopping/order/index.md:description,earliest_fulfillment_time,latest_fulfillment_time) from fulfillment release timing (fulfillable_on).Fulfillment optionsnapshot contract under Expectations, mirroringlist_price(feat: add optional response-only list_price to item schema #1016 / docs: define list_price once as a reference price #1031),attribution, andpolicies.Motivation
Follows the optional Order snapshot pattern established by
list_price(#1016 / #1031) so Businesses that retain the selected Checkout fulfillment option can surface it on Order expectations without making it mandatory, while keeping the original Checkout promise separate from later post-purchase updates (as requested on #347 and #532). Drops the earlier event-level fields (fulfillment_method_idwas redundant withmethod_typeanddestination).