Hi @destpat ,
This sounds like a perfect use-case for metafields. It wouldn't be available at /orders/#[id}.json, but would be available at /orders/#[id}/metafields.json instead.
Is it still the case that MetaFields are the only way to store & Retrieve this Pickup information on an Order? I was hoping that I could determine which Orders are Pickup vs Shipping by reading the "requires_shipping" field in the JSON at either the Order or Line level - but when we mark an Order for Pickup in Store, this field still appears as "true" which must mean that's not the intended usage. Also, I was hoping the "origin_location" would reflect the Store that is selected for the customer to Pickup their Order, but that doesn't appear to be the case either. Can anyone explain how (using either REST or GraphQL API) we can identify which Orders are Pickup vs Ship, and from where they should be Picked Up? Thanks in advance for your assistance.
Would you love to unleash the unbridled power of the Google Shopping Channel into your sho...By Gabe Jan 6, 2023
How can you turn a hobby into a career? That’s what Emmanuel did while working as a wa...By Skye Dec 30, 2022