It's a pretty insane thought right? For years we've been somewhat restricted with Magento Checkout on Luma. For the last 9 months we've been removing those shackles to realise the true power of Hyvä Checkout.

Just how slick and easy is it? Sean and Arron set off on their transatlantic flight to New York and instead of 7 hours of alcohol and in-flight entertainment, we set out to find out if we could demonstrate how easy it really was to implement Hyvä Checkout from start to finish!

One key point to make here is, this is not widely common to complete a Checkout build in less than 1 working day. In fact some may consider this reckless. What we would like to make clear though is that there are a growing number of merchants using Magento in a leaner sense, with greater reservation on customisation.

Fewer commercial extensions means much faster ability to react when compelling opportunities present themselves. Hyvâ Checkout is one such solution and we have carefully steered our merchants torwards the solutions and vendors whom are placing investment to supporting technology like Hyvä. mollie is one such vendor providing compatibility for Hyvä and Hyvä Checkout ahead of many other payment providers and thus, allowed merchants to adopt the techology for a greater competitive edge.

Key contributors to the fast time-frame

  • mollie compatibility
  • Inhouse MSI & Instore Collect
  • Postcode Lookup service worked out of the box
  • Amasty Shipping Rates worked
  • Minor UX work required

Plctured Left: Photo of 1st manual QA run approximately 4 hours into the flight.

What did we achieve in-flight?

  1. Purchased the Hyvä Checkout license 
  2. Created a Development Instance using MDOQ
  3. Installed Composer Keys & Modules
  4. Installed and configured existing compat modules for mollie and MSI / Instore Collect
  5. Installed our standardised Hyvä Checkout Base Theme
  6. Implemented simple client-specific UX styling
  7. Committed all to source control
  8. Ran Automated Regression (pre-prepared library of Hyvä Checkout Selenium Tests)
  9. Ran Build & Tag process on MDOQ
  10. Deployed to production