Feedback on StarShip Cloud

A customer just received an email from V-Technologies regarding StarShip. They're suggesting their StarShip Cloud solution, citing issues with outdated on-premise setups and infrastructure. According to the email, come January 1, 2025, on-premise pricing is slated to jump by an average of 30%, and they're changing their policy on lapsed renewals (you'll be hit with back maintenance fees at the current rate). 

To sweeten the deal for cloud migration, they're offering incentives: 50% off the first year and 25% off the second year of the SaaS subscription, no price hikes for two years, and no back maintenance fees if you commit and pay onboarding before your renewal date (My customer renews 5/21/2025). They're also highlighting that over 1,200 users are already on the cloud platform.

I'm curious about everyone's experience with this. Specifically, I'd love to hear from both sides:

  • Those who have moved to StarShip Cloud: What has your experience been? Any unexpected hurdles or pleasant surprises? How has it impacted your customer's Sage 100 integrations? Are the performance improvements noticeable? Any regrets?

  • Those who have not moved to StarShip Cloud: What's holding you back? Are you concerned about cost, functionality, integration, or something else entirely? What are your plans for the upcoming price increase and policy changes?

Parents
  • 0

    We decided to migrate to StarShip Cloud from the StarShip on-premise Desktop client about a year ago after receiving similar emails for V-Technologies. I spent 6-months trying to get StarShip Cloud to work smoothly in our environment and then gave up.

    Besides dealing with a couple of outages that broke Sage StarShip Link for days at a time (the first outage lasted over 2-weeks), there were just too many bugs. Sales Kits weren't handled properly. Item weights when applying a sales unit of measure (e.g.: selling in packs) were not calculated properly affecting the Customs info for international shipments. The StarShip Connector would randomly stop working which caused the scale weight to not be sent to StarShip Cloud. Making that worse was that StarShip Cloud defaults to the Sage item weights when the scale is not available (see the previous note about item weights not being calculated properly when selling packs). I tried to make the default package weight zero which would prevent a shipment from going out with an invalid weight but even V-Technologies Support admitted that was not possible.

    I asked Support to submit some feature requests to at least bring the StarShip Cloud functionality up to the level of the Desktop client and was told that the Development team had such a backlog that new features were at least 9 months out. Our users were struggling daily with some of these issues and being told it would be months before they could be addressed was the last straw.

    We started testing an early release of SSK from Simple Shipping Software last September and have been very happy. SSK is much faster than StarShip Cloud and its tight integration with Sage 100 allows for better automation. We do a good amount of international USPS shipments and maintaining a separate inventory database in StarShip was always a hassle. SSK uses Sage 100 data tables for all item data.

    Maybe V-Technologies has made some big improvements to StarShip Cloud or the issues they still have won't affect your customer. Otherwise there may be an alternative worth considering.

  • 0 in reply to Dave M.

    We may have looked more into this had we known about it before going forward with Starship Cloud.

Reply Children
No Data