Hi,
So Shopify has integration with colissimo, the order looks something like this.
Each pick-up point from Colissimo has a pick-up point id associated with it, how do I pull this from here or just pull the pick up point address from here, so I can at least tell its be made via pick up point and not normal address?
Hey Tom - are you using this app: Colissimo Official - Colissimo officiel | Shopify App Store
If so, it sounds like you may need to connect with the developers directly on this issue here Le Studio de Tom - Expert e-commerce et solution SaaS
If your goal is to simply differentiate between a pick up point order or a shipping order, you can find this out via the methodType field on the FulfilmentOrder.deliveryMethod.
Hope that helps!
So im using shopifys native colissimo integration with local pick ups. I need to this pick point id which I then can pass into a erp system. Bit of a tricky one this.
Cant even use there widget as checkout extensions wont allow it.
Okay I understand now. Unfortunately, although pickup point data is visible in the admin, the data isn’t available on the public API at the moment. However, stay tuned as teams are working on making it public.
Hello, do you have any updates regarding the availability of the pickup ID in the REST API when using Shopify’s native pickup option ?
Hey @Leo_Quinsac 
- we do expose some pickup location data through the GraphQL API, but this is mainly intended for apps that are managing/creating pickup points:
Right now, for the REST API, we aren’t supporting adding new features for it going forward as it’s considered a Legacy API (more info here)
Hope this helps, let me know if I can clarify anything on our end here! 
@Alan_G Thanks for your answer but when a customer places an order using Shopify’s native pickup option with Colissimo at checkout, I’m unable to retrieve the ID of the selected pickup point, even through the GraphQL API. I only have access to it’s name and address. However, I really need this pickup ID because my external logistics provider requires it
Hey @ Leo_Quinsac - thanks for following up here. I believe that ID should be retrievable, as long as your app has the right access scopes.
Would you be able to share your app/integration’s ID as well as an example Order ID by any chance? I can see if I’m able to take a look on our end internally and share the best method for grabbing that or to see if we can explain why it’s not popping up for your app.
Hope to hear from you soon, happy to look into this!
@Alan_G Hey, is it possible to contact me to expose you my issue ? i have a custom app that need to read my order’s pickup_up_point_id just like @Tom_Hooker explained before
Hey @Leo_Quinsac - for sure! Sending you a DM now
Hey @Leo_Quinsac and all, just looping back here per a DM I had with Leo. Confirming that Leo’s follow up here does appear to be the same situation as Tom’s initial post, I think there was a misunderstanding on my part, I’ll check to see if we can share any updates though - I’ll loop back here with more information or to put through a feature request at the very least for you folks
Hi folks, following up here . I was able to touch base with the product team, and confirm that we don’t currently have a plan to make these endpoints retrievable. That said, I’ve been given the go ahead to log a feature request for this, since it definitely is a valid use case.
I can’t guarantee anything specifically on my end in terms of when/if this would be implemented, but I’m happy to set up that feature request to advocate for this on my end.
That’s a really good question 
. Since Colissimo assigns a unique ID for each pickup point, the cleanest way is usually to fetch this through the GraphQL API rather than relying on the REST API, as the latter is now considered legacy. The GraphQL route will let you pull more structured details like the pickup address and identifiers, which can help you differentiate them from normal shipping addresses.
On a related note, I’ve also been exploring how different platforms handle user-friendly solutions and creative automation in everyday scenarios. If you’re interested, I’ve shared some insights here: birthday wishes for friends
