TraciW

My feedback

  1. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    TraciW shared this idea  · 
  2. 341 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    We are currently working on a feature that displays the best way to ship (either based on best price or fasted delivery time). The goal is to show the best way to ship across all of your connected carriers.

    The next phase of this feature will include automation options. We’ll update this post when the development work has begun.

    An error occurred while saving the comment
    TraciW commented  · 

    If SS factored in the standard USPS / UPS / Fedex zones and transit times by zip code and allowed these to be used as criteria in the automation rules, it would save my team 100's of hours.

    IE - if USPS PM is 3 day transit time, choose FC instead || if USPS PM is 2 day transit time, choose PM

    or

    if UPS zone 4-6 choose 3-day, if zones 1-3 choose ground

    The only other option is to create a huge number of rules based on 5K different zips codes AND carrier AND service options, which i don't think SS can even support and is not realistic.

    This would allow me to automate carrier/service selection and review carrier OTD so I can 1) proactively reach out to the customer to address the delay, 2) easily compile and submit guaranteed service claims to the carrier, and 3) review OTD metrics by carrier for QBRs and decision making.

  3. 38 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    TraciW commented  · 

    Better yet, in order to facilitate carrier/service selection once we know the 'deliver by' date:

    If SS factored in the standard USPS / UPS / Fedex zones and transit times by zip code and allowed these to be used as criteria in the automation rules, it would save my team 100's of hours.

    IE - if USPS PM is 3 day transit time, choose FC instead || if USPS PM is 2 day transit time, choose PM

    or

    if UPS zone 4-6 choose 3-day, if zones 1-3 choose ground

    The only other option is to create a huge number of rules based on 5K different zips codes AND carrier AND service options, which i don't think SS can even support and is not realistic.

    This would allow me to automate carrier/service selection and review carrier OTD so I can 1) proactively reach out to the customer to address the delay, 2) easily compile and submit guaranteed service claims to the carrier, and 3) review OTD metrics by carrier for QBRs and decision making.

  4. 106 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Hey everyone! Thank you to @Perry who took the time to bring this one up! We’ll keep your feedback in mind, but for now we’re primarily interested in hearing what other users have to say.

    If you haven’t already, please let us know your thoughts on this and how you’re doing this today (if at all).

    An error occurred while saving the comment
    TraciW commented  · 

    If SS factored in the standard USPS / UPS / Fedex zones and transit times by zip code and allowed these to be used as criteria in the automation rules, it would save my team 100's of hours.

    IE - if USPS PM is 3 day transit time, choose FC instead || if USPS PM is 2 day transit time, choose PM

    or

    if UPS zone 4-6 choose 3-day, if zones 1-3 choose ground

    The only other option is to create a huge number of rules based on 5K different zips codes AND carrier AND service options, which i don't think SS can even support and is not realistic.

    This would allow me to automate carrier/service selection and review carrier OTD so I can 1) proactively reach out to the customer to address the delay, 2) easily compile and submit guaranteed service claims to the carrier, and 3) review OTD metrics by carrier for QBRs and decision making.

  5. 35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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
    TraciW commented  · 

    If SS factored in the standard USPS / UPS / Fedex zones and transit times by zip code and allowed these to be used as criteria in the automation rules, it would save my team 100's of hours.

    IE - if USPS PM is 3 day transit time, choose FC instead || if USPS PM is 2 day transit time, choose PM

    or

    if UPS zone 4-6 choose 3-day, if zones 1-3 choose ground

    The only other option is to create a huge number of rules based on 5K different zips codes AND carrier AND service options, which i don't think SS can even support and is not realistic.

    This would allow me to automate carrier/service selection and review carrier OTD so I can 1) proactively reach out to the customer to address the delay, 2) easily compile and submit guaranteed service claims to the carrier, and 3) review OTD metrics by carrier for QBRs and decision making.

  6. 69 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Hey @Daniel, thank you for adding your idea! Are you only interested in the shipping cost report or are you looking to generate several weekly/monthly reports? Would this just be for you or for other eyes as well?

    TraciW supported this idea  · 
  7. 651 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  159 comments  ·  Product Feedback & Fresh Ideas » Product Records  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    TraciW commented  · 

    You have my votes. We will move away from ship station by EOY if this is not implemented. How does SS offer inventory management, but then if we have a basic multi-pack? It basically renders the inventory management functionality useless for our needs, and create a ton of work outside of the system to ensure multi-packs are picked and consumed from inventory correctly.

    TraciW supported this idea  · 
  8. 171 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    TraciW supported this idea  · 
  9. 5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    TraciW supported this idea  · 
  10. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    TraciW supported this idea  · 
  11. 22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    TraciW commented  · 

    This is needed. Also need ACTUAL Parent/Child sku setup options. IE SKU-A is actually a retail master carton with 8x SKU-B inside. Customers can buy both SKU-B standalone, or they can buy the 8-pack, but ShipStation inventory consumption does not know that SKU-A = 8x SKU-B... so its's basically useless and we have to calculate consumption manually.

Feedback and Knowledge Base