 Cwm ydw i gweithio'r cwmno, yna'n gweld y cwestiynau i gyd.. ..yna'n ddod i gyflawni i gyd, roeddwn i'n gwybod... ..y'n meddwl i'r math. Yn nodi'r ffordd, yna yw Amazon Pay yn ddechrau... ..yna'r cyfrif y gallai beth yw'r bywysau'r bywysau... ..yna'r bywysau'r bywysau'r bywysau'r bywysau'r bywysau... ..yna'r bywysau'r bywysau'r bywysau'r bywysau... maen nhw'n gwiswch, yn cael ei bwysig o'r amlwg ar y Amazon, mae'r llwyddoedd, mae'n dechrau'r cyfrifiadau, mae'n rhaid i'n ddim yn gwneud sicrhau ar y Bwysig, byddai'r llwyddoedd yn gwneud. A rydych chi'n meddwl y bwysig ar y bwysig, mae'r llwyddoedd yn gweithio'r cyfrifiadau a'r cyfrifiadau yn ddysgol ar y bwysig a'r cyfrifiadau yn y caseoedd y byddai'r cyfrifiadau yn y bwysig a'r chwybr ar y bwysig. The next would be registration process on a website and forced account creation and 86% of the people that we surveyed essentially called that out as one of the key issues and frustrations they felt when shopping off Amazon. And then finally that it was just simply taking too long to complete purchase. Tied in with the forced account creation and the length of time, the amount of fields it would take to finalize that purchase. They've gone through the magical experience with wonderful content, great product imagery, really seamless user experiences online, and then suddenly they're confronted with this barrage of information fields that they need to fill out on sequential pages. Merchants cited some slightly different problems as you'd imagine on the other side of the equation. One was being increasingly responsible for fraud and risk management. Another was how to convert visitors onto their sites into new customers, prevent that person actually just browsing online but converting in store. It's weird, we often hear about the inverse of that being the case, but we found certain merchants were concerned that people actually would prefer to convert in store but browse online and not necessarily convert in their store. And then offering easy and frictionless checkout processes when there's still a requirement to gather enough information to ship the product to that buyer and to complete their purchase. So we basically generated what created Amazon Pay around providing trust, convenience and speed and simplicity to that final part of the online execution. I guess in terms of Amazon Pay at a glance then, our customer base really is this figure that you see there. I think there was a little laser on here somewhere. So the figure that you see there is what our customer base actually should be. It's 300 million plus Amazon customers worldwide. So far we've penetrated around 10% of those with Amazon Pay, so there's still a lot of work to be done, but that's been done through organic growth, through making Amazon Pay available on sites that are not Amazon and activating new buyers from there. However, there is nothing someone needs to do to become an Amazon Pay customer other than use Amazon Pay for the first time. If they have an Amazon account they can use Amazon Pay, it's as simple as that. Of the customers that have used Amazon Pay so far, 50% of them are Prime customers. We're known to transact more often and transact in greater average order value and spend more online. Over the last year we've seen that active merchant base grow by 120%, so that organic growth is starting to take off. The solution, which Matt and I will take you through in greater detail, but simply put in a nutshell is one account with your shipping addresses and your digital wallet access through one username and password, which is your Amazon username and password. It provides speedy and simple checkout, 90% conversion rate, well sorry, up to 90% conversion rate I should say, and checkouts that can be conducted in less than 30 seconds. It's seamless across mobile and desktop, and some parts that we often overlook here, but it also can provide a customer a greater sense of assurance through the A to Z guarantee being extended to those customers. We skip to the slides that run through it, and we can talk about this. Do you have the URL available on your computer? I don't remember, I'll tell you that in the demo, so maybe we could run through it on a live site. Yeah, but I just don't remember the URL on my computer. Sorry, we're just having a quick comp lab because there was a demonstration video on my laptop which we got transferred across, so apologies to the lack of the region here. So what we'll do is run through a live demonstration of what the user generally looks like on a site, and then Matt will do it. Do you have the URL available by chance? Do you know what I've got anywhere in the demo on my site? Because I just always have it. I can put it up quite easily. Nope, I don't want the email. I just know I'll be able to find it quick. A quarter of a video, so we won't have to do it live because nothing ever goes well when you have to do a demo live. So we'll go through it, and I'll just give a quick overview. So one of the interesting things about the Amazon Pay integration is it's not just a payment gateway, is it does involve the whole flow so that way you can get the greater conversion rates. How do you just make Safari work? Does it not let you accept a bad certificate? That's what I was going to do. So as I said, it takes over the entire flow, so it allows you to get those greater conversions because you're able to use the Amazon components inside your Drupal common site. That's why you said it needs to be dragged over. So we'll go ahead real quick, and we're going to buy a T-shirt or a hat. So it's right there. I'm going to add it to the cart. So when they come here, they can see the Amazon Pay. We'll go ahead and log in. So typically a site either allows a guest account, or more times they want you to log in so you can track your user account. And as Jim said, many times some people aren't necessarily comfortable doing so. So actually when we're logging in right now, it's using like a single sign-on approach. It provisions a Drupal account. So now they're actually logged into Drupal. You can see it says my account. So this is one of the great things about it, is when they actually authenticate with Amazon, it's a Drupal account that they can come back to and log in to via Amazon. Again, it garners that trust and lowers that, garners trust and lowers that barrier to gain more conversions. So one thing to notice is that the address book is actually replaced by an Amazon widget. So in Drupal Commerce 1, to get an address book, that's a module. Now using Amazon Pay, it's a widget rendered on their side, managed on their side. It's all tokens. You have an order reference token. And Amazon says, oh, here's a shipping address they picked for that order. So we'll go continue to the next step. And we're able to fetch that data and you can still use it with the shipping methods and the commerce shipping module. And then when we come to review, we have the same thing with the wallet. So reusable payment methods in Drupal Commerce 1, you have to have a card on file and your payment gateway module has to support card on file. With Amazon Pay, you get the address book or the wallet widget automatically to reuse different payment methods. And they can add them actually in site, I believe. You can add a payment from here. If there's invalid payment handling, let's say the card is declined, you can edit the information all from within here. They don't need to leave your site to change any information that might have been inside Amazon Pay. And then we'll go through and just pick a card. You continue the next step. And voila, it's all done. So just for real quick, I'm going to log in and just kind of show what that looks like. And that is one thing, too, is they could have it where, when there's login form, it does embed the login. You could actually turn off Drupal's registration and have your site solely be login with Amazon and Amazon Pay if you just want to kind of use Drupal Commerce to extend your already existing marketplace inside Amazon. As a footnote, this is for just Amazon Pay. It doesn't actually provide like Amazon catalog syncing that like merchant web services might do. This is just for Amazon Pay. And when I said it kind of takes over a lot of your workflow. So if I go into the settings here, so general settings, if the US site doesn't support the language code, but if you're in the German or the UK, you can actually pick different languages that are available to it so that way you can localize your experience for the payment settings. It allows asynchronous transactions as I thought was really cool. There's a lot of payment gateways that don't support asynchronous transactions very well. So how that works is that checkout flow we went through. Let's say the card was declined. We would still complete checkout because it may take 60 seconds or whatever your fraud detection may want to have. And on a decline, Amazon Pay will alert the site, pay the payment was declined, and it actually sends an email telling them like please visit pay.amazon.com with their localized URL, they update the payment method, and then it tries to reauthorize the order. So it has this robust workflow that's just part of a module or part of our integration, which there's no other payment gateway that does this. There's no other integration that has this kind of robust integration. And one thing we also have is order management. So you can automatically capture an authorization or capture on shipment. You fulfilled your order, you marked it complete. It'll capture it for you automatically. You don't need to go to another UI. So that's why I actually really like the Amazon Pay integration, especially in triple commerce one, is it has a lot of these things that you kind of expect, and it's all tied in. And then there's a few other things in here, but that's the general flow. You manage orders the same way you go to the payments tab, but it's more so that customer experience and some of those back end things that are powerful. That's the quick demo there. How do we get back to the presentation? Rob, did you want to go to the strings? Or how do we go? What's the next slide after that? So we did that one. So if you've done three of these, did you want to go to the... Yeah. We can go into the... How was... Do you want me to just go over how this is developed? So when we go through the integration of this part. So it was really interesting because it does take over a huge part of the triple commerce checkout. If anybody here is developed for triple commerce one, it's not... There's ways that you can customize the checkout, but it's not exactly easy. So it provided some really interesting challenges. It is powered using checkout pains, so you can still customize the checkout and configure it as you would like. It can work alongside your existing checkout flows. So we have a lot of people that have it integrated. They were able to take their existing sites and just implement it alongside of it. I'm hoping we have a good case study out of this company called Rift Tracks, who's a huge triple commerce user. They're a huge Uber cart user. And I believe next week they're going to put it in production on the Amazon page. So it'd be really great to have them show some of this conversion, how they implemented it with their highly custom site. Rift Tracks, they sell industry science theatre 3,000 style soundbites. And they have digital and physical products. And they said that Amazon Pay will help them, hopefully convert their existing Amazon customers. And this integration had a really big impact in triple commerce too. Because we were writing this as we were developing triple commerce too. And along the way I was like, wait, we need to make this architecture change to better support integrations like this. Over the past week, getting ready for Vienna, I worked on the triple commerce 2 port. And I actually have a demo that I'll be giving at our booth downstairs. That shows a multi-lingual, multi-domain, single platform site where you can go to the DE.AmazonPay version. And it's translated into German. It takes you to the German Amazon Pay merchant. Unless you go through the different flows and it recognizes the multi-store concepts in triple commerce too. So a lot of what we learned when developing Amazon Pay went into triple commerce too. And will help you get larger conversions in multiple regions. So I guess where I'd pick up from is a question of like, why is this important so what? It's great that you could have a payment solution like Amazon Pay but the real reason why this is important is up there really. It's the 69.23% cart abandonment rate. Now that's not a figure that we necessarily have produced that's from a report that we ran with a company called the Bay Mard Institute who are essentially UX specialists. They've done over 240,000 hours of UX research mostly with enterprise level customers but also small, medium businesses to mid market. And across 37 different studies that's the cart abandonment rate they saw. And the important thing here is it's not something that's fixed. Like it will not always be the case that we will see 69% abandonment rate in e-commerce. It's not something we just have to grin and bear and accept. There are certain key drivers, key reasons for that abandonment rate and these are some of the ones that they've pulled out. Now in terms of extra cost too high for shipping, website having errors and crashing or the delivery being too slow that's not something necessarily that Amazon Pay can help a merchant with but there are other Amazon businesses that may be able to do that such as FBA and AWS, I'm not here to talk about them today but ones that we can see being addressed and in some ways these are one better word low hanging fruit in terms of addressing checkout conversion that forced account creation for over a third of people that is a reason for a cart abandonment. Over a quarter of people abandon carts because the process is too long or too complicated. I travel every work today for my sins on the London Underground basically pressed up against the unwashed masses of London and as anyone that has ever gone through that can attest to a couple of things it's an unpleasant experience and in modern times everyone's on their phone. Often in areas that have signal about to make a purchase it's that sort of period in the day where people want to while away time doing some shopping and I see time and time again someone will be shopping on mobile they'll even have the product, they've got time to complete that checkout and they'll go underground and lose reception and the phone just goes back in the pocket. We set them up for the goal but it's just too hard to go through that process of a guest checkout or a new account creation on their mobile. The same is true of desktop although in a different situation. Trust is again a key driver and we'll also just touch upon that there weren't enough payment methods. So I guess first looking at the top two highlighted in red the process of forced account creation and the fact that it's too long and complicated checkout process. A couple of things I think to touch on here. One would be the sort of proliferation of forced account creation has seen an average in the UK at least of 19 user name and password combinations per user for their online shopping which is apparently beyond the cognitive reach of most of us it's certainly beyond my cognitive reach to remember those different combinations in which sites they apply to. And going back to the original slide for the customers that we've surveyed at Amazon that is a key source of frustration. So as Matt touched upon from here in the experience with Drupal commerce from the cart page can essentially skip through the checkout step and jump straight into checking out via Amazon Pay. Once the username and password have been entered and it's been authenticated with Amazon the merchant will receive that name of the customer and their email. So two fields of information but the crucial parts for a new account. The merchant gem.com wishes to do with that information later is up to them. It's your customer and if you need certain things like the customer's age or gender or phone number for other parts of the account creation that can be done sequentially but the important thing is the account can be created there and then. Even if that person decides I'm going to enter my username and password and the far alarm goes off and they don't complete the next step which is to select their shipping and payment information that username sorry that name and email address will still be passed new customer acquired. Then and this is an example of a one page template it can be done sequentially but every shipping address and every card or payment detail that person's ever entered into Amazon that's eligible on this site and for that purchase will render. So if Amex is suppressed, Amex will be grayed out. If that person has entered a shipping address in the like I don't know, Ruratura islands in the Cook Islands and that's not placed that merchant ships to that will be suppressed but we're getting past here the point where that customer has been forced to enter into more informational fields to complete their checkout. That's important because the average amount of fields that a merchant, sorry a buyer is forced to enter are 14.8 fields at the moment of information just to complete their purchase. Here they enter typing in the username and password and then the information is already stored just to be selected with one tap. What does this translate to? It translates to a faster checkout experience. So on the left there we've got the average checkout time and that's from goods in the basket ready to checkout via either a guest checkout via the hosted checkout or via an alternative payment solution that's the industry average for all. With Amazon Pay we're looking at an average checkout time of 29 seconds. Now it probably comes no surprise to you all but this is kind of a strong correlation. Purchase completion rate to time is positively correlated. I don't know if anyone's ever heard of the golden hour and sorry if this is a bit of a strange analogy. The golden hour is a term that's used for like first responders so in a previous life I used to be in the military and we'd get drummed into us the golden hour so if someone becomes a casualty that golden hour is when you get them into a place where they can get basically beyond first aid and the faster you get them into that period within the golden hour the greater the chances of survival. Now this is a very dramatic analogy for checkout so I apologise if it goes a step too far but I always think it kind of applies here. We don't know what the golden period of time is. Is it a golden minute? Is it a golden 30 seconds? And to be honest that golden period of time is getting for ever and ever restricted as basically buyer expectations go up. But what we do know is that the greater the speed and the greater the simplicity of the experience the greater the chance of that purchase completion rate going up and this is not like what we want our end solution to look like we would like that time to be reduced the steps to be reduced and part of that will be in terms of looking at new ways to identify the customer and also reduce those steps to completion. Are there any questions at this point by the way? And so looking back again here I think we've looked at forced account creation and how Amazon Pay can assist with I guess negating the need for forced account creation and also speed and simplicity of checkout looking at trust then and I'll touch very briefly on the there weren't enough payment options. So trust is at the heart of the Amazon that's supposed to say Amazon model it's not just a pigeon English but trust is at the heart of the solution and that's come from trying to consistently deliver on customer expectations over a number of years but it hasn't come easily and that's been a hard fought battle from selling books out of a garage in Seattle in 1994 through to the current position of Amazon I think last year it was Forbes' most trusted brand. And what we've seen from certain research is with the user engagement company SDL is that it takes around two years of continuous engagement with a brand to feel that strong sense of trust and then five years of continuous engagement until that starts to translate into actual uptick in the average order value. So how does that information help anyone who's starting out in their own business for the first time because it's very difficult to earn that trust? Well, and sorry to take a step back we also see that for 78% of people they consider trust extremely or very important in where they choose to shop from payments.com So what we're looking to try and achieve with Amazon Pay is essentially taking the trust that's been built up in Amazon over a period of over 20 years now 25 years almost and implant that onto a person's site for the first time. I missed the show of hands earlier but who kind of develops e-commerce sites or is an e-commerce merchant in the room? And I take it for you all then it's nothing new to put some trust symbols onto a site. So Commodo or even an SSL certificate or Norton Antivirus we want to position Amazon Pay as that sort of trust symbol certainly in the checkout site. We find that users tend to react more with gut than with logic and sometimes we can see a bit of a confirmation bias within the industry for both Amazon Pay but also with merchants, with developers. We know that your sites are secure we know that some of the solutions you're using to make that site very secure are best in class. The average buyer transacting online doesn't know this and they don't have the same level of technical sophistication but they know what they like and they know what they're familiar with and they know what they trust and that can come down to certain I guess like almost intangible things but like the look and feel of a site and how trustworthy does it feel. You see certain sites where every part of the payment information and the address is just in the same field. It looks all the same even though the actual value of that information and the level of security that would need to be provided to that information is vastly different. My middle name looks exactly the same when I have to fill that out as does the county I live in as my actual credit card number and the expiry date on that card. Sites that present that information in a slightly different field that is trivial as it sounds but is maybe bordered by a different colour can give people a feeling that that site has is treating that data in a different way that would be more secure. We want to extend Amazon Pay as a trust symbol onto people's sites to increase that level of trust that they feel engaging with that brand for the first time. That's a part of the value proposition for small to medium sized businesses and we've seen good results with that. A couple of quotes up there from Sue Taggart, the digital marketing manager who is so can sleep a UK merchant dealing in very luxurious bathroom products but she noted that Amazon is synonymous with shopping online and that basically seeing that Amazon logo immediately creates that feeling of trust in the site that resonates with brands and I don't know if anyone has ever encountered seed-lip drinks but they are kind of a UK start-up in going for a couple of years now selling non-alcoholic gin which sounds strange and anoxymoron but it's actually quite delicious if you ever have a designated driver and you just want an adult drink for the night but when their site started even though the brand itself now features in many restaurants I think it's partnered with the top 100 Michelin starred restaurants in the world now to provide seed-lip drinks to them but actually to the average buyer online it's a new brand and they saw that basically having that trusted source that people already know was helping them to drive new customer acquisition and an increase in sales and so just going back one step as well the final point that there weren't enough payment methods now this can be slightly misleading and I think this should be caveasted if you're selling something that can only be found on that site and is the best in class in the world and is unique to your site and your product line then a buyer will pretty much crawl over broken glass to purchase that no matter how many metaphorical barriers are put in their place they will find a way to complete that checkout and purchase that product in reality there's always another option online there's always someone else selling something similar if not the same product in their own shop and being best in class in terms of providing a convenient user experience for the merchant while they're on your site is a key point to to making sure they convert while on your site now in terms of not offering enough payment options what this study by Baymard kind of threw out was that there's a real particular subset of customers who prefer to see certain third party so to speak or alternative payment solutions such as Amazon Pay such as PayPal or Apple Pay or Android Pay and these are international buyers now certainly where I'm working at the moment in the UK internationalisation is a big focus given a backdrop of political uncertainty and certainly people want to make sure that their brands are able to trade and sell across international boundaries and I expect that's the same for merchants within the US within the rest of Europe as well and the subset of buyers to whom there not been enough payment methods available really counts is international buyers so people buying off their home nations site it's again touching upon that trust symbol of seeing a sort of internationally recognised brand on a site and there's a greater part to this in terms of the convenience of that purchaser if I'm purchasing something from a site that I've not engaged with before I really want it I'm trying to think of an example now I want to get this beautiful jacket that I've seen from Italy now my foreign language skills are dire at best and they're not going to be necessarily improved by having to go through a process of going through a returns policy or refunds policy in a different language so we're having international payment methods that can be localised in multi language really addresses a buyer pain point is for those buyers buying internationally we want that trust symbol but they also want the convenience of if something goes wrong I know I can deal with that payment method not necessarily the merchant themselves so if I'm buying this Italian jacket and I know I can purchase with Amazon Pay I know if the goods don't arrive in time if they don't arrive in the condition they were described to I will be able to get my money back and that payment solution will act as that middle man with the merchant rather than me having to go to someone who is in a different location to myself different country potentially different regulations around returns policies and certainly a potential language barrier there any questions? so one final thing that I think can be overlooked sometimes because we focus on biotrust but it's also at the heart of the solution we've tried to make sure it's trustworthy for merchants as a customer as well our sort of account management team will often complain that one of the headwinds can face is such as the retailers will have sometimes mixed feelings towards Amazon and that by having Amazon Pay on their site there would be a concern that this is I guess some form of digital Trojan horse that's there to harvest data from their site to feed it back into Amazon and run everyone out of business so that feeling of mistrust would not I think be negated by me just saying that's not the case but what we've done is basically coded it into our solution so the information that will be passed to Amazon or Amazon Pay is simply the order value well and also the time of the execution but no product line information is passed so what's actually been sold we don't know obviously unless it's a single product site and then that would be fairly obvious but we don't have an interest necessarily in finding out that product information we just want to facilitate the buyer and the merchant making that transaction instead what the customer receives as in the merchant will be the customer name email address, the telephone number shipping address, billing address payment confirmation these are the main lines of information there's I think another 17 16 and 17 information fields that can be passed as part of the product now that's basically coded in within the solution it's also within our terms as well so we don't share data and I guess the final thing that I'd say on this is it would also be business suicide for Amazon to an Amazon Pay to act in that way over 60% of Amazon's revenues now come from outside of retail the majority of which come from services so if one subset of Amazon started croding that trust in Amazon as an overall organisation that would be the equivalent of just taking a shotgun to your own foot and pressing the trigger and 40% of all e-commerce is in some ways traced back now to AWS as well so if we were to do that there would probably be a more a more efficient way of doing it by AWS but that's not the case in like many hundreds thousands brands and companies already trust AWS so I'll just turn now to a couple of case studies and then we'll see open up for questions or Matt if you have anything more to say for the order when we create the order reference what happens in that checkout is the widgets then say here's your ID this is the ID you can talk to Amazon with to know merchant information which in the UK you get you get billion right away or after payment and then in the US you don't get any but all you pass is the order value and currency and then when it was created the store it was for so like in Drupal commerce 2 you can actually send that different store like the name of the store but that's it there is no line item data there's no how much in tax whatever percent of shipping charges taxes, promotions whatever it's not known like we just send that flat amount so that is one thing that's nice too because we don't have to calculate all that and replicate all that data and pass it along so thanks very much so yeah a couple of case studies now the first one seeded it who I mentioned earlier and as I mentioned it's a bit unferty that may start up there becoming quite well established a small growing business and the key things really that we look to help them here with was the element of trust online and also new customer acquisition and the figures here are for within six months of going live with Amazon Pay we saw starts with the 30% of increase in conversion and that's an increase in conversion versus their native checkout the only alternative payment option they have is Amazon Pay so it rates well in terms of conversion versus their native checkout and it quickly assumed 50% cart share as well and what we believe the reason for that is because it was a relatively nascent business in a small business so the cart share naturally would go to a solution or a payment option that people were more familiar with or a site that they were unfamiliar with the reduction in checkout time was 60% and again that's correlated in many ways to the increase in conversion and one thing that I really like about this and it's worth touching upon now in light of the Drupal commerce integration is it took them 15 minutes to implement so with Drupal commerce we will hopefully very soon be bundled into the commerce kickstart which will not correct me if I'm wrong it will eliminate a lot of friction in terms of implementation and I certainly think the solution in terms of a plugin solution to Drupal commerce that Matt has designed takes a lot of the friction out of implementation To get set up in Drupal commerce one for Drupal 7 you download the module and we hook into the library's module and you download the SDK so that takes some time because there's no way to automate that process really let's say that's 10 minutes you install it and you plug in your merchant details it'll probably take more time to copy over your details from your seller essential account into the Drupal commerce store but you do that and you're done in Drupal 8 it's even easier because of Composer you literally could start with a blank Drupal site when Composer required Drupal slash the module name and it will download the module the SDK and commerce itself and in 10 minutes you'll have your whole site ready so it is one that you don't have to manually implement it the module does, you just plug in your information and go thank you and then a case study from All Saints what we consider like an enterprise level brand with an international footprint so the trust element for All Saints maybe was less important there very well established certainly in the UK, the US both their online shopping experience and their checkout was already pretty well optimized but what we saw was really through providing that speed and convenience of checkout some pretty compelling results so again there was a 34% increase in conversion this time for a 24% cart share and as I mentioned the sort of fact that the site was already well established we believe kind of provides slightly a glass ceiling in terms of potential cart share but as there were already customers set up with accounts on All Saints who would be happy to continue transacting with those it did see a 15% higher average order value however so customers that were checking out with Amazon Pay were going to spend 15% more on average than those using the native checkout now there's a number of different drivers for this one is potentially because of the sort of disproportionate amount of Amazon Pay users or also Prime users so Prime users tend to be more affluent than average and as I mentioned earlier more frequent purchases online and when they purchase online they also tend to spend more online and also the fact that if it's a quick and convenient checkout and you know that's going to be the case you can free up more time for your shopping and purchases and browsing which can lead to more items going into the cart itself and then a 70% reduced checkout time from what was already a fairly well optimized checkout for All Saints so thank you very much for bearing with us while we had a few technical issues at the start of the presentation this has given me exactly the case I need to go back to work with to get them to give me a Mac book rather than this antiquated laptop very happy to take questions now just a sort of final I guess note for myself like as Amazon Pay we're not newcomers to e-commerce by any stretch of the imagination but we are getting to know Drupal and the Drupal community and Drupal commerce more so very happy to speak to you I'll be on the booth for the rest of the week co-located with commerce guys and be great to understand more about sort of businesses that you're involved in at the moment what customer pain points you're looking to solve and you know looking at how we can work together in the future as well but please any questions I don't have a few things I can add so at the booth we will be doing a demo I have it set up I have a local environment so I don't have to worry about the wifi crashing well I can't talk to Amazon if the wifi crashes but it's a Drupal commerce two site that has multiple stores in it and it's one domain one site in the current domain you're on controls the active store and translation which relates to a specific seller account so let's say that you do you have a you're based in the UK but you also have a German store so you have a German merchant account you go to the website without a domain prefix and it seems this is the main site that this is the UK store uses the UK seller central when they get to the German site it will be in the German translation and it will be localized and have your German Amazon pay account set up with also that localization so that's the demo I have to kind of go through it so we can show off these new features in Drupal commerce two and also how the Amazon pay integration works where it shows it's one account it's still the one account inside Drupal but they sign up from the different channels so one interesting thing you brought up when somebody logs in and they didn't convert you have their information so you can send them an email and say hey why don't you know did we make you upset you didn't finish your order like what could we do for you which is crucial a lot of time with cart abandonment there is no way to reach out to them so that is a huge step and one thing that we're really looking to do in the next with this new version of Drupal commerce two is be more opinionated and give best advice in e-commerce which I really think our partnership with Amazon pay is doing that because with building this integration we're also learning and we're also able to take those best practices and build them into this platform as well and deepen our integration with Amazon pay so it's a really good mutual relationship in that effect thank you