<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I'll cautiously agree with that sentiment :)</div><div><br></div><div><br></div><div><div><font face="Arial" style="font-size: 10pt; ">--<br>Ian Bezanson<br>Bezanson IT Solutions<br><a href="mailto:irb@bits.co">irb@bits.co</a><br>+1.902.442.8392<br></font></div><div><font face="Arial" style="font-size: 10pt; "><br></font></div></div><div><div>On 2010-10-20, at 10:40 AM, <a href="mailto:jeff@ayendesigns.com">jeff@ayendesigns.com</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Right. What I meant is that it's not 'really' separate product catalogs, such as, for example, having a separate catalog taxonomy for each location, that it's one big catalog that appears (fudged) to be separate catalogs via controlling the visibility of each node.<br><br>On 10/20/2010 09:37 AM, Ian Bezanson wrote:<br><blockquote type="cite">Oh sorry... let me rephrase a bit. No need, whatsoever to fudge the catalogs by domain, that's actually part of the domain access modules. You have the ability to "show on all domains" or pick specific domains to show each node on. So it should be extremely easy and straightforward to manage that bit. I think we had set up separate payment processors for each domain, as well (this may have been a custom module, IIRC), so that piece is doable as well.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Cheers,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote></div></blockquote></div><br></body></html>