Thanks all, good thread - keep ‘em coming - will definitely check the examples there!
I’m not (you’ll be surprised to hear) particularly focused on WordPress per-se in this equation. Obviously it’d be the end point for us and any users given that it’s the tool we use for presenting web content, but it’s part of a bigger question which is everything you’ve all outlined below.
You get almost close when you look at tools like
https://www.bookthatapp.com/ which says it’ll do tickets but within Shopify - but talking to the developer they say none of the event data is available via any kind of feed or API, which again means this sits there as a source of duplicate / silo’d data.
I think Ben’s point is an important one - figuring out which of these systems is a “core” one and then hanging other stuff off it is probably the only way to go. But it’s still altogether a bit unsatisfying, IMO.
Maybe...
1) ..it’s just too hard to build anything other than totally bespoke systems (which then automatically rules out smaller / poorer orgs)
2) ..users actually don’t care that much and are perfectly happy to bounce around from system to system. Maybe users don’t need a membership and some merchandise and a ticket all in one place and it’s just museum wishful thinking that they are going to buy all these things..
Is there any research in this space, either on systems, or on usability, or on conversion rates, or comparative analytics?
If not, why not? Seems odd given that many would argue that museums really need tools to help them market and sell more effectively...
cheers!
Mike