Retail & Wholesale MM5 with different style templates?

[Arthur_B]

I've worked with Merchant since ver 1.x something up through compiled ver 4. and have used a lot of everyone's modules, but I have not yet tried anything in ver. 5.

My question: Is it possible to create a dual template system to deliver completely different pages to a "standard" visitor as opposed to a "dealer" that is logged into a restricted area? They would have different information and different sized images for an identical part number.

Example: the general visitor would see a large product image, with additional images available, a long part description, warranty info, etc. whereas the dealer area would show a line item layout with small image, UPS & package sizing info, UPC and other wholesale related items. This would be a catalog only site, with no selling therefore no cart/checkout function needed.

I am trying to decide whether to attempt this in Merchant or look elsewhere for a catalog engine. MySQL is a must.

Thanks to anyone that can advise me on this.

[Vic - WolfPaw Computers]

You could do this, however it would take basically duplicating the product page as a custom page. Redirect the 'wholesale' customer to the custom product page after login, and use a conditional to test for login and membership to the wholesale group to ensure the right information is displayed.

It will take a good deal of work.

[Arthur_B]

Ouch! Thanks Vic.

Guess I need to look for other solutions that will allow use of multiple templates.

[Vic - WolfPaw Computers]

You can use multiple templates. There are a few vendors for this.

However, in order to do what you're asking - restricting the view based on being a member of a specific group, you'll still have to conditionalize the template content.

I know of no module currently that can switch template display on the fly like that.

[wcw]

Quite easy. Each page template would be conditional.

<mvt:item name="toolkit" param="pgroup|pcount" />
<mvt:if expr="g.pcount GT 0">
show price group page template code
<mvt:else>
show standard page template code
</mvt:if>

This uses one less than $30 3rd party module (tool kit) to determine if the customer is in a price group. Each page in the store can be customized with this simple technique.

[Arthur_B]

Thanks Bill! That's very interesting.

Could one also use conditional arguments to modify the display of category headers and sidebars for two different product groups, or is there already some form of category store display module available?

I was getting ready to ask if two Merchant 5 installations could process data from the same MySQL database in order to have the separate presentations for retail/wholesale, but what you suggest seems easier and more elegant.

[wcw]

A conditional could be used the same way. For example if one product group had the characters XZ in the product code, you could check for that. If present, show one, else, show the other.

[ids]

I've worked with Merchant since ver 1.x something up through compiled ver 4. and have used a lot of everyone's modules, but I have not yet tried anything in ver. 5.

My question: Is it possible to create a dual template system to deliver completely different pages to a "standard" visitor as opposed to a "dealer" that is logged into a restricted area? They would have different information and different sized images for an identical part number.

Example: the general visitor would see a large product image, with additional images available, a long part description, warranty info, etc. whereas the dealer area would show a line item layout with small image, UPS & package sizing info, UPC and other wholesale related items. This would be a catalog only site, with no selling therefore no cart/checkout function needed.

I am trying to decide whether to attempt this in Merchant or look elsewhere for a catalog engine. MySQL is a must.

Thanks to anyone that can advise me on this.

If you stuck with MM4.24 and OpenUI, I have a module that allows you to set up Wholesale pricing (per customer) without the need for multiple templates or stores because it deals directly with the pricing. Basically, your store prices are by default like retail untils your customer logs in. If they have negotiated prices for your stores products, that is what the customer will see and receive when checking out. Just look for the "Wholesale Pricing" module at MivaCentral or directly on my site: http://www.southbound.com.

A direct link: has more info about it also:
Product: http://www.southbound.com/Merchant2/agent.mv?AG=scotts&SC=PROD&S=southbound&P=IDS_WHOLESALE

[Arthur_B]

Example: the general visitor would see a large product image, with additional images available, a long part description, warranty info, etc. whereas the dealer area would show a line item layout with small image, UPS & package sizing info, UPC and other wholesale related items. This would be a catalog only site, with no selling therefore no cart/checkout function needed.

The difference in pricing is an important, but only one part of how the general visitor pages would need to be unique from the dealer pages. The dealers need a bunch of arcane data as per the above, while the visitors just need to see some pics of stuff that fits their vehicle. Since this is not a retail site, they won't even be given pricing.

I think that the code examples that Bill provided in one of the higher posts should do the trick, and since MM4 isn't getting any younger, I'm looking forward to getting involved with MM5. Thanks for the input, though.

[ids]

The difference in pricing is an important, but only one part of how the general visitor pages would need to be unique from the dealer pages. The dealers need a bunch of arcane data as per the above, while the visitors just need to see some pics of stuff that fits their vehicle. Since this is not a retail site, they won't even be given pricing.

I think that the code examples that Bill provided in one of the higher posts should do the trick, and since MM4 isn't getting any younger, I'm looking forward to getting involved with MM5. Thanks for the input, though.


I understand that point of view, of looking ahead at MM5. I've been trying to get to developing for it for a while. I've been too busy with MM4/OUI stuff and until recently, docs were scarce.

I'm not trying to push my mod, but get more info out there. And I believe MM4/OUI is still relevant. The Wholesale Pricing mod will work with the template modules, VC and DT. So, you could create the scenario you're talking about: If Logged in; display ArCANE DAta Else; show very littlel info.
All the Leggos exist already for a MM4/OUI version of your scenario. They may not for MM5 yet.

I do plan on WP for MM5, just of matter of creating "my time." Maybe it will be a candidate module for you when I get to it.

Best Regards,

Scott

[Arthur_B]

Would love to know if you do a WP module for MM5. Too bad MM4 can't utilize a MySQL database. That's something I know I want for this one.

[Arthur_B]

Quite easy. Each page template would be conditional.

<mvt:item name="toolkit" param="pgroup|pcount" />
<mvt:if expr="g.pcount GT 0">
show price group page template code
<mvt:else>
show standard page template code
</mvt:if>

This uses one less than $30 3rd party module (tool kit) to determine if the customer is in a price group. Each page in the store can be customized with this simple technique.

OK, Bill -- I've got the modules installed. I don't understand yet what the "g.pcount" refers to, but let me see if I'm getting some clue here.


<mvt:item name="toolkit" param="pgroup|pcount" />
<mvt:if expr="g.pcount DEALER 0">
DEALER_PROD
<mvt:else>
PROD
</mvt:if>


Would this expression, when added to the top of the page templates for both the standard product page and a price group (DEALER) product page template called DEALER_PROD, give the different pages to those different visitors?

If so, then would one make a similar expression for the category pages and whatever other pages need to show as different to those groups?

Thanks!

[Pete McNamara]

Try: <mvt:if expr="g.pcount GT 0">

instead of: <mvt:if expr="g.pcount DEALER 0">

GT means Greater Than.

[Arthur_B]

Just wanted to let Bill know that I got this retail/wholesale-page-thing working for the Team Xenon catalog and I'm stoked! He was very patient with me over the weekend helping me get up to speed on using his toolkit module and although it sure took me long enough to figure out exactly what I was supposed to do to implement the if/else conditionals as he suggests above, once I had my mini-Eureka! moment it all came together.

Thanks again, Bill. And -- anyone contemplating getting his toolkit module -- do it!