Thanks for your continued support on this idea, we don’t have any updates to report on the status of how we authenticate email addresses based on client domains, but any updates will be posted through this thread.
But, please continue providing your experiences with how the lack of this feature impacts your workflow.
You guys HAVE to fix this.
We're not far now from a world where incorrectly configured email deliverability is equal to zero email sending capability.
Imagine offering shipstation with no ability to send out shipment status and tracking emails to your customer's customers. That's very close to what you have now without the ability to include your mail servers in our SPF records.
Very, very low hanging fruit to fix this with a huge win.
Put one devops person on this for one weekend and it's all good.
Please get this done.
70 votes25 comments · Product Feedback & Fresh Ideas » Selling Channels, Carriers & Other Connections · Admin →
Thanks for bringing this up! If you know any other users that are interested please send them here!
As developing a seamless integration typically requires cooperation from both parties, we recommend reaching out to SpeeDee Delivery and expressing your interest in an integration to help expedite this process.
We've now added Spee Dee to our workflow, bypassing ShipStation for those orders. It's a pain in the rear. We're now shipping something like 20% of our total orders, and probably something like 90% of our midwest orders, via Spee Dee and outside of ShipStation.
I am a developer and I wrote a simple integration for our e-commerce system with Spee Dee's web API in an afternoon. It queries with an origin zip, a destination zip, and a weight and returns the shipping cost (and also a zone number which would allow you to look up a transit time in days). Your team would likely need to build a more robust integration, so maybe it would take a few days instead of an afternoon. Seems like a no-brainer.
Add Spee-Dee please.
Thanks for leaving your thoughts, everyone! We’ll keep this in mind; for now, please leave your votes and comments to help keep this discussion active. Being specific in how this would affect your workflow and how you’re currently doing it will help our product team to implement new features.
For now, as an alternate workflow suggestion, you could be marking these orders as shipped. You would want to set the carrier to “Other”, and then use the tracking field for your “Pickup” or “Pallet Delivery” custom message.
Here’s an article to go over marking orders as shipped in case its needed: https://help.shipstation.com/hc/en-us/articles/206640507
This seems like basic, core functionality. You should really provide a way to print a basic from/to mailing label with a choice of "other" for the carrier.
You may not be aware of this, but you are not currently partnering with EVERY SINGLE carrier and delivery method that companies use to get their product to their customer. Yet many companies have made SS a core part of their order processing workflow. The inability to handle some percentage of orders for companies that use carriers and methods you don't support is a flaw in your service that could be easily remedied by simply providing an "other" carrier and letting us print a generic label.
It's pretty hard to believe that this issue has been sitting in here un-addressed for (at this point) over five years.
3 votesbt-admin shared this idea ·