We use Batches to organize orders before processing. Many times we need to contact customers before processing. All the customers we want to contact have been organized in a Batch. The most efficient way we contact multiple customers is via a mail merge, which requires a .csv (or Excel) file containing the customer and order details. Without being able to Export Order Line Items from within an Active Batch, I am left with no option but to contact each customer one at a time--a very lengthy and tedious process that ideally my company can avoid.

Who else would LOVE this feature?? Please VOTE to support this idea!

Permanent Customer Tags!!

It would be very beneficial to have the ability to tag an order within the "orders" tab for a customer and have the option to save that tag to the customer’s record going forward.

For example:
John Doe ordered from you in the beginning of the year. John then placed another order 3 months later. So you tag John in the orders tab as something like…. Returning Customer, Free Gift, or what every you want. Well low and behold the only way the tag will stick to every upcoming order is that you would have to search for his name in the Customer tab. Which is time consuming and a royal pain.

It would be great if you can tag John’s customer record from order tab instead of having to search for him in customers to apply a tag for future orders

It would give you the ability for you to say to yourself, hey this guy ordered from us before, or hey he received a free gift already. Without having to go through the trouble if hunting him down in the customers tab in order to tag him as something.

Just a thought…

I built an image of what I think it should look like.

What do you think?

Would like to avoid paying oversize surcharges from FedEx - I feel your software could accommodate this if you added more criteria in the automation rules. I see there are 47 different criteria ranging from # of Items to Warehouse Location. Why not add 1 more?

I think you should allow us to pick Girth.

A FedEx Account Executive emailed this me today. "If any one side is greater than 48", it will be assessed an additional handling surcharge of $11. An oversize surcharge of $72.50 would be applied if length plus girth exceeds 130"."

$72.50 for an oversized package!?

This package has dimensions of 32x15x25 and 57 lbs. You are quoting us only at $45.83.

Meaning it is oversized. According to FedEx rule 30.1 the formula used in maintaining you have less than 165" in length+girth. Is L+2W+2H. Meaning on that package It would be 32+2(15)+2(50)=162"

So tack on another $11 handling surcharge and $72.50 oversize surcharge. So now the shipment is $118.33!

And we don't find out about this until we get FedEx statements in the mail a month or more later!

We feel blindsided by this.

In talking to ShipStation Support over chat he told me you get the quotes directly from FedEx. So he felt your deed was done. I think however, that your software should provide us with a warning, error, or at the very least - the ability to create an automation rule involving a tag.

But over that chat we found no way to use the available criteria to accomplish flagging items with girth over 130". Which brings me to my first question I posed at the top of this idea.

You need to add girth. So you need to find a way to pop out a calculation for girth using the L+2W+2H formula and then we should be able to pick that as criteria for an automation rule.

We have several brands of products that we manage and sell thru SS. Each of them have their own Shopify account or we sell them on ebay. We use the shipping presets and absolutely love them!! However what is missing is the ability to have your preset ALSO be setup to use a specific USPS account. BEcause we have to always prepay the USPS in one single account it is difficult behind the scenes in our accounting department to keep track of how that money was used and allocated for each brand of products. For example we have commissions with artists and other designers who are involved with each product brand so we need to keep the accounting in silos for each one. This includes the shipping too.

So the solution is open up the ability to have more than one USPS account on SS... then take it a step further by allowing the assignment of a specific account in the shipping presets!!

This would take SS to an entirely higher level.

Thanks for considering.

Currently when entering multiple filter criteria they ALL must be true for the filter to match (ie, AND clause). This has clear limitations to the flexibility to filtering when you need to use an OR condition instead.

For example, to create an accurate filter for orders to Guam, you must create 2 separate filters, one with Country=Guam and another with State=Guam. If we were able to chose the logic operator (OR/AND) when setting up these filter criteria, both criteria could be used in a . single filter with the OR operator, instead of having to create multiple filters.

This idea has been suggested twice in the past with some traction but eventually shutdown by ShipStation Admin. Can you please add this feature? Previous requests for this same feature:

http://feedback.shipstation.com/forums/126593-idea-archive/suggestions/3097028-enable-and-or-in-your-filter-criteria

http://feedback.shipstation.com/forums/126593-idea-archive/suggestions/6499957-allow-or-for-filter-criteria-and-and-for-filte

My team throws around a LOT of plaintext Order IDs in Slack as we go about our day.

If we need to look up an order, we then have to go to Shipstation, enter the order in search, wait, and then do our thang.

To minimize time and friction, I wanted to write a snippet to automatically convert the plaintext order ID to a link that would open the corresponding Order ID in Shipstation. It would shave off 15-45 seconds from every order lookup... time which adds up!

It seems like a simple fix to be able to link to a certain order.

Thanks fuys for a great product.

We print the Order ID on every label so that we can use it in our WMS and ERP solution that we built based off of your order API. And our custom system does everything. Pretty much 90% of your idea portal is solved in-house.
The only thing we can't control is your interface, and API bugs.
We can't make use of the scan to view barcode because of how cumbersome the setup is. Here are my suggestions.

Remove the Hex
We have a perfectly good Order ID on our labels already, which we use in our system. Your Scan to View barcode feature requires the order ID communicated in hex. Why can't it just work as the order ID?

Remove the Special Characters
Even if you didn't require Hex, you require the order ID to be encapsulated ^#^ ^. We would need an additional barcode with the encapsulation so that it didn't interfere with our existing system. Just use a normal input box like everything else. We have made hundreds of pages in our system for dozens of features. None of them required encapsulation.

Remove the Order Status Requirement
An Order ID is unique to ShipStation. There will never be both an unshipped and cancelled order with the same order ID, so why require the filter? The person scanning the barcode may not even know the status - they could be using ShipStation to pull up the order to confirm if it was cancelled. In that example they would have to <i>Look up the order so that they could Look up the order</i>. How redundant. Remove the filter, it makes no sense.

The hex and special characters are extremely cumbersome, and filters for a 1:1 match are redundant. It is almost like a third-party came in and coded this without knowledge of how anything else works.

Also improve the idea portal. Typing this was a pain with the textarea limited to like 600px width. 1-2 lines of code will allow the user to stretch the box wider so that the lines to wrap so soon.

Also the forums are embarrassingly quite for an official support forum. I could answer most of the users questions, so why can't ShipStation? I would be frightened to see an official support forum be ignored by a company. But I'm already stuck here.

Thanks for voting.