OpenText Trading Grid alternatives and competitors

We use the solution basically for the integration, mostly EDI, and sometimes API. 

The documents would come out of SAP and then go to SEEBURGER, get transformed, and then be sent to the trading partner. 70% or 80% of the business would be this, and 20% is on the API side where we have very high demands from the logistics side of the business.

Whatever it is I need, I have. for example, end-to-end integration, data mapping, communication protocols, and integration with the SAP module. Everything is good with SEEBURGER.

It's a stable product.

We haven't had any issues with scaling.

Technical support is responsive. 

At this moment, everything is working fine. When we are talking to them, when we are trying to bring all this mapping in-house, right now, SEEBURGER is doing everything for us. 

However, when we are thinking of going onto the cloud, so they are not using any of AWS or Azure which are more stable. They have their own private cloud. That's the reason we did not go ahead with managing everything by ourselves or moving into the cloud. They said that they're going to be doing it within the next two years, having access to Azure and AWS. That would be something we would like to see.

I've been using the solution for more than 15 years. 

The stability is good. For example, it is far more cost-effective than OpenText and better, far more reliable, and has very high availability. It's good overall. 

The fact that it is on-premises does not affect its scalability. For us, it works quite well and meets our needs. We have 20 to 25 users on the product right now. Mostly, they are consultants. It's used on a daily basis. 

Technical support has been great. They resolve our issues very fast. We are satisfied with the level of support we get. They are very responsive.

Positive

I'm also familiar with OpenText. 

OpenText is priced higher than SEEBURGER. It's why we were trying to find out a different provider, however, it's a very big task as we have a lot of trading partners on OpenText and it will be a big challenge to move away from that provider. Initially, we were thinking of Mulesoft, however, when I talked to my peers I found that Mulesoft gets costly once you start implementing it. Right now, talks are going on as to how to get rid of OpenText, and whether we move everything over to SEEBURGER. OpenText's responsiveness to the customer service team is also not at par with SEEBURGER. I would rate them at around 2.5 out of five. 

Also, there are a lot of hidden areas where we'll have questions, and they're not providing answers. Maybe they're reluctant to provide answers about the cost or things like that. The transparency is less when you compare it with SEEBURGER. We would like to see, for example, more documentation in regards to some areas of OpenText to understand some areas of the product a little bit better.

We set up the solution 15 years ago. It was so long ago, that I can't recall if it was easy or difficult or what was involved in the process. 

A third party assisted in the initial setup.

I can't speak to the exact ROI. The head of the EDI has all this information. I do not have this information.

I'm not familiar with the exact cost of the solution. I can't speak to how much we pay.

That said, it's my understanding that it is reasonably priced. I'd rate it four out of five. 

I'm a customer and an end-user.

I'd rate the solution nine out of ten overall. I've been very happy with its capabilities.