It is concerning that this even needed to be suggested as an idea. Forgetting "package" for a moment - every "Equals" should have a corresponding "Does Not Equal" whenever possible.
You can accomplish this with an Order Filter plus an Automation Rule.
With that said, I agree on the idea, I just wanted to make sure you at least benefited from the workaround that exists in the meantime.
As for your idea, yes - the store settings module should let configure as many options from Automation Rules as possible/feasible.
Hey @Matmul, thank you for bringing this up. Can you give us some more information on what you mean by “our warehouse pulls the shipstation order id”? For example, is your warehouse using the API for a custom app you’ve built? And how does this relate to what you’re looking at in ShipStation?
Hopefully we can work on a something that’ll help you get the ball rolling so let us know here in the product feedback forum.
We need this too.
You use it internally. You give it to us on packing slips. And you give it to us over the API.
But you don't let us use it in reverse, so we can't scan a packing slip or copy an order ID from a solution build with the API, and look up the Order ID on the front end of ShipStation.
This is less a feature request and more a "Don't hide something you already use from search". It is like the "feature" is obfuscation, and this request is to remove the feature. We should have negative votes.
3 Votes from me, and I already have a similar idea open.
We use your API for a custom app that does everything under the sun. We pick and pack by order ID because like @Matmul mentioned, order numbers will collide. We have 5 ebay stores, and ebay stores are per-username, so eventually all 5 ebay stores will have order number 50000 for example.
Using the ShipStation OrderID ensures a unique identifier. That is the only way a machine can tell the difference. You already use this internally, and reveal it to us via the API. What @Matmul and I need is for the order ID to work on the front-end of the ShipStation platform.
At our facility, we scan the OrderID everywhere in our own system, but then have to hand-type an order number in your system because you don't support your own OrderID. And as expected, we get multiple results when searching by order number because order numbers collide.
Giving us support for the OrderID will cut out the ambiguity.
On Amazon, using Amazon's Buy Shipping service is important for defending against item not received claims. And for seller-fulfilled prime, it is required.
Why do we have to be punished for doing the right thing on Amazon? Why are "fulfillments" treated like second-class citizens? They aren't even external fulfillments to begin with, but I understand that after the Stamps.com buyout all the programmers jumped ship and what you are left with probably requires shipments to have a void link or some other carrier glue.
Hi everyone! Members of our product team that are involved with these order details redesigns have requested direct feedback from you and other users. If you would like to, feel free to email our product team at email@example.com with your most precise feedback, criticism, and impact to workflow caused by these recent order detail changes.
We now need this too, since your recent GUI change removes the ability to see the last shipment configuration for an order.
30 votes3 comments · Product Feedback & Fresh Ideas » Selling Channels, Carriers & Other Connections · Admin →
Thanks for your great idea! We’ll keep this in mind but would like to see more interest from other users before we pursue this new feature. If you know any other users that are interested please send them here!
I'm interested just based on ShipStation's comment alone. The more you can make available over the API, the less we have to post on the ideas forum for front-end requests.
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.
A flaw with everything coming from ShipStation is that we are all on the hook if an email provider decides some emails are spam. The entire domain being blacklisted means none of us can get emails into the inbox of our customers.
It could happen. Occurs with enough other services we used where someone before us got the domain blacklisted.
An order’s record itself can never be deleted. It can be inactivated, but an order cannot be deleted. No order entry will be permanently wiped from the system. However, the system is working as intended that the order activity is removed after roughly 2 months.
And to help us understand your workflow, how frequently are you going into orders that are older than 2 months old to check the activity? And is this under situations such as a wrong delivery address or when trying to see who on your team shipped a package, etc. that you go back to view these older orders’ activity?
Going to mention an ebay review period has passed and I'm trying to investigate a late delivery from just over two months ago. Depending on the region, most of our ebay rating periods go back at least 3 months. Unfortunately the order activity is gone. It would have been helpful to know what date the order was imported on, and with what status.
Especially since I have open ticket about ShipStation importing unpaid ebay orders as paid. I've been told that I need to contact ebay. I'm not the one who advertises I integrate with ebay.
The order activity would help with this data collection, especially if ShipStation believe I need to be the ebay liaison for Every.ShipStation.Customer.
In this day and age it should be pennies per customer in disk space needed to continue storing this for a long time.
Didn't see Caleb respond to ShipStation's question, so I'll add my two cents that we probably attempt to look at order activity older than 2 months about once every other week. We use it for a variety of reasons. We'd need it less if the Order API gave us a Ship Date with an actual time. The value over the API is clearly a timestamp because it has hh:mm:ss, but it goes unused. Going into ShipStation is needed to find out what time the shipment was created, but if we do this after two months we screwed.
Hey @kalrakov thanks for bringing this up! We’d like for your idea to gain some traction before moving forward.
Please add your thoughts, examples, or workflows here in the forum to help us and others understand your goals.
>This should be self-explanatory.
Instead of voting on the idea I am going to cite your own ShipStation blog, where you post about the importance of a mobile experience having parity with the desktop experience. Here is one example:
Thank you for your feedback on this idea and letting us know how you would use tagging/rules to identify those repeat or first time customers- your use cases for this feature really help us shape how it would best fit into your workflow. Please keep commenting if you have new ideas so that we can best design this feature with your needs in mind. Our product team is still reviewing this idea and we’ll let you know once a decision has been made.
We were doing it via the API, but it broke during the API transition this month and based on how you have created the replacement API we are not sure we will be able to do it again. It seems like the new API is built for simply recreating the GUI. This was a perfect example where we used the API to meet business demands that weren't present in the GUI.
When it did work, we had a view in our internal program that let us, for a given date rage, view the number of orders by customer ID, email address, etc; basically any useful field.
Hi, everyone! Thanks for showing your support here! Can you tell us more about what you would use this feature for?
From the previous comments it looks like some users are looking to use this for exchanges or more accurate accounting. Do you all agree?
What do you think about our re-ship feature? Every time you re-ship an order, we will show you all the tracking numbers related to that order and its status. You’re able to change the order details for each label you re-ship.
More info on re-ship (not to be confused with re-print): https://help.shipstation.com/hc/en-us/articles/206638607
Please let us hear your comments in the forum and add your ideas with other users so we can get the full picture!
Giving 3 votes to this
Thanks for leaving your thoughts, everyone! We’re still reviewing this idea that has definite merit. 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.
Would like to be able to customize pick lists. We have them print out our thermal printer with a batch and you need a microscope to view the text. I need to customize these and increase the font size.