Fredwarner1

My feedback

  1. 44 votes
    Vote
    Sign in Sign in with: ShipStation
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thank you for your feedback!

    We are currently investigating how to upgrade our ebay integration to ensure we are receiving the most up to date information. We will update this post when we have started this integration work.

    An error occurred while saving the comment
    Fredwarner1 commented  · 

    Please make this an option, so users can decide if they want their eBay order ID to reflect the Sales Record Number or the new eBay Order Number. We'd like to use the eBay order number, since that is what customers see, and it would make it easier for us to look up orders in ShipStation, both manually and with the API.

    Fredwarner1 supported this idea  · 
  2. 34 votes
    Vote
    Sign in Sign in with: ShipStation
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Hi, @Craig! Thank you for taking the time to bring this one up! We’ll keep it in mind when updating our reports, but for now we’d like to see what interest there is from other users before moving forward.

    If you’re interested in this idea, please let us hear you! Comments count, too!

    An error occurred while saving the comment
    Fredwarner1 commented  · 

    We had to develop our own solution to this since there doesn't seem to be a good solution available. It uses the ShipStation API and the various carriers' APIs (UPS, USPS, FedEx, etc).

    Basically, we have a script that runs on a cron job once a day to load all new ShipStation shipments into a database. Then a different script that runs via cron once per minute, each minute pulling one tracking number that is still in transit, and checking the carrier API for its status. If it's in transit and on time, it marks it to check it again the next day. If it was delivered on time, it marks it to not need to check it again (and purge it from the database after a period of time). If there's an exception, or it's late, or it hasn't been scanned in at all, it emails somebody so they can handle it.

    This method insures we don't hit the fairly low ShipStation API call limit, since we have other things running on the ShipStation API. A simpler solution for low shipment volume would be to have just one script that pulls ShipStation shipments and check the carrier API in one step.

    The hardest part is that the USPS API doesn't return a good exception code to use. USPS just returns the notes for each tracking event. So you have to build a large list of potential status notes, and I've found they can change based on what the individual postal employee enters. UPS, on the other hand, returns a single-character status code. So you only have to check for "X" for an exception, for example. Much better.

    I don't think it would be hard for ShipStation to implement something like this, and it would certainly be a very positive feature to have.

    An error occurred while saving the comment
    Fredwarner1 commented  · 

    It would be great to have a system that warned us of delayed, non-moving, or late shipments. Something that could warn us the moment a shipment experiences a delay or misses its delivery date.

  3. 29 votes
    Vote
    Sign in Sign in with: ShipStation
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Fredwarner1 supported this idea  · 
  4. 2 votes
    Vote
    Sign in Sign in with: ShipStation
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Fredwarner1 commented  · 

    I wish this idea got more traction because it seems pretty important for a large inventory where tags are updated in bulk.

  5. 100 votes
    Vote
    Sign in Sign in with: ShipStation
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Hi, @everyone! Can you help put this into perspective and add how often (relative to your single page packing slips) you’re needing to print additional pages?

    For example, in a week 3/4 of your orders require a single page for packing slips and the remaining 1/4 require 2 pages; very rarely does an order need more than 2 pages.

    An error occurred while saving the comment
    Fredwarner1 commented  · 

    It's pretty rare but we were just hit by this problem twice in the last week. One order we caught but the other we didn't. Each order had 8 or more line items, so using the half sheet packing slip some items were cut off (with no way to know that they were).

    We can't switch to a full sheet packing slip as this is only a problem on a few orders out of 20,000+ per year.

  6. 8 votes
    Vote
    Sign in Sign in with: ShipStation
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Fredwarner1 shared this idea  · 
  7. 17 votes
    Vote
    Sign in Sign in with: ShipStation
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Fredwarner1 commented  · 

    Having the ability to change State through an automation rule would be very helpful here. In a batch of 100-200 shipments, there will often be 2 or 3 going USPS to PR (or other territories). Having the errors and having to manually change addresses really puts strain on our process. It seems like it shouldn't be too difficult to add one more Action in automation rules. You can already filter by State.

    Fredwarner1 supported this idea  · 

Feedback and Knowledge Base