When do developers choose to integrate natively with ecommerce platforms, and how do they use Rutter's range of integrations to complement it?

I would say the typical customer journey is that they usually have one or two integrations already and they have five to seven more planned for the roadmap. They probably have a Shopify integration. The second one might be WooCommerce, or it might be Amazon. That's what we've usually seen. Then they have Squarespace, BigCommerce, Wix and so on planned.

The journey for a customer working with Rutter is that they start using us for the longer tail. What we see is that most migrate over their existing connections from Shopify, Amazon or WooCommerce onto Rutter. If you maintained your own native integration and use Rutter, you're not entirely solving the problem of completely abstracting the integrations away. You're still dealing with, let's say, two integrations, one being Rutter and one being Shopify. It makes way more sense from the developer standpoint to just work with one and have that one integration provider be responsible for everything. We usually see this happen when developers run into maintenance issues. Shopify's API updates every quarter, and there might be breaking changes. When something like that happens, that's when a developer says, “Okay, it’s time to migrate over and just use Rutter.”