<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html style="direction: ltr;">
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Ian,<br>
<br>
I'm thinking that what you did results in being able to sell Widget in
several languages and currencies, all sales coming from one inventory.
And that uc_domain would modify the invoices, etc. based on what
country the items were ordered from. Is that correct?<br>
<br>
In this case, Widget would be item 001 in the U.S., item 002 in Canada,
etc. so that an order for it from the U.S. would not come from the same
inventory as an order for it from Canada, and all the downhill books
(sales accounting, distribution) would follow.<br>
<br>
In other words, what you did would seem to be for one company and
source of goods sold to many places, where what I would need is the
company headquarters (with the admin panel) having a distribution
company in each country, each with their own inventory and accounting.<br>
<br>
Jeff<br>
<br>
On 10/20/2010 05:31 AM, Ian Bezanson wrote:
<blockquote
cite="mid:556F4CA7-CFB9-4C52-B2E7-D6C1E296CEAE@ianbezanson.ca"
type="cite">Jeff:
<div><br>
</div>
<div>You'd be better off, and likely have less headache to utilize
the Domain Access module (<a moz-do-not-send="true"
href="http://drupal.org/project/domain">http://drupal.org/project/domain</a>)
to
achieve the latter bit, rather than separate installs, sharing a
database. I've built a multinational, multilingual storefront with
Drupal and Ubercart earlier this year and that was definitely the way
to go - you can manage content per domain, or make it available for all
domains, use different themes per domain, etc. If nothing else, come
upgrade time you will thank yourself for doing it this way as you'll
only have one site to maintain and upgrade - plus then your admin
section IS in one spot, rather than having to fake it together.</div>
<div><br>
</div>
<div>As for general store/reporting separation, take a look at
Ubercart Domain Access (<a moz-do-not-send="true"
href="http://drupal.org/project/uc_domain">http://drupal.org/project/uc_domain</a>)
which
claims to allow "...an Ubercart store to span multiple domains,
storing the originating domain when an order is made and displaying the
correct store information on invoices."</div>
<div><br>
</div>
<div>I'm sure you'll have to do a little bit of exploration to make
it all work together happily, but venture to guess it will be less time
than the other approach.</div>
<div><br>
</div>
<div>Hope this helps,</div>
<div><br>
<div>
<div>
<div><font class="Apple-style-span" face="Arial" size="3"><span
class="Apple-style-span" style="font-size: 13px;">
<div style="font-family: Helvetica; font-size: medium;">
<div><font style="font-size: 10pt;" face="Arial">--<br>
Ian Bezanson<br>
Bezanson IT Solutions<br>
<a moz-do-not-send="true" href="mailto:irb@bits.co">irb@bits.co</a><br>
+1.902.442.8392<br>
</font></div>
<div><font style="font-size: 10pt;" face="Arial"><br>
</font></div>
</div>
</span></font></div>
</div>
<br>
</div>
</div>
</blockquote>
</body>
</html>