Cleo Integration Cloud vs. Vertify

CLEO Integration Cloud is well suited in any environment where you need to move and translate business data from one format to another or multiple other formats. It is very well suited to replace existing EDI systems that are cumbersome, are a lot of work to add new mappings (add customers for example), or where the support is lousy and you are constantly creating support tickets to try to resolve issues. It just works very well and is constantly improving including keeping up to changes made by various services such as Shopify.

Incentivized

I would recommend it, as VertifyData exactly fit our use case. I can't speak for all use cases and all connectors - naturally - but the ones we are using and have explored so far, work perfectly well. Also, being a person myself that is not fluent in SQL or JSON or API language in general, I was still able to create all workflows our company needed myself. Which I consider a huge benefit.

• A great platform perfectly integrated with the rest of the company's software.
• Detailed design with simple and easy access from anywhere to our information.
• Multi-location and multi-device access.
• We save on hardware, software and maintenance, by minimizing the user's need for powerful equipment and the programs in charge of managing and configuring them, reducing the investment in their acquisition.
• Cleo integration is in charge of technical maintenance and updates.

Incentivized

• Communication.
• Follow up.
• They're constantly trying to improve.

• A fully functional help manual would be good. Some topics have no help at all, "envelopeassemblybycontext" for instance.
• A needed feature is to be able to sort files by either file type (FM, RS, BPS) or by filename. Some of our projects have almost a hundred files.
• Better, more descriptive error messages. Sometimes a ruleset or process fails and the error message is not helpful.

Incentivized

• Automated error trouble-shooting is not always clear/helpful
• Clearly distinguishing internal errors vs. external errors
• Perhaps a blog where users can interact with questions + solutions

Creating a mapping between source and target while also using lookups and transformations is not trivial. And VertifyData solved this reasonably well, at least all users in my organization understood it pretty quickly.

It is not the easiest user interface to read/understand. However, once you understand how it works, then using it is not that bad. It's hard to remember what feature is listed under what tab (Manage vs. Define). A suggestion would be to get all call to actions on the same page

Great data manager in the cloud, at a competitive price, backed by a great company and great professionals.

Incentivized

Before choosing a solution, we did a detailed analysis of cost, performance, scaling and support. Cleo checked all the right boxes and we have been very satisfied with our choice.

Incentivized

Vertify offered more flexibility and was presented as a simple solution. In reality, it is more complex that we envisioned and we have never fully utilized our tools due to the lack of ability to configure things properly.

Incentivized

• We have easily improved our EDI tenfold (or more) as far as ease of adding new customers for example
• We have saved a ton of money by reducing chargebacks for missing ASNs for example
• We have improved customer scorecards where they measure our EDI performance such as one large brand name customer we sell wholesale to who originally scored us around 28% and after implementing CLEO we quickly went to a 96%+ score.

Incentivized

• Independently, teams are able to carry out their process with less communication and at a higher level of accuracy.
• VertifyData is actively taking into consideration, consulting, and supporting our plans to build out the business