MichielfromNL
Shopify Partner
Contact Me
Status
Offline
Last Activity
‎01-06-2025 07:49 AM
Topic Started
3
Topics Started
Topic Solutions
0
Solutions
Post Count
13
Posts
Post Kudos
8
Likes

Bio: Consulting, public affairs, and IOT & other development as a hobby & for the family business

Community Badges

No content to show

User Activity

Hi EmoFryda,Yes, I still use this approach , haven't found an easier alternative as of yet. 
Hi,Tx for this answer!It however raises the following question: are variants also unique across shops (shop instances) ? Same for inventoryitem id's and location id's ? This is relevant for us because we connect to / manage different shops & manage i...
Hi Liam,Thanks very much for passing that info on!About graphql: I am aware of the fact that at some point in time, in any case this year, we need to move from REST to GraphQl . But I haven't studied that in great detail yet. As far as I understand, ...
The move to new-style fulfillments (by requesting fulfillment_orders for each order) was aimed at decoupling orders from fulfillments; the idea is that the fulfillment_order has all the information needed to complete the fulfillment.We retrieve REST ...
After some experimentation I found a relatively easy solution myself:Since this is an extension-only app, the extension is identical between each app for each domain/shop, i.e. does not have any data relating to the specific app (name).So simple syml...
We run several shops but Plus is still way too expensive for us. We wrote a small checkout validation on addresses, to limit non-deliverables and returns for customers that forget to enter details etc. Good for the environment But we are running int...
I've run into the same problem, and I have an additional questionWe run two relatively small sites , (hence) we are not in the Plus plan.I wrote a simple checkout validation app that we want to apply to both sites. But as it seems, we need to make tw...
Understand,But then we are back to #1 : (See my original post) because with that filter,    ?status=open&fulfillment_status=unshipped,partial/orders/count.json and /orders.json  give different results. 
I am having the same issue: cancelled and archived orders remain in the "unfulfilled list" forever.This is a pain, because there is no (JSON) import filter to exclude archived or cancelled orders hence they keep showing up in the to-be-fulfilled list...
The problem is that these orders stay forever in the list as "unfulfilled" .Did you find a way to remove them from the unfulfilled list too ?  
Thank you!This indeed gives consistent counts.But introduces a new problem: usually there are considerable amounts of cancelled orders that have not (yet) been archived. Which are then included in the count & in the JSON order list to be processed, w...
Who can help me here.Í have been pulling my hair out to find a filter that gets me consistent counts for orders/count.json and /ordersFor a smooth import UI, I first count how many orders there are, and then I read themBut whatever I try, the  number...
Question remains: why there is no fulfillment_order_id list in the Order object? That saves an extra API call to get that ID. Can we submit that request to Shopify? (how ?)
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.