The question I have in all of this is: why are you doing it the way you're doing it?
First off, a domain name should always have a root page. So your root page in the case of surprisecitystore.com shouldn't be surprisecitystore.com/store, but surprisecitystore.com ... period. This ensures that the URL is both user-friendly (easier to type in) and search engine friendly (root page is always first to be indexed and the one that tends to be easiest to rank for keywords and phrases.)
So why not redirect surpriseaz.com/store using a 301 redirect (permanent web redirect) to surprisecitystore.com , if you're going to do anything? This makes much more sense.
Show your director this thread, too. I'm sure that others will chime in at some point. (Chris, Steve, Forrest, John, st0x...l'il help?)
As far as a 301 redirect is concerned (this is the correct redirect for your circumstances), this would depend on the language(s) supported on the server containing the site doing the redirecting (in this case, the surpriseaz.com site). Here's a sample using ASP:
The last line's important or Googlebot (among others) will choke on the redirect.
Hank: I'm not trying to lay blame or be accusatory here. I'm just trying to explain that the process/idea you have been given isn't the best way to do things.
If your director wants his way on the issue, the only way you're going to pull that off with your existing setup is with frames, and that's a death sentence for an e-commerce site (SEO is next to impossible on a frames-based site and users quite often get confused when they click different links and the address bar doesn't change).