ShipWorks Module: Legacy vs New Image Path Support for Invoices

[William Davis]

I’m using the compiled ShipWorks module provided by Miva. Historically, product images were stored in a flat legacy directory. Since switching to Image Machine, image paths are now dynamically generated and organized differently.

However, ShipWorks still receives legacy image paths via the module, which causes issues when:

• Newer products don’t have legacy image paths.
• Legacy products have been updated with new image locations only.

Ideally, I’d like to have ShipWorks receive a ResolvedImagePath that:

• Uses the new image path if available
• Falls back to the legacy path if not

Since the ShipWorks module is compiled, I’m unsure if I have any access to alter what image path is sent. Can you advise if there is:

1. A way to modify the data ShipWorks receives?
2. Any known workaround or support-assisted override for this? Or,
3. Other options?

[Mark Hood]

I've been dreaming that someday the shipworks module would be updated or perhaps a new API integration is possible now for many years.
Last time I think the module was updated was 2019. They also don't support webp in shipworks yet so if you've started making that change the new ones won't work anyways.

[Rick Wilson]

We've been told by Auctane (Shipworks owner) that eventually everything will flow through the new API's we built on their latest code that works with ShipStation. So no update is forthcoming to the old module, but you might inquire with them if there's any movement on their end to make our integration work with Shipworks.

[Foreman2]

Will the new API flows allow order information changes to transfer back and forth like a cancelled order, cancelled item, etc?

Also, will they allow custom field data to be transferred to Shipworks?

[Rick Wilson]

yes, it's the same module that we've had out for ShipStation for the past 18 months or so.

[Mark Hood]

The response I got was this.

They have let me know that there is no ETA on updating the Miva connection but it is on their radar.

Maybe we need anyone using Miva and Shipworks to send an email... I fear we may not have that many voices though because I know a lot switched to shipstations but shipworks really just works well for us.

[Rick Wilson]

For the record, I don't think they're planning on updating the old module. The "big idea" was that their new app layer, which is what we use for ShipStation, should "just work" for all the platforms they own at Auctane. I'm not super clear behind the scenes if that's actually true.

If you have a good contact over there, send me their info and I'll see if Brennan or someone over here can connect with them.

[William Davis]

For the record, I don't think they're planning on updating the old module. The "big idea" was that their new app layer, which is what we use for ShipStation, should "just work" for all the platforms they own at Auctane. I'm not super clear behind the scenes if that's actually true.

If you have a good contact over there, send me their info and I'll see if Brennan or someone over here can connect with them.

Approached ShipWorks, here is h ow they finally responded:

"My team mentioned that you may be able to get MIVA to decompile the module file so you could have a developer look at and possibly modify it to also grab the "new" paths if this helps."

I knew they were going to be a waste of time. The last 3-5 support tickets I've opened with them within the last 12 months I've gotten the same vibe from them -but they are very nice. lol

[Rick Wilson]

We could decompile the module for them, but they'll need to reach out and work through us on that request. Find out who we should talk with?

[William Davis]

We could decompile the module for them, but they'll need to reach out and work through us on that request. Find out who we should talk with?

Thanks! Will do.