Poor support for Japanese at Plimus: worse than I imagined

28/07/08 6:01 PM

I already blogged about poor support for Japanese at Plimus here and here. By the lame form email they sent me each time I reported a bug with Japanese, I knew that they had no interest in supporting it.

That’s why when a customer pointed out the fatal bug in their Japanese page, I jumped ship and went to Avangate.

Plimus provides a Japanese-localized order form, but it turns out you can’t enter Japanese text in the name field!

EPIC fail by Plimus

In this form, I’ve entered a common Japanese name under “customer information” — Taro Suzuki — and the red error message is telling me I’ve made invalid input. The only way to complete the form is to write the name using the Roman alphabet — it won’t accept Japanese characters on the Japanese page.

Plimus masks this critical bug from vendors. It has a feature to “test drive” purchase pages, and allows you to enter Japanese text there with no errors. What I later realized, however, was that behind the scenes Plimus changes any name you enter on the test page to “John Doe.” I’ll assume this wasn’t intentional on Plimus’ part — they just seem completely clueless about handling Japanese, and show no desire to learn.

Luckily, a customer emailed me and told me she was having problems entering Japanese text on the purchase form. No telling how many customers simply gave up when faced with this bug, but my logs do show a number of people located in Japan navigating to the Japanese purchase page, but not completing the form.

Here’s a summary of the bugs I’ve found in Japanese support at Plimus, and which made me drop them as a payment provider:

  • Can’t enter Japanese text on Japanese page
  • Can’t customize purchase page with Japanese text
  • Yen prices shown to two decimal places

If you’re selling to Japanese customers, I recommend not using Plimus. I switched to Avangate, which has flawless support for Japanese.

From my research of resellers, Avangate is probably the only solution for selling to Japanese customers apart from rolling your own shopping cart with a merchant account, or using something like PayPal. As a one-man shop, I have only limited time to dedicate to Felix. I’d rather spend that time improving Felix than dealing with payment providers, which doesn’t help my users. That’s why it’s too bad that Plimus couldn’t meet my needs.

Posted by Ryan Ginstrom | in e-commerce | 2 Comments »

2 Comments on “Poor support for Japanese at Plimus: worse than I imagined”

  1. Turk Amon Says:

    Hi Ryan, I’m using Plimus an an e-commerce provider and find them very good. You scared me with your blog here so I went ahead and called Plimus Vendor support for clarifications.

    Here’s what I got for your 3 issues:

    1. Can’t enter Japanese text on Japanese page
    This is a restriction they’ve put to make sure all forms are readable by the Vendors. They will probably change that to a configuration switch.

    2. Can’t customize purchase page with Japanese text
    You can. I tried it. works nicely.

    3. Yen prices shown to two decimal places
    That’s not true. All Yen prices have 00 after the decimal point.

    So I’ll be sticking with Plimus for now. Not many Japanese shoppers for my software anyway 🙂

    Cheers
    Turk

  2. Ryan Ginstrom Says:

    @Turk Amon

    Thanks for the comment.

    Sorry, but the inability to enter Japanese on a Japanese purchase page is a huge bug. There’s no excuse for it.

    “2. Can’t customize purchase page with Japanese text
    You can. I tried it. works nicely.”

    They have a Japanese-localized order form, but you can’t add any of your own text (e.g. to give the purchase page the same look and feel as the rest of your site; navigation and such).

    “3. Yen prices shown to two decimal places
    That’s not true. All Yen prices have 00 after the decimal point.”

    You do realize that this is a bug, right?

Leave a Reply

  • Search

  • Categories

  • Calendar

    July 2008
    M T W T F S S
    « Jun   Aug »
     123456
    78910111213
    14151617181920
    21222324252627
    28293031  
  • Pages

  • Meta