<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Valérian Beaudoin on Medium]]></title>
        <description><![CDATA[Stories by Valérian Beaudoin on Medium]]></description>
        <link>https://medium.com/@valouille?source=rss-c10aa98ffebf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*p-0bX3A5uxT9VGTdIxboSQ.jpeg</url>
            <title>Stories by Valérian Beaudoin on Medium</title>
            <link>https://medium.com/@valouille?source=rss-c10aa98ffebf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:37:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@valouille/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Japan (re)launch]]></title>
            <link>https://engineering.backmarket.com/japan-re-launch-a503cc6d6a04?source=rss-c10aa98ffebf------2</link>
            <guid isPermaLink="false">https://medium.com/p/a503cc6d6a04</guid>
            <category><![CDATA[japan]]></category>
            <category><![CDATA[refurbished]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Valérian Beaudoin]]></dc:creator>
            <pubDate>Wed, 24 May 2023 06:21:47 GMT</pubDate>
            <atom:updated>2023-05-24T06:21:47.086Z</atom:updated>
            <content:encoded><![CDATA[<h4>From Back Market to バックマーケット</h4><p>By the time of Japan launch in 2021, <a href="https://www.backmarket.co.jp/">Back Market website</a> was already available in 14 European countries as well as in the US. All countries have their own specificities reflected in our code base. However, we had to adapt our product even further for Japanese market, which is different from European markets in many ways. Let’s see how we did.</p><figure><a href="https://www.backmarket.co.jp/ja-jp"><img alt="" src="https://cdn-images-1.medium.com/max/677/1*gNO32IXaAjm-Ea_R2jjLTg.png" /></a></figure><h3>&quot;Proof of Concept&quot; mode</h3><p>We didn’t go through the whole development process right away. Instead, we decided to have an unassuming approach to get a better idea of which features and changes were necessary. To make sure to do the right things and avoid unnecessary trials and errors, we teamed up with a local Japanese web development company called <a href="https://www.re-fine.jp/">Refine</a>. We launched the first version of our website together with them, using a completely separate codebase. Doing so, we learned a lot about e-commerce in Japan, building trust with our Japanese customers and partnering with local sellers to sell our first <a href="https://www.backmarket.co.jp/ja-jp/about-us">refurbished devices</a>.</p><figure><img alt="The first version of Back Market website in Japan" src="https://cdn-images-1.medium.com/max/1024/1*x-VI4fCg-izEs6LsSfvsbQ.png" /><figcaption>The first version of Back Market website in Japan in 2021.</figcaption></figure><h3>(Re)launch and features</h3><p>After more than a year of successfully running our marketplace with this first version, we grew enough knowledge about e-commerce expectations in Japan. We were starting to have more and more sales, and decided that to continue Back Market expansion in Japan, we needed to migrate to our main codebase. By doing so, we aimed to take full advantage from the expertise Back Market built when scaling other countries.</p><p>Using the gathered experience and learnings from our first Japanese website, product and business teams listed all the mandatory adaptations to our codebase. Then, tech teams re-implemented these features internally before the migration. Here are the major ones:</p><ul><li><strong>Translation and Japanese language support.</strong> The first thing that comes to mind for launching a website in Japan is to translate it and support Japanese characters. Because we were already an international company, we leveraged our Translation team to provide accurate translation matching our tone of voice but also met Japanese customers&#39; expectations. The Design System team implemented a Japanese font on our website and ensured it displayed well everywhere.</li><li><strong>Konbini (convenience store) payments</strong>. Instead of paying over the Internet using a credit card, the customer is given a number, that is used to pay in a physical store using cash. This method is really popular in Japan, and represents approximately 40% of orders, so this was a must-have for the relaunch.</li><li><strong>JCB credit card support</strong>. In addition to Visa, Mastercard, and American Express, a Japanese card brand is very popular here: the JCB card.</li><li><strong>Furigana.</strong> Japanese names are written using <a href="https://en.wikipedia.org/wiki/Kanji">the Kanji system</a>, and some can be rare and, therefore, hard to guess how to pronounce, or have multiple possible pronunciations. That&#39;s why on a vast majority of Japanese websites, customers are required to enter two times their first name and last name; the first time as Kanji, and the second time as <a href="https://en.wikipedia.org/wiki/Furigana">Furigana</a> (using <a href="https://en.wikipedia.org/wiki/Hiragana">Hiragana</a> or <a href="https://en.wikipedia.org/wiki/Katakana">Katakana</a> syllabary)<strong>.</strong></li><li><strong>Japanese addresses.</strong> A Japanese address is usually written in the following order: postal symbol, postal code, prefecture name, then city, town, village or city ward, subarea, subarea number, block number, house/building name and apartment number.</li><li><strong>Japan logistics.</strong> Add support of parcel tracking integration from local logistics companies Yamato Transport, Sagawa Express, and Japan Post.</li></ul><h3>Ways of working</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vNCf9MwoxXfYesjrYDaM7A.png" /></figure><p>To lead this project, we launched a dedicated tech team, with members both in our newly opened Tokyo offices and in our Paris headquarters.</p><p>By doing so, we were able to work closely with product and business teams in Japan and fully understand the ins and outs. At the same time, having an engineer working from Paris in the same timezone as most of development squads, enhanced dramatically the communication.</p><p>Japan tech team collaborated with all the product &amp; platform squads that were impacted by the Japan relaunch. Given the list of changes and features required, it meant almost all development squads of Back Market 😄</p><p>Depending on the topics, this team had 3 ways of working:</p><ul><li>Doing the development by themselves, and asking squads for review.</li><li>Writing technical specifications and asking the squad(s) owning the scope(s) to do the implementation.</li><li>Fully relying on a squad to develop a feature.</li></ul><p>Since we had to work a lot asynchronously, we made sure to leverage the collaborative tools we use at Back Market the best way we can. We centralized as many discussions as possible in a <strong>public</strong> Slack channel, kept track of all discussions in Confluence meeting notes, used asynchronous development patterns, etc.</p><p>We only needed to keep two kinds of regular synchronous meetings between Tokyo and Paris:</p><ul><li><strong>Daily</strong> meetings between Tokyo team members and Paris members to do pair programming, do the baton pass on current developments, align on communication, etc.</li><li><strong>Weekly</strong> meetings with a few designated persons for sharing the progress of the squads, and raising blockers to make sure to meet with the anticipated relaunch date.</li></ul><p>Daily stand-ups were made asynchronously using the <a href="https://geekbot.com/">Geekbot</a> Slack app.</p><h3>What was anticipated</h3><h4>Yen Support</h4><p>The first major project for us was to add support to the Japanese Yen (¥) currency. Indeed, it differs from other currencies we already supported because <strong>there are no cents in this currency</strong>, therefore no decimals. We wrote <a href="https://engineering.backmarket.com/ca216dc013b8">a complete post</a> about how we dealt with it in our Python codebase, if you want to know more about the technical details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/1*CIIs9vteXhUsJQNIhhisVQ.png" /><figcaption>Price displayed in ¥ on the product page.</figcaption></figure><p>Other minor changes include a comma every 3 digits, the fact that we need to add ¥ symbol before the price, and 税込 indication to specify that the displayed price includes taxes. We also needed to do various adaptations on the front-end due to the fact that prices in ¥ are generally longer than in European currencies.</p><h4>Konbini payments</h4><p>Before even implementing the Konbini payments, we had to redesign a significant part of our payment workflow, because it was our first asynchronous payment method. Before Japan, we always proceeded the payments right away, but we had to completely rethink the way we did stock management and payment statuses transitions with all the squads owning parts of the workflow.</p><p>Once we implemented this requirement, we could proceed with the Konbini payment implementation per se:</p><ul><li>Creation of the form and confirmation message providing the required information for latter payment</li><li>Integration with our Payment Service Provider</li><li>Email reminders and payment expiration process</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qxNpYbt3PsPdGWCZ-huoYg.png" /><figcaption>The first successful Konbini test payment receipt.</figcaption></figure><h4>Data migration</h4><p>We decided to migrate some customer data from our previous website to the new one to allow customers to still connect to our website and access their order details. From there, they were still able to ask for support if required as part of the warranty that comes with every product bought on our website.</p><p>The two systems being very different, we could not simply import orders data in our new website; therefore we built an ETL-like (Export Transport Load) script to incrementally import data. This way, we imported customer information multiple times prior to the relaunch to make sure the script worked as expected, reducing the risk and execution time during the migration.</p><p>We also imported orders data in a dedicated table in the database not to mix them with new orders, and decided to display them on a specific page. Then, we ran the ETL daily even after the migration to make sure statuses of the orders made on the previous website were reflected in the new one. Indeed, orders made on the last few days of the previous website have been shipped by sellers using the previous Back Office even after the relaunch.</p><p>We decided not to import passwords for security reasons, so we asked customers with an account on the previous website to reset their password upon first connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OuLfrpsG5Juk2Z41gAlrSQ.png" /><figcaption>Display of an order made using the previous website in the new one.</figcaption></figure><h4>Names &amp; Address Management</h4><p>We had to make many adaptations to support Japanese addresses. First, always ask for <em>last name</em> <strong>first</strong>, and <em>first name</em> <strong>last</strong>. In Japan, we usually call our customers by their last name, adding 様 (さま・sama) suffix. This change was required in many parts of the website, including emails, profile display, etc. It’s considered rude to call people by their first name in Japan, so we were extra careful to change it everywhere.</p><p>We added two extra fields for <a href="https://en.wikipedia.org/wiki/Furigana">Furigana</a>. It’s important to note that usually it’s displayed like on the screenshot below, in a 2x2 grid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*0dUXxDAEiYN1u5dO1TMuOQ.png" /><figcaption>Our updated address form for Japan.</figcaption></figure><p>In Japan, almost all websites ask for the post code first, and auto-complete the prefecture name and city name, so that’s what we did. Something interesting enough is that the list of prefectures in the list is displayed from North to South, not in pseudo-alphabetic order.</p><h4>Grade names</h4><p>Instead of using Excellent/Good/Fair translations for the quality picker, we decided to go with A/B/C grade names which are already used widely in Japan for second-hand items. A-grade means excellent state, while C-grade means some aesthetic defaults such as scratches are expected on the product, despite the fact that they are always 100% functional.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*rzFXfEnASryOgZziqmimUw.png" /><figcaption>A/B/C grade picker in Japan.</figcaption></figure><h3>What was *not* anticipated</h3><h4>Japanese names can be a single character</h4><p>This was one of the unanticipated issues we had to overcome before opening the website to the public. Japanese names are written using Kanji and therefore contain few characters; some names even use a single character. It impacted some rules we had on our websites that we had to change to prevent displaying the personal information of our customers, for example in the reviews.</p><p>The usual rule was to display the first name and the first character of the last name of the customer writing the review on the product pages. For example: John D. But with Japanese names, it would have displayed the full name in some cases, so we decided to display the anonymized textレビュー投稿者 (reviewer/persons who wrote a review) instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*LGe2MB_khvBvAS9kH3jggQ.png" /><figcaption>How things would have ended if we had keep the same logic for comments.</figcaption></figure><h4>Support of double-width numbers</h4><p>When typing with the Japanese keyboard, the numbers entered are usually <em>zenkaku</em> (全角・ぜんかく), or double-width characters.</p><ul><li>single-width characters: 0123456789</li><li>double-width characters:０１２３４５６７８９</li></ul><p>In order to support these characters in address forms, we had to update our regular expressions, because we only allowed [0–9] and not [０-９] as well.</p><h4>Japanese auto-complete keyboard</h4><p>Japanese keyboard on all modern Operating Systems uses an auto-complete drop-down list to convert text inputed in Hiragana into Kanji.</p><p>For example, while using the Japanese keyboard and entering the characters for Tokyo, とうきょう, it’s automatically converted to the matching Kanji 東京. But this didn’t work as expected on some input fields as you can see below. 🤯</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*WPVb5bn5YboTirxr.gif" /><figcaption>The bug we had with Japanese keyboard.</figcaption></figure><p>How it’s expected to work, with the double-width characters changed to single-width ones, and making sure we add the hyphens if missing:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*YGlpLLBxpgxnDBPI.gif" /><figcaption>The fixed version at the time of the release.</figcaption></figure><h4>Transliteration of Japanese characters</h4><p>Japanese Kanji are actually originally Chinese characters, and while the two writing systems evolved in their own way, many characters are still written the same way in both languages. Our transliteration (conversion of non-Latin characters to Latin ones) library in Python was actually assuming that Kanji were Chinese characters, and displaying Chinese transliteration instead of the Japanese one.</p><p>We had to use a dedicated library called <a href="https://github.com/polm/cutlet">cutlet</a> to fix this issue and display the right transliterations in the URIs of our website.</p><p>For example, for the product “<em>iPhone 12 SIMフリー 128GB — ブルー</em>”, we generate a page with the URL “<em>iphone-12-sim-free-128-gb-blue</em>”.</p><h3>纏め (matome)・Conclusion</h3><p>Our first website allowed us to learn a lot about the Japanese market, and building it collaboratively with a local company prevented us from making many wrong assumptions. We were able to iterate a lot on it and run trials and errors quickly without impacting other websites, and refine a great version of our marketplace with the right features for Japan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7HzyiuWJ2Vetw5oCCIreuw.png" /><figcaption>The original website just before the migration.</figcaption></figure><p>Using this experience, and thanks to the dedication of Back Market teams, we reimplemented exactly what was required, and we were able to do it pretty seamlessly. Our customers could continue using the website the same way they were used to, and we didn’t notice any sales slowdown.</p><p>Testing the features <strong>as a Japanese customer</strong> was also key to identify issues we would have missed otherwise, such as issues with keyboards, names, phone numbers and addresses, etc. For that, having a local team in Tokyo has been a major contribution to the relaunch success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MjCjQzPeNua7XzY9j0f2iw.png" /><figcaption>The new website just after the migration. Can you tell the difference?</figcaption></figure><p>Let’s have a look at our b̵r̵a̵n̵d̵ ̵n̵e̵w̵ refurbished website at <a href="https://backmarket.co.jp/">https://backmarket.co.jp</a> and contribute to a greener tech!</p><p><a href="https://backmarket.co.jp/">バックマーケット | 整備済スマホ・タブレット・中古再生品・リファービッシュ品専門マーケットプレイス</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a503cc6d6a04" width="1" height="1" alt=""><hr><p><a href="https://engineering.backmarket.com/japan-re-launch-a503cc6d6a04">Japan (re)launch</a> was originally published in <a href="https://engineering.backmarket.com/">Back Market Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>