Pricing the length of a piece of string

Virtually everyone ends up on this page. Why bother emailing us or arranging a call if our price points are too high?

We would love to provide detailed pricing here so you had all the facts to make a decision about contacting us. But realistically, we couldn’t do that even if we wanted to. The reason is simple. We want to be fair.

If you want us to launch you on eBay UK, with 30,000 SKUs, with poorly formatted data lacking categorisations, on ChannelAdvisor, we could generate a price for that. But what if its 15,000 SKUs? What if it’s on Linnworks? What if your data is excellent? What does excellent data even mean without a point of reference?

Any pricing breakdown we attempt to generate would either be 42 pages long, confusing, inaccurate or unfair.

Let’s also be mindful that our discussions are about fact-finding. Perhaps we ask questions which lead us to a new topic, where a constraint from your side is raised. Or perhaps we identify another issue you have, which we can help resolve.

It would be far easier for us to define all our packages and pricing into a series of grids, dependencies and tables, and make you pick. But you would have a tough time picking, and the pricing still may not be fair. No two situations are identical. There are nuances everywhere. We aren’t hiding our pricing because it’s high or unfair. We are exceptionally competitive. We are simply unable to provide the best possible price without first talking with you.

We aren’t the cheapest online. If you are looking for the cheapest rate out there, that is not us. You can’t deliver excellent service at the cheapest price. But we aren’t expensive either. For the quality, we are unmatched. We are sure you will soon learn that.