Salesforce Integration Ideas

Hey All!

This is just a general thread for ideas/experiences/pitfalls that anyone in the community has had with integrating ShipHero data into Salesforce.

It’s something that’s on the horizon for us, so I’m interested to hear any input and advice.

The main thing we’d like to accomplish is better visibility on existing orders without our customer service team needing to check several places.

Additionally we’d like our customer service team to be able to make changes to an order in Salesforce, and have those changes sync to both ShipHero and our ecommerce platform.

If we take it to the next level, we’d want to proactively detect order differences between our ecommerce platform and ShipHero (e.g. maybe a product was changed in the ecommerce platform but that change did not sync into ShipHero, or maybe a product was added to an order in ShipHero without being added in the ecommerce platform).

If you can relate to these needs, have any thoughts, advice, warnings, etc, we’ll really appreciate it if you can take a moment to post a quick reply.

Thank you!

-Sid from Origin

Hello @originsid
A pleasure to e-meet you.

We can surely help you with this, as we have great experience working with Shiphero and so many other e-commerce, marketplaces, accounting systems, 3PLs and etc.
So, we can definitely help you here.

You can please contact us here - sales@constacloud.com
We are integration partner of Shiphero.

Looking forward to hearing from you, thank you!

Hi Sid,

Luis here from ShipHero.

We appreciate your thread and please, let us know if you have a specific request, examples or issues and we’ll take it to our product team to consider!

Best Regards,

This one is old news now, but I’ll drop a couple wishlist items we had for folks who may come across this in the future:

Simple way with the API to get the URL for an order in the ShipHero backend (so we can easily link to the order from Salesforce). Currently I think this would require a separate request for each order to get the “legacy id” for it, which seems to be what’s used in the URL in the ShipHero dashboard.

SSO solution that works with Salesforce and ShipHero.

If we had those a few years ago we probably would have done a lot more cool stuff :smiley:

Hey @originsid! You can create an order and expect its assigned ID in the associated query you can make when sending the mutation. That single step, plus appending the legacy ID to the common part of the URL, should do the trick:

mutation {
  order_create(
    data: {...}
  ) {
    request_id
    complexity
    order {
      legacy_id
    }
  }
}

Have a nice day!

Hey @tomasfd !!

Hope you’re well!

To be a bit more specific on our need, we use the orders endpoint to fetch updated orders, and ideally we’d like the legacy_id in there. If that’s available from that endpoint, please let us know, it really could have just been an oversight when we wrote our scripts and it’d be quick to add that in if it’s available.

Thank you!

-Sid

Its there! The orders query is just a collection of order calls so they both share fields, not the arguments though.

https://developer.shiphero.com/wp-content/uploads/spectaql/#query-orders

Ultimate, they both return an order object:
https://developer.shiphero.com/wp-content/uploads/spectaql/#definition-Order

Please let me know if this is what you were looking for!