Neil McQuillan - CEO Citrus-Lime Do you know how you will decide what functionality to develop inhouse for the benefit of all (that we are already paying for) and what you will outsource as an optional extra cost to us?

Lyndon Hollands It largely comes down to demand and the resourcing requirements inhouse.

For example if, as we have done, we put resource into the new backoffice that brings productivity gains to thousands of users, we estimate this saves 15 minutes time per user per day so there is a real return for all our customers.

More niche functionality we are happy for partners to innovate and present products on the Cloud POS Marketplace.

There isn't really a hard and fast rule, but import/export is asked for by a handful or power users, and TurboMT's product is far better than something we could have produced inhouse with its Excel driven import/export and use of the API to retrieve and allow you to set facets in Excel. If we'd done something it would have been simple and CSV based.

The product is worth a whirl if you have a lot of batch changes to make its really cool.

Thanks for the explanation, that context is helpful, and I completely understand how demand and internal resourcing drive prioritization. Focusing on improvements that deliver broad productivity gains across the customer base makes sense, and I appreciate the transparency around how those decisions are made.

I did want to offer a bit of perspective from the bike retail side. Many independent bike shops have historically been slow to adopt e-commerce, but that’s starting to shift quickly. As shops begin to take online product listings and inventory synchronization more seriously, basic import/export functionality (images, titles, descriptions, etc.) is likely to move from a “power user” request into a more common operational need. In that context, even a simple CSV-based solution could remove a meaningful barrier for shops that are just starting that transition.

I also wanted to ask about options within the Marketplace itself. At the moment, TurboMT appears to be the only viable path to achieve this functionality, which effectively makes it a paid requirement rather than a choice. Is it possible to submit an open-source or low-cost solution to the Cloud POS Marketplace that covers this use case and can coexist alongside TurboMT? That would preserve partner innovation while giving smaller shops an entry-level option that aligns with tighter budgets.

I’m not advocating for replacing TurboMT — it clearly offers advanced capabilities and value — but rather for enabling an alternative that lowers the barrier for shops that need basic batch import/export without committing to a full third-party product.

Appreciate you taking the time to consider this, and I’m happy to discuss further if helpful.