PageDNA ordering sites provide a variety of ways to collect money from your customer - the end-user of the online ordering system. Options may be direct or indirect - these options are explained in this document.

This is - by far - the most common configuration, wherein a billing code (cost center, PO Number) is collected from the end user on the Shipping page. This number can be verified in a number of ways, detailed elsewhere in this documentation. Generally, a report of order activity is generated at the end of the month and a summary invoices is sent to the contact at the end-user corporation for remittance of payment.

Similar to collecting billing codes, the system can collect a credit card number from the user, which is later run manually through whichever terminal you use. While the system does not actually authorize funds in this configuration scenario, the system CAN verify that the credit card number is valid for the appropriate card type chosen, that the expiration date has not passed, and that other required fields have been completed (name on card, cardholder's phone).

NOTE: Although we verify that the card number has a correct format, we cannot verify that it is a legitimate card unless you use real-time credit cards (see the next section).

In this scenario, access to credit cards is given through a specific menu item named "Credit Card Manager". We request that access to this tool be restricted to only those individuals in your firm who need access to credit card numbers as part of their job functions. You can learn more about this tool in our Site Configuration documentation.

We can do real-time authorization of credit cards, wherein money is actually moved between accounts. We can integrate with a number of different payment gateway processors including our default gateway, Bank of America Merchant Services, as well as PayPal PayFlow Pro (formerly owned by Verisign), Authorize.net and CyberSource.

	Note
	Because of the complexities involved with coordinating between PageDNA, gateway processors, and banking systems, setting up real-time processing can easily take ten (10) or more business days. Please note that your site can work in "offline" processing mode while you get the automation in place.

Bank of America Merchant Services - PageDNA’s Default Gateway Provider

Figure 1.1. Bank of America Merchant Services Logo

Bank of America Merchant Services is a provider of credit card processing services that has a special relationship with PageDNA. The first time we activate your Bank of America Merchant Services account on one of your sites, PageDNA charges $250 - no additional monthly fees are charged on our end. For sales questions regarding Bank of America Merchant Services, please contact them directly.

How to Contact Bank of America Merchant Services: contact Chuck Gorski at Bank of America Merchant Services directly:

Chuck Gorski
Bank of America Merchant Services
858.829.1420 cell
402.315.5090 fax
charles.gorski@bankofamericamerchant.com

Other Supported Gateways

For non-default gateways, PageDNA charges $500 for the first time we link a site to a particular real-time credit card gateway. An additional $50/month fee is also charged (either per site or across your entire account - depending on your plan) for using real-time credit card authorization. The non-default gateways we currently support are Authorize.net, Cybersource, and Payflow Pro.

When using real-time credit card authorization combined with our approval interface, we pre-authorize when the order is placed. When the order is approved, the card is actually charged. Alternatively, we can set your site to AUTH-only mode, which allows you to have realtime verification of credit cards while retaining complete control of when cards get charged.

Real-time Credit Card Activation

In order to use real-time credit card activation you will need to set up a processing gateway. The providers that we integrate with are Authorize.net, Cybersource, and Payflow Pro.

Figure 1.6. Activate_request

Once you have a gateway set up using one of the PageDNA supported gateway processors you will need to request that we activate that gateway in our system for you. To do so, go to the Credit Card Activate link on your Storefront Menu and contact support@PageDNA.com. At that point you will be asked to provide certain detail about that gateway in order for us to enter it in to our system. There is a fee for setting up each different gateway. Support will be able to advise you on the pricing for that.

After you have a credit card processing gateway setup in our system, return to the Credit Card Activate option in the Storefront Menu. Now you'll be presented with choices for configuring real-time credit card processing. Mark the check box to activate real-time credit card processing, select your preferred charging mode, choose they currently type, and click the Apply Changes button.

Figure 1.7. Activate_options

So long as you are using the same gateway, you may now activate real-time credit card processing on any of your sites without additional cost or need to engage support for assistance. If you need to use different gateways for different Storefronts then there will be a cost for setting up each of those gateways. Contact support@PageDNA.com for assistance.

PageDNA can 'punch-out' to PayPal's system very easily. Following are the steps to take:

PageDNA supports collection of sales tax during the ordering process. This is critical for sites with real-time credit card authorization as it allows the complete order total to be charged at the time of order submission.

Tax information is shown to users on the "Review" or "Billing" step (or both) of the ordering workflow. When the order is submitted, the tax rate and amount collected is also stored in the database where it can be accessed in Reports. Items or components of orders can be marked non-taxable if necessary - for example, you might not want to have shipping taxable.

On behalf of our customers who need to collect sales tax in the United States and Canada, we receive and install monthly updates of US/Canada tax data prepared by a third party provider - Tax Data Systems. We cannot offer geographic-based tax rates for countries other than US/Canada at this time, but we do support setting a single site-wide tax rate if desired. For example, in Australia there is a flat tax of 10 percent (GST) which is supported by our platform.

To activate sales tax collection, you need to specify prices for your items and you need to use the Tax Settings menu item.

It's necessary to make sure to use two-character state or province abbreviations ("WA") in the Ship To address section and to make sure the country code is "US" (or "CA") if you also support international deliveries on your site.

Let's say the client name is AAA Printing, with their own homepage of www.aaa-printing.com.

The options are:

Please note that nationsprint.com has always been intended to separate PageDNA from the URL of the ordering sites. To accomplish this the homepage is completely blank - there is no link from nationsprint.com to PageDNA through the web.

	Note
	Regardless of which option you choose, your site will always be available through the default URL of http://www.nationsprint.com/clients/SITE/ -- virtual hosting is just an alias for an existing site.

Using a subdomain (#1) is an excellent way to reinforce your companies' presence on the web without needing to make changes to the site continuously.

Using a frames page (#2) allows the simplest integration into your current web site, but requires your webmaster to make the changes every time.

Using a new domain (#3) is a very easy option and makes the web site have that familiar www.domain.com sound, instead of the unfamiliar subdomain.domain.com; the only hard part is finding a domain not already taken.

Finally, using subdomain.BCOS.com is the easiest option of all. No technical work is required from you - just ask PageDNA to take care of the details.

After you understand your options and are ready to request a virtual host, visit the Menu for the first storefront you'd like linked to a new virtual host, and choose the "Virtual Host Setup" menu item. You will be presented options to add a Secure or Non-Secure (regular) Virtual Host - or link your storefront to a previously established virtual host, if you have one.

Choose the option you wish, fill out this form and submit your request. For Secure Virtual Hosts, our upport staff will contact you within 1 business day with further instructions. Plan on up to one business week to get your virtual host established.

New non-SSL vhosts are active immediately. Use the Virtual Host Setup item in the menu to purchase and create your vhost. The setup will check if the DNS record for your name is valid - it must be a CNAME reference to www.nationsprint.com before purchase will be allowed.

Note that your storefronts' default URL using the "nationsprint.com" domain name will automatically redirect users once a virtual host is established - so you can safely add Virtual Hosting after a launch with no disruption in customer experience. Customers clicking old nationsprint.com links (for example, in a reorder link found in an older Confirmation Email will shuttle automatically to the new virtually hosted domain.

After Virtual Hosting has been configured for at least one storefront, the Virtual Host setup allows configuration of a second URL for a virtual hosted site. This is useful if you change a sitename - The main site URL (used for outgoing emails) can change, but the old URL will continue to work.

In this case, we have a site named green-123, perhaps because the sitename "green" was already used. With the Virtual Host, we can simplify the main URL for the site as orders.myprint.com/green. That main URL will be used for all outgoing emails. But orders.myprint.com/green-123 will also work, in case someone has bookmarked that site.

Secure Virtual Hosting (secure vhost) allows you to access your vhosted sites via SSL/HTTPS while showing the padlock icon that gives customers confidence in site security. Because secure vhosts require additional setup and an IP address, they are more expensive: $250 per year.

	Note
	Special SSL certificates cost extra, such as Extended Validation (EV) certs and wildcard certs.

If you own the domain, you will need to procure the SSL certificate. You can use any SSL provider (ask support if you need recommendations). We will provide you with a CSR (certificate signing request) after you give us the following information (sample information is in brackets):

Country Name (2 letter code) [US]:
State or Province Name (full name) [California]:
Locality Name (eg, city) [Redwood City]:
Organization Name (eg, company) [My Company Ltd]:
Common Name (eg, web hostname) [orders.example.com]:

Please specify whether this vhost will be used for a single site or multiple sites.

After we get the information for your CSR, we will set up a special CNAME target for your hostname. It will look something like ssl-yourhost.nationsprint.com -- see Setting up CNAMEs. for general info about checking your setup.

When you choose a subdomain or a new domain, you should tell support whether you intend to connect the vhost to a single site or multiple sites. If only one site, please specify which site you'll be using. A single-site vhost will map your vhost (e.g. http://example.com/) directly to the site; with a multi-site vhost, each site will need to be specified as part of the vhost URL (e.g. http://example.com/SITE1/ and http://example.com/SITE2/). Note that if you ever change a single-site vhost to multiple sites, you will need to notify all your customers that the site URL has changed.

With a multi-site vhost, you need to link up each new site that you create. This is done through the Site Menu, using "Virtual Host Setup". If your site does not have SSL enabled and you select a secure vhost, your site will be forced to SSL mode.

	Note
	With a multi-site vhost, the main vhost URL (e.g. http://example.com/) will return "Forbidden" (HTTP error 403). This works exactly the same as going to http://www.nationsprint.com/clients/ -- you need to add a trailing SITE to the URL.

To verify that your CNAME is set up correctly, you can use the "host" or "dig" tools on a Mac or Unix machine (dig is mostly useful if you want to see your DNS cache time). On Windows, you can use nslookup.exe. There are also web-based tools that you can find by searching for "dns lookup cname".

Make sure that your CNAME points to www.nationsprint.com -- here's sample host output showing what you should see:

$ host -t CNAME order.example.com
order.example.com is an alias for www.nationsprint.com.

PageDNA offers a Shipping Cost Calculation module which provides your end-users instant and accurate shipping costs using a direct connection to UPS.

The system computes shipping costs by requesting an actual UPS rate for moving that much weight from the shipment origination ZIP code to the users "Ship To:" address.

The system can optionally calculate a markup based on percentage and/or handling fees, and the shipping rate is optionally taxable, depending on your needs.

This feature is most commonly used on sites with real-time credit card authorization, where an accurate shipping cost must be shown to the user before "checkout" takes place.

After the shipping page, users are presented with a page showing their current order cost sub-total, followed by a drop-down list of the various shipping methods you have opted to allow your users to select. Each option also lists the price for that method (ie, 'Second Day Air - $25.34').

When the user changes the shipping method by releasing the mouse, a new total is calculated using JavaScript and displayed for the users approval.

Shipping cost calculation can be added to any site. Contact support@PageDNA.com to initiate this process. Following is a list of information PageDNA needs to activate this feature. Please send this information in with your request and allow 10 business days for activation:

You will need to calculate the weight per 1000 count for each product on your site (in pounds) and enter this into the 'weight_per_1000' field found in the "Item Editor" Menu item.

Covers the options our software offers for restricting access to sites.

Our sites can be password-protected. This means that, when an end user clicks on a link to a site, and if that site is password protected, then the user's browser pops up a window asking for a username and password. Usually there is one username for all users. (There is always one password per username).

We can also allow ranges of IPs to get into sites without a password. An IP is generally tied to where a computer is located physically, so by getting the IPs of the customer's network you can let them get into a site without always asking for a password.

Finally, if the user does not have or does not remember the password, we can present a "403" page which helps them get into the site automatically.

Related topics such as secure server/HTTPS and the restricting options on the authorization pages are also touched on briefly.

Usernames and passwords are case-sensitive. We cannot make the passwords case-insensitive. That means that if the user enters, 'HELLO' and the username is 'hello' then the user will not get through. When communicating passwords, it is best to mention this. Also, for this reason it is better to use all-lowercase as it is easier to remember that.

The list of usernames and passwords resides on our web server in a per-site area. It can be fully managed by you (PageDNA’s client) through a menu system, and even by designated people at the customer.

Passwords are scrambled by our system when they are added to our web server. This means that they cannot be recovered, our server cannot e-mail the password back. PageDNA recommends that you (PageDNA’s client) write the password down for this reason.

Instead of a list of IPs we could also check for a domain name. How this works is that our server will check to see if the user's computer's IP matches up to the given domain name. This method is convenient when it works but it doesn't always work; the customer's IT department must have set up "Reverse DNS lookups" for thier entire network.

PageDNA can "harvest" the IPs that have been used on the site from the web server log files. In this way you (PageDNA’s client) can get partial coverage of your customer's IP addresses without bringing thier IP addresses into the loop. This is really most effective if the site was accessed by the customer, repeatedly, from a few different locations.

When a user tries to log in but they cannot, then the web server will return a page explaining that authorization is denied. This page is as helpful as possible and gives the user options to:

Option #2 is useful if the username/password is fixed; it will be up to the customer to create and post that intranet page.

Option #3 will only accept e-mails with domain names specific to the customer. For instance, if it was the Acme site, only @acme.com emails would be accepted.

Also, on option #3, a temporary username and password can be generated, instead of using one fixed username/password. These passwords will only last one day.

Secure Sockets Layer, or HTTPS, is supported by PageDNA. As long as you are accessing through the www.nationsprint.com domain this is very easy to do: access the site through https://www.nationsprint.com/clients/(sitename) intead of http://www.nationsprint.com/clients/(sitename) - it is that extra 's' after http that asks for a secure connection. We can also have the site automatically switch users to secure connections, even if they arrive from an insecure connection.

Just because it's called a secure connection, doesn't mean its secure. The security it provides is the security of knowing that no-one could possibly be listening in to your browser and PageDNA’s server exchange information; but a secure connection doesn't stop unauthorized people from placing fraudulent orders - that is what the password/IP schemes detailed above do.

Another way of stopping unauthorized people from placing orders would be to have a billing code (cost center, GL code, etc.) that is entered on the Authorization page checked against a database. For this to effectively stop unauthorized users it must be a free-entry that is checked against a database, not a drop-down list.

Email delivery issues are a growing issue as spam protection services become more and more common. It is common for users to have individual and/or corporate email filtering software controlling delivery of messages. Email messages from foreign sources may be treated as suspect.

Diagnosis

You can see, without any ambiguity, which email address every email for a given order (confirmation, approval, etc) has been sent to by our system by following these instructions:

1) Visit the hub and login if necessary. Quick link to the hub: http://www.nationsprint.com/hub.

2) Type the order number in question into the "Find Order" dialogue at the top of the page and submit the button. This will take you to the site in question and display the entire order history in a list at the top of the page.

3) If you see a valid email address in this report, but the user reports that they did not receive the email, there is something blocking the email from being received on their end. This can range from local "spam filtering" settings n your customer's personal email application, all the way up to global spam filtering issues at the corporate level. Sometimes there are combinations of factors.

Customer service info is very important because this information determines in part how the emails appear to your customers - and whether or not they are blocked by spam filters.

Customer service info is edited in the Menu at:

Global Site Info > Edit Customer Service Info

If your customer service address was - for example - set to: customerservice@yourdomain.com

... you would want your customer to search their spam filters and/or ask their IT administrator to "whitelist" this email address so they can get their emails unhindered.

Fixing Problems at the Corporate Level

Figuring out who to contact inside a corporation to see that the email filtering is not blocking emails is something outside PageDNA’s scope of operations but if you are persistent you can often get whitelisted on the corporate level if you are dealing with a good IT department and get the right contact. We suggest first your customers check any "local" spam folders, and if they don't find our email there, that you escalate and get in touch with their IT department. You can use the Order Action Console to send yourself a copy of the confirmation emails.

Overview of WebLink integration. This integration option allows order data from PageDNA to flow into the Printer's Plan suite of Print Estimating and Print Management software. You can learn more about their offering at their website.

WebLink is a specific integration option Printer's Plan - a firm separate from PageDNA based in Maryland - offers that lets PageDNA order data flow into the Printer's Plan system. An overview of this part of their system is found in the WebLink portion of Printer's Plan's site: http://www.printersplan.com/tour-weblink.php.

Their WebLink documentation is at: http://www.printersplan.com/_docs/WebLinkUserGuide.pdf.

Essentially, you use a feature in our "Vendor Email" to send data into Printer's Plan. The WebLink integration tools pick up that data (and attachments) from this point, preventing re-keying of key order data.

Configuration on the PageDNA side is performed in the "WebLink" part of the Vendor Email. Each of your sites needs to be configured independently. A basic configuration is shown below - this should get you started.

Figure 7.1. Example WebLink Setup

Our understanding is that Printer's Plan has an integrated email client of sorts - within Printer's Plan you will make configuration changes to grab emails from an email address... it downloads our Vendor Email, and parses out the relevent lines from the "WebLink" part of our email including the attachments.

One customer using this feature wrote us the following:

In order to get it to work, on the vendor email you have to:
 
-Turn off file attachments
-Turn off link in URL at bottom of vendor email
-Disable display tracking number in barcode font
-Disable show item barcode HTML email format used

Then, in Printers Plan under WebLink > Link Key Fields you have to enter the text:
 "Tracking #:" (no quotes) next to the field "Each Item starts with this field"

If the site is password protected, the EPS will not import.  Only
the first order and graphic are imported at this time.

Please be sure to make use of Printer's Plan internal support to help you with details on that side of the fence, and let us know if you have any questions we can help with.

PageDNA offers a "Standard XML Integration" designed to facilitate three data exchange processes with outside systems (be they MIS, back office, or other e-commerce front-end):

We have three XML formats - one for each of the three data feeds above. Below are links to documentation with samples showing the data we both send and receive to make these exchanges possible.

How data is transmitted: We support pushing the data over: FTP Pull (from us), FTP Push (to you), HTTP POST (web post). We pass this data over the fence, and once you get these XML files from us, the import into the third party system is the responsibility of the MIS provider, consultant, or internal scripting team.

Our file format is based on the cXML OrderRequest DTD. Here is a sample:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cXML SYSTEM "http://xml.cXML.org/schemas/cXML/1.2.014/cXML.dtd">
<cXML payloadID="fastrackids.F1211I.0417.120@PageDNA.com" timestamp="2008-04-17T13:36:26-08:00" xml:lang="en-US">
<Header>
<From>
<Credential domain="Ad-hoc">
<Identity>not used</Identity>
</Credential>
</From>
<To>
<Credential domain="Ad-hoc">
<Identity>not used</Identity>
</Credential>
</To>
<Sender>
<Credential domain="Ad-hoc">
<Identity>PageDNA</Identity>
<SharedSecret>not used</SharedSecret>
</Credential>
<UserAgent>Printra Stationery Ordering System</UserAgent>
</Sender>
</Header>

<Request>
<OrderRequest>
<OrderRequestHeader orderID="F1211I" orderDate="2002-08-11" type="new">

<Total><Money currency="US">0</Money></Total>

<!-- shipto -->
<ShipTo><Address addressID="">
<Name xml:lang="en">Acme International, Ltd.</Name>
<PostalAddress name="default">
<DeliverTo></DeliverTo>
<Street>123 Anystreet, Suite 200</Street>
<City>Anytown</City>
<State>CA</State>
<PostalCode>90001</PostalCode>
<Country isoCountryCode="US">United States</Country>
</PostalAddress>
<Email/>
      <Phone>
        <TelephoneNumber>
          <CountryCode isoCountryCode=""/><AreaOrCityCode/>
          <Number></Number>
        </TelephoneNumber>
      </Phone>
</Address></ShipTo>

<!-- billto -->
<BillTo><Address><Name xml:lang="en"></Name></Address></BillTo>


<Shipping>
  <Money currency="USD"></Money>
  <Description xml:lang="en"></Description>
</Shipping>


<Tax>
  <Money currency="US">0</Money>
  <Description xml:lang="en"></Description>
  <TaxDetail category="sales" percentageRate="0.0">
    <TaxAmount><Money currency="US">0</Money></TaxAmount>
  </TaxDetail>
</Tax>



<Contact role="buyer">
  <Name xml:lang="en">Jane Doe</Name>
  <Email>jane.doe@acme.com</Email>
</Contact>


<Comments xml:lang="en-US"></Comments>

</OrderRequestHeader>
<ItemOut quantity="250" lineNumber="1">
  <ItemID>
    <SupplierPartID>1ST</SupplierPartID>
  </ItemID>
  <ItemDetail>
    <UnitPrice><Money currency="US"></Money></UnitPrice>
    <Description xml:lang="en">Business Cards</Description>
    <UnitOfMeasure></UnitOfMeasure>
    <Classification domain=""></Classification>
    
  </ItemDetail>
  
  <Comments xml:lang="en-US"></Comments>
</ItemOut>
<ItemOut quantity="250" lineNumber="2">
  <ItemID>
    <SupplierPartID>2ST</SupplierPartID>
  </ItemID>
  <ItemDetail>
    <UnitPrice><Money currency="US"></Money></UnitPrice>
    <Description xml:lang="en">Letterhead</Description>
    <UnitOfMeasure></UnitOfMeasure>
    <Classification domain=""></Classification>
    
  </ItemDetail>
  
  <Comments xml:lang="en-US"></Comments>
</ItemOut>
<ItemOut quantity="250" lineNumber="3">
  <ItemID>
    <SupplierPartID>3ST</SupplierPartID>
  </ItemID>
  <ItemDetail>
    <UnitPrice><Money currency="US"></Money></UnitPrice>
    <Description xml:lang="en">#10 Envelope</Description>
    <UnitOfMeasure></UnitOfMeasure>
    <Classification domain=""></Classification>
    
  </ItemDetail>
  
  <Comments xml:lang="en-US"></Comments>
</ItemOut>

</OrderRequest>

</Request>
</cXML>

In response to the XML POST, a response such as this should be returned. If there is a structural error with the XML, return 500 and an error message. Otherwise return 200.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cXML SYSTEM "http://xml.cXML.org/schemas/cXML/1.2.014/cXML.dtd">
<cXML payloadID="response.F1211I.0417.120@PageDNA.com" timestamp="2008-04-17T13:36:26-08:00" xml:lang="en-US">
  <Response>
    <Status code="200" text="OK"/>
  </Response>
</cXML>

We have provided sample data for a typical export schema below. These fields can be further modified to suit your particular needs - this is intended as a starting point when considering an order export setup. For your convenience, you can download the following information (and a sample export file) at http://www.nationsprint.com/hub/docs/samples/hub_order_export.zip

Shipping carrier and method information is passed by PageDNA using an integer. That number corresponds to shipping methods per the below table. If you do not see a method listed that you need supported, please let us know and we will add it for you.

There's a setting in the XML Export transport that will output extrinsic data representing the item's review info. This is useful for outputting a lot of item-relevant data without creating a big extrinsic map. To use this, set "Item Info Format" to "XML: extrinsic named "item_info" with XML Structured data."

        

        <ItemDetail>
          <UnitPrice><Money
            currency="US">63.5</Money></UnitPrice>
          <Description xml:lang="en">Postcards</Description>
          <UnitOfMeasure></UnitOfMeasure>
          <Classification domain=""></Classification>
          <Extrinsic name="item_info">
            <Option name="Item">Postcards</Option>
            <Option name="Tag">postcard</Option>
            <Option name="Qty">250</Option>
            <Option name="Price">63.5</Option>
            <Option name="Buy Price">None</Option>
          </Extrinsic>
          <Extrinsic name="item_info_configuration">
            <Option name="size">5.5" x 8.5"</Option>
            <Option name="paper">#100 matte cover</Option>
            <Option name="cutter">-</Option>
            <Option name="ink">color front and back</Option>
            <Option name="coating">None</Option>
            <Option name="packaging">None</Option>
          </Extrinsic>
        </ItemDetail>
        
      

This section describes PageDNA’s policies regarding file storage for various parts of the system.

Production artwork files for live orders are stored on the server for 60 days, after which they are deleted. Order files can be regenerated after this point, but there is no guarantee the file will be the same file that was generated for the user initially. See Site Variables for more information.

Preview files generated while a user is ordering (where the order is actually submitted) are stored for 1 year from order date. These files can sometimes be used to "Prove" that a user really was presented with a proof for what they later claim was a production error.

Files that are uploaded by users and included on live orders are stored for 1 year from the date of order submission.

Any end-user uploaded files that are not linked to orders are deleted after 30 days to keep file storage under control.

PageDNA stores order information (but not artwork files) indefinitely. This allows future orders to be re-ordered at any time in the future. The old order data is sent through the current style (layout) on the site. More information on this is found in the Re-Order section of our documentation. Sites that are marked RIP have order data deleted when the site is removed from the server.

As of March 2010, support for older versions of browsers are dropped due to low usage: FireFox 1 and 2, Safari 2 and 3. Support for Internet Explorer 6 will be limited after May 1, 2010. Internet Explorer 8 support officially added. Support for Google Chrome officially added.

FireFox is an excellent browser and has been supported since version 1.0. FireFox 3.5 is the number one browser version across all PageDNA sites.

FireFox 2.0 support ended due to low demand March 2010, however it is expected to function without problems. FireFox 3.0 usage is dropping due to popularity of FireFox 3.5 and may be ended at the next review of browser compatibility.

Internet Explorer 8 is an excellent browser and has been supported since March 2010.

Internet Explorer 8 is the number two browser (tied with Safari 4) across all PageDNA sites.

Internet Explorer 7 is supported with some exceptions. Some advanced administrative tools may not work in Internet Explorer 7. Some layout glitches may occur with Internet Explorer 7 since it has some trouble rendering CSS properly.

Internet Explorer 7 remains reasonably popular with 14% of users across all PageDNA sites.

Apple's Safari is an excellent browser and has been supported on the Mac since version 1.0. Version 2.0 and version 3.0 are no longer officially supported due to low demand as of March 2010, however they are expected to function without problems. Safari on the PC is not officially supported due to low demand however it is expected to function without problems.

Over 96% of Safari users across all PageDNA sites are on version 4, and version 4 is the second most popular browser (tied with Internet Explorer 8).

Google's Chrome is an excellent browser and has been supported on the PC since March 2010. Google Chrome for Mac will be supported once it is out of beta, but is expected to function without problems.

Google Chrome is the 6th most popular browser, just behind Internet Explorer 6.

Internet Explorer 6 presents unique challenges. It is very difficult to install and run on a new up-to-date machine, and has significant incompatibilities in behavior and rendering compared to all other modern browsers. It is extremely old (8 years) and there are much better alternatives available.

Despite this, there are enough users (across PageDNA sites, 6% as of March 2010, the 5th most popular browser), that it must still supported, albiet in a limited capacity:

Please note that Microsoft will end support of Internet Explorer 6 for XP SP2 on July 13, 2010. Major websites have ended support of Internet Explorer 6. Many security organizations and even some countries have recommended against its use.

Browsers for desktop/laptop machines other than the supported browsers will very often function as well. We avoid user agent-specific logic where possible to improve compatibility with all browsers. Alpha and beta versions of browsers are not supported.

The PageDNA storefront system has extensive support for international requirements - we continue to add more support as our business grows rapidly outside the United States.

Below, please find a summary of our capabilities at this moment.  If you don't see something that you need - just ask. Our support staff can help collect your requirements and bring in our development group.

PageDNA supports the ability for a storefront to toggle Its display language between almost any language seen in the list at http://www.microsofttranslator.com  This capability touches storefront template text (site copy and instructions), item descriptions (the "long name" of item as it appears in the catalog) and error messages.

PageDNA Documentation is found at:

http://www.nationsprint.com/hub/docs/html/SiteConfiguration/translation.html

While we can add more, the languages we have worked with so far include:

Example:  English selected:

Figure 16.1. English Selected

User selects Chinese (simplified) from drop down list - storefront display is translated:

Figure 16.2. Translated to Chinese with Chinese Selected

There are other options for changing the language besides the dropdown -e.g. the front page could show the language options and force the user to select before they go further.

We have different mechanism for translating text in emails sent by the system, as well.

We can filter which items are displayed based on the current language, separate from any normal division filtering.

For example, a French Canadian customer may only wish to see the French localized versions of products when ordering, while a US-based customer for the same entity wishes to only see English versions.

Storefront text translations can be provided by a client or sourced by PageDNA. The entire text of a storefront can be downloaded into an excel spread sheet. - We recommend this step after the site is completely configured, all products have been added and the entire system has been tested. That way the system only needs to be translated once. If the translator can translate directly in the excel file, our tools can be used to add the new text th the system quickly and easily by copy and pasting the information. Another option that works well is to take screen shots of the site and allow your translator to provide translations as notations in a pdf file.

PageDNA doesn't currently offer any inline typesetting translation services of documents, but recommends a resource at a third party who may be able to provide dedicated translation services:

Andrew Lindquist | Business Development Manager | Global Translation Services | RR Donnelley

One Embarcadero Center, Suite 200 | San Francisco, CA 94111 | USA

( +1-415-743-4616 |È+1-415-691-1599 || <andrew.r.lindquist@rrd.com> | www.rrdtranslations.com

We support typesetting of almost any type of font: Postscript, OpenType, TrueType, dual-byte fonts. As an FYI, we have live identity programs typesetting Chinese for Fortune 100 customers. The system has provisions for handling North American and international phones differently in the configuration forms, so that identity rules for phone formatting are enforced.

Each storefront can support a single sales tax nexus. We support:

We have extended our sales tax system in the past to handle new customer requirements - for example, the US & Canada combined option above was developed expressly for a customer with offices in both countries.

Each storefront can support a single currency. Currencies supported currently include USD, AUD, Pounds Sterling, and Euros. Additional currencies can be added.

Regarding currency conversion:

Dates are also localized, both for time zone and format - based first on user preferences (the PageDNA admin), then site preferences (the PageDNA platform user).