@Nabil I've also used boomi and patchworks

boomi is definitely in that “costlier” bucket in my mind, and it seems like patchworks is focused on ecommerce?

What's your usecase?

I’m annoyed about them not having logs for “successful” runs that are missing data elements and whatnot

Both valid points, they've got a lot better at logging the entire payload in the past few months for failures though. If you want to log success, you need to set up a separate import into another service, I often do it in dynamoDB

Some of it is also tied with issues with Shopify, if the name of the customer isn’t on the customer profile by the time the order is created, then it’S impossible to add the name to the order at a later date, which then forces us to fix in the integration layer

Source system validation is the only way to deal with that.

preaching to the choir 👼

I love hearing feedback, currently work at Celigo, and used it for a few years before joining. Also built out custom scripts and what not for other use cases that it wasn't the best for. Like Craig said, that's definitely a source system validation problem. Even if you were to use another product or script, you would have the same issue given the source is providing bad data. What we see a lot of times is defaulting values if they aren't crucial, and full names typically aren't. For example, Amazon, ebay, walmart often only give you first names. I'm happy to help if you need a pair of eyes to look at what you've got.