Apache Camel is an open source integration platform.
N/A
SPS Commerce
Score 7.0 out of 10
N/A
SPS Commerce is a retail network, connecting trading partners around the globe to optimize supply chain operations for retail partners. SPS Commerce supports data-driven partnerships with cloud technology. Their retail cloud services platform features supplier onboarding, EDI compliance, ERP integration, product content management, and sales analytics.
Message brokering across different systems, with transactionality and the ability to have fine tuned control over what happens using Java (or other languages), instead of a heavy, proprietary languages. One situation that it doesn't fit very well (as far as I have experienced) is when your workflow requires significant data mapping. While possible when using Java tooling, some other visual data mapping tools in other integration frameworks are easier to work with.
Run as far away from this company as possible.We looked into using SPS Commerce as an alternative to TrueCommerce for our EDI integration software. After initial discovery calls that claimed functionality built into the service, we decided to make the switch from our current provider as it claimed to be more expansive. Upon signing our initial contract (which they will not do a full consultation without a signed contract - GIANT RED FLAG), it was discovered that the functionality would not work with our current systems and there was no benefit of switching from our current provider to SPS Commerce. However, they claimed that "you signed a contract, regardless of whether you use the software or not you owe the money." Long story short, we ended up in mediation costing a small business significant amount of money and legal fees. SPS Commerce is deceptive and cares more about short dollars than customer experience. Look at the BBB website for more information
Some of the documentation is a little sparse. In particular, its TCP-based routes use an underlying Netty server, and the interactions between Netty's decoder capabilities and Apache Camel's routing/handler capabilities can be a little muddy at times. In general it is clear which routes and endpoints are the more frequently used and which haven't been given as much attention.
We have quite a few people here who use this portal, and we have it set up to receive an email when an order is available to print. As of now, you can only add a few recipients to receive those emails; it limits you.
Invoicing is challenging at times as you have to remember to go in and invoice. If you forgot, it is hard to find the order to invoice, as it seems to disappear.
We still haven't figured out how to have some of the invoicing features auto-populate, so there isn't so much to fill out. I wish some of those features were easier to use, or find if you have them.
Phone support is generally very good and you can get a person on the phone within a few minutes. Their emailed customer support however is very poor and often goes several days or longer before receiving a response, if ever at all
Apache Camel has been the integration framework of choice, but I was not the person to make the decision to use it. Compared to other competing products like Tibco Business Works, etc., it is free and open source and its licensing policy is acceptable to the management of Cox.
We reviewed many, SPS Commerce Fulfillment was the best "bang for our buck" with the level of growth we have been experiencing. The list of services they offered were exactly what we needed to be able to move our business to that next level of professionalism where we were growing faster than we could prepare ourselves for.
Very fast time to market in that so many components are available to use immediately.
Error handling mechanisms and patterns of practice are robust and easy to use which in turn has made our application more robust from the start, so fewer bugs.
However, testing and debugging routes is more challenging than working is standard Java so that takes more time (less time than writing the components from scratch).
Most people don't know Camel coming in and many junior developers find it overwhelming and are not enthusiastic to learn it. So finding people that want to develop/maintain it is a challenge.
I enrolled in a product I ended up not using because the vendor that required it ended our working relationship and SPS refused to offer a refund. After I canceled it, they continued to charge our account for three more months of service.
The interface is simple and easy to understand and use, so it saved time when preparing shipments.
