Multi-store checkout Miva vs Magento

[godogo]

I see some discussion on the Miva forum on this subject, but I'm not finding a definitive answer. How easy/difficult is it to share and manage multiple stores, under multiple domains, with the same checkout in Miva?

I have a potential client looking to do this with a number of sites, and they already have one or two sites made with Magento (not multi-store checkout). I have been recommending Miva for other reasons, but it appears that Magento offers a simple solution for multi-store checkout, which has me scratching my head.

Anyone have advice on this? I have not use Magento before, so I don't know what I would be getting into with it.

[Bruce - PhosphorMedia]

Re: Multi-store checkout Miva vs Magento

The issue is that it all depends exactly what they are looking for when they request "multiple stores" with a single checkout...that's why there is no 'definitive' answer.

However, for most specific senerio's there is an answer.

[godogo]

Re: Multi-store checkout Miva vs Magento

Ok, I'll try from another angle, then. But I have to say, I have looked quite hard for the answer I am looking for with Miva, and the best I can find is this thread here, which is from 2010: Five Stores, One Checkout

Referenced in that thread, this Miva store does what I am looking for with three domains (tabs between three stores that have different look and feel, etc.. but share same cart). As stated in the post that site required "about 40 hours worth of PS work" in one instance and a "semi-custom" package in another case. So obviously it can be done - but I'm not assured about the ease of management with this setup in Miva as compared to what Magento offers out of the box. But I also don't know the pitfalls of Magento, so right now I'm just trying to weigh my options.

[Bruce - PhosphorMedia]

Re: Multi-store checkout Miva vs Magento

Near as I can tell, the store mentioned has three 'sites' (meaning different URLs) feeding a single domain's cart. This could be done in several ways. But the most basic is that each "url" calls into the cart's Merchant system and a conditional test determines what to return based on the URL called. The products could be segmented by using Top Level Categories for each product set.

As for maintenance, you'd have a single Order System to interface with for back end and order management. On the front side, it might be a bit complicated to manage the templates, but some additional custom work could be made to simplify that. For example, using different Page Templates for each Store.

As for whether this would be easier in Magento or Miva, I think the problem with an answer is that anyone who knows enough about Miva to pull this off, probably knows not enough about Magento, and visa versa. However, the one advantage of going with Miva is that you wont be using Magento<g>.

BTW: I have no idea of why one would really want to do this outside of the fairly Minor advantage of distinct URLs for individual brands, which could be done with simple product pages for each. Personally, from a shoppers stand-point...its confusing...

[Kent Multer]

Re: Multi-store checkout Miva vs Magento

Hi, I may be the person who wrote the "semi-custom" package you read about in the forums. I have a module that lets one Miva store have two or more different designs or "looks," depending on the URL by which a visitor enters the store. The design changes are created by having certain page-template elements, such as the header and footer, that can be switched to have different content, depending on the URL.

I've provided this module to several different Miva stores in recent years. If you're interested in a copy for your store, you can drop me a line by email to discuss it further.

Thanks --

[Rick Wilson]

Re: Multi-store checkout Miva vs Magento

The second post referenced something we did directly as well. There aren't any modules actually needed, but simply custom JS.

Also AFAIK Magento only supports multi stores at the Enterprise Level which is $15k a year just for the licensing.