InteractOne is excited to be attending Magento Imagine Commerce 2016! Magento started the Magento Imagine conference with the goal of bringing together the entire community to celebrate, learn and inspire one another. Magento enthusiasts, merchants, agencies and technology providers from around the world come together in one place to celebrate Magento. What could be more Magento magical than that?
What we are looking forward to this year at Magento Imagine 2016
There’s the keynote speaker Magic Johnson to start. We look forward to hearing how Johnson’s business approach took him from a star on the basketball court to a star in business with his multi-million dollar company, Magic Johnson Enterprises.
We also look forward to hearing what’s new from the big guys at Magento like Mark Lavelle and Steve Yankovich. There’s always a new announcement that keeps everyone talking. Wonder what they’ve got in store for us this year?
Without a doubt, what we look forward to most is meeting with YOU! With so many new changes happening in Magento, a lot of merchants are wondering how this will affect their business. Magento 2 is live and real; should you consider upgrading? If so, when? Do you have questions and need answers? We’re hearing a lot of good questions from the community:
We’re running on M1, should we upgrade to M2 now?
How do we get our site ready to migrate to M2?
What are the differences between Community M2 and Enterprise M2?
How do I save my SEO rankings with this change?
How do I improve conversion with M2?
We would love to meet up with you to answer your questions and listen to your ideas. Our CEO Brian Dwyer, and our Magento Solutions Advocate, Dustin Clark will be rubbing elbows with our friends at Zerolag at booth 413. Stop by to learn more about one of our favorite hosting partners and to meet with Brian or Dustin with your M2 questions.
If you’re interested in setting up a one-on-one meeting, please email [email protected] or [email protected]. Brian and Dustin are happy to schedule a quick meet up anywhere, a hallway, the pool, how about one of the many food and beverage stations? You name it, we’ll be there.
Look for Dustin, we don’t think you’ll be able to miss him.
Oh, btw, the Orange Report. Do you get it? Sign up here for our monthly Magento newsletter to receive the latest and greatest in the Magento world.
We look forward to seeing you at Magento Imagine Commerce 2016!
Contact Information:
InteractOne, Inc.
513.469.7042 [email protected]
InteractOne Launches New Magento Site for Watson’s
Cincinnati, OH – InteractOne, Magento Solutions Partner, recently redesigned and launched www.watsons.com, a responsive-designed Magento website devoted to indoor & outdoor entertainment products for the home on February 16, 2016.
Watsons.com features all the products customers enjoy in the popular brick and mortar locations including pools, spas, furniture, fireplaces, pool tables and more. Now customers can research products with detailed descriptions and updated images before shopping in store.
The new site is built with a responsive Magento design, allowing full access from any device. The new site was created with a special focus on easy navigation. Specifically, a left column with attributes was added to make filtering easier. It was important to Watson’s to show customers they offer more than their well-known selection of pools and spas.
In addition, Watson’s needed a dependable and flexible content management system that was easier to manage in house. With quick product turnover and ever-changing seasonal promotions, it was critical that their in-house staff could make quick and easy updates to the website.
“Our experience with the team at InteractOne has been superior. They are extremely responsive to our needs and questions and expertly deploy solutions while relaying the information back to us in layman’s terms.” says Tracy Kuethe, Marketing Manager at Watson’s.
About InteractOne:
InteractOne has provided web development and Internet marketing services since 1998, becoming a Magento partner in 2009. We have helped many companies develop and establish very successful eCommerce sites and internet marketing strategies.
Many people don’t consider the need or necessity for Magento version upgrades once an initial package is installed and running. Many think that once they’ve got their software setup and tweaked just the way they want (or especially once they’ve added several customizations) that an upgrade might then somehow “break” or undo all of the special changes, settings, edits and customizations on which they’ve spent countless hours getting just right. Why would anyone want to then go and “mess things up”? One might also ask, “Aren’t those updates and upgrades just adding more buttons and whistles that I don’t need? Couldn’t they potentially change the placement of elements in the user interface that I don’t have the time or desire to re-learn?”
Well, sometimes some of those concerns are legitimate, but rarely. The more pressing concerns that should be at the top of your list are:
Are my customers satisfied with the overall experience of navigating my site?
Is the site I depend on for my business secure?
Can my customers continue to trust my site for a hacker-free experience?
Does my site comply with Payment Card Industry Data Security Standards? (PCI DSS)
Will my customizations and plug-ins continue to function worry-free and conflict-free?
Will I be able to expand, change, or upgrade in the future?
Is my site secure?
Is my site secure??
Is my site secure???
…you get the idea.
The year of 2015 turned out to be particularly busy with security hacks, breaching all levels of the web, including even CIA Director John Brennan’s personal email account. Magento has itself had its share of hack attempts over the year, having published several security patches and version updates as recently as the end of October 2015. The latest patch, SUPEE-6788, being a fairly major update to the core code.
So the question of how often to perform version upgrades in Magento is somewhat self-explanatory (hint: as often as new versions are published), however many version upgrades are simply the latest core code with the latest security patches applied. For example, if your site is running Community Edition 1.9.2.0, an upgrade to v1.9.2.1 simply adds the latest patches up to that point.
Version release notice from CE 1.9.2.1 upgrade page on Magento.com
Similarly, the latest Community Edition version (1.9.2.2) includes the major patch SUPEE-6788 supplied at the end of October 2015, where an even more important warning is posted:
Version release notice from CE 1.9.2.2 upgrade page on Magento.com
Notice that this patch can impact previously installed extensions and customizations? There are major core code changes in SUPEE-6788, and if your Magento site is languishing back in earlier versions and/or heavy customizations, you may be at risk for opening up your site to some major security holes and also finding yourself in a now more painful upgrade. Depending on how far back your version of Magento may be, the difficulty of an upgrade could be high or low. In the case of SUPEE-6788, it’s already a tiny bit painful for those running later versions around 1.9.x, so even earlier versions could cost you more to bring up-to-date, as well as cost your company if the security risks aren’t handled in a timely manner.
A compromised site can have long-term consequences for both customers and merchants. Customers might suffer financial loss and identify theft, while merchants can face damage to their reputations, loss of merchandise, higher processing fees, revoked privileges with financial institutions, and the threat of lawsuits.
This all may seem like common sense, but it’s surprising how many companies continue to allow their websites to operate without Magento version upgrades or patched software. In May 2015, CBS News reported that online security firm Cyphort had scanned 1.75 million URLs against a list of known malicious sites and found that the software behind as many as 21% of the URLs referenced hadn’t been updated with the latest security patches. Further, it was reported that none required “special or invasive means” to solve the issue, and that “attackers need no more than a standard browser to find vulnerable sites to exploit.”
Though there are occasions when an update or patch isn’t focused on security (SUPEE-6237 patched a change in the USPS API that impacted shipping rates), it is fairly easy to agree on the fact that any and all patches and upgrades will provide important updates to your Magento installation. If updating important functionality and performance standards aren’t a high priority, certainly the idea of a malicious hacker taking down a site for hours or days along with gaining access to sensitive customer information should be plenty to rattle the cage of any player in the e-commerce arena.
PHP7 is here and our developers noticed some impressive speed improvements right off the bat. It’s important to keep your Magento server up-to-date for security and performance, but we recommend upgrading to PHP7 for noticeable Magento performance improvements. After some benchmark testing, we noticed a 70% decrease in page load time and 30% less memory consumption across the board on a base installation of Magento 1.9.
Our Lead Developer wrote some simple directions on upgrading to PHP7 from PHP5 on Ubuntu. These should be performed by a developer or system admin – Contact us for help on upgrading to PHP7 on any Magento install.
There’s only a couple of minor quirks, like not having dl() support which killed a couple of the extensions that had copy-protection on one site. There are a couple of minor things to do to make PHP7 work but it’s covered below.
If you’re ready to take the Magento/PHP7 plunge and are using Ubuntu, then this is how you can do it:
Remove PHP5 (Warning: This will remove PHP5 from your system completely.)
Here are some common problems with Magento after installing PHP7 –
If Apache is dumping plain text php instead of rendering it, then be sure that you’ve installed libapache2-mod-php7.0.
sudo apt-get install libapache2-mod-php7.0
sudo service php7.0-fpm restart
sudo service apache2 restart
Getting a white page or error about mcrypt in Magento?
sudo apt-get install php7.0-mcrypt
sudo service php7.0-fpm restart
sudo service apache2 restart
Still not feeling confident? If you aren’t ready for upgrading to PHP7 on your own, give the experts at InteractOne a call today at (513) 469-7042 or fill out our contact form.
We recently teamed up with hosting specialist, byte, to be a part of their Magento support system for MageReport.com. MageReport was created to protect the performance and security of Magento shops. By sharing their tools with the rest of the Magento community, byte hopes to increase the overall security of Magento worldwide.
We are certainly happy byte chose to share their useful tool. After using MageReport for scanning Magento sites, we were extremely impressed with the level of detail and accuracy it provides. MageReport is a definite asset to Magento merchants and the Magento Community.
How MageReport works
MageReport is a free service that checks the security status of Magento stores with lightening quick results. The report not only shows insight on the security status of scanned shops, but also on how to fix possible vulnerabilities. While it is not possible to see existing Magento files from the outside, MageReport uses behavior-based identification patterns. All possible because each Magento patch introduces subtle changes in behavior. In addition, it’s possible to request a few static files and derive the Magento version from that.
MageReport.com checks Magento shops for the following known security vulnerabilities:
Credit Card Hijack
Ransomware
Cache leak vulnerability
Guru Inc Javascript Hack
Outdated Magento version
Unprotected development files
Default /admin location
Unprotected Magmi
Unprotected version control
Outdated server software
Security patch 5994 (admin disclosure)
Security patch 5344 (Shoplift)
Security patch 6285 (XSS, RSS)
Security patch 6482 (XSS)
Security patch 6788 (secrets leak)
Security patch 7405 (admin takeover)
SSL Certificate check
Head over to MageReport.com to read more about the Magento tool and to scan your site for security patches.
By Brad Leslie, Certified Magento Developer at InteractOne
Magento 2 was released during Q4 of 2015, starting the next era of Magento within the eCommerce space. Originally announced in 2010, M2 has been long awaited by shop owners who are now left with a number of decisions to make regarding the new platform. Among the most important decisions are whether a shop should make the jump to M2 and, if so, when.
Magento 1 vs. Magento 2
There are some fundamental differences between Magento 1 and Magento 2 that shop owners need to understand before they can really evaluate whether the upgrade makes sense for them. While Magento 1 and Magento 2 are both Magento products, the file system and database structure are completely revamped in M2. This means that the M1 database (settings, orders, products, customers, etc) can’t be used directly with the M2 installation. Likewise, M1 custom module and theme files can’t be copied into Magento 2.
Magento has released a guide related to expediting the Magento migration process, but it is still a complex procedure and the difficulty is compounded by the customizations made to the M1 install.
Learning Curve
Even Magento 1 certified and Magento 2 trained developers are getting used to what’s essentially a brand new platform, but most developers are excited about the challenge and ready attack it head-on. All Magento 1 shops should, at the very least, be starting discussions about Magento 2 migration, if not planning the development process and launch of the Magento 2 site.
If a shop needs to rebuild their Magento 1 site quickly and without room for error, it should most likely be rebuilt on the latest version of Magento 1. Developers, project managers, marketers and solution partners, in general, are used to – and very good at – building out Magento 1 sites. Many have been doing so since the early versions of Magento. Additionally, shop owners and administrators are familiar with the admin processes of Magento 1. Magento did a good job of making sure the Magento 2 admin processes are similar to Magento 1, but some of the settings and other admin areas have been moved around.
Magento 2 Training
There is a learning curve for everyone when switching to Magento 2. If there are a lot of problems within the existing site, it’s possible that the proper training of admins and / or developers would be delayed in exchange for launching a Magento 2 version of the site quickly. Some people can learn on-the-fly and be successful, but there are sure to be growing pains with that approach that could be avoided given proper training before making the switch.
If It ‘Ain’t Broke Don’t Fix’ It
The final reason to stay on Magento 1 rather than upgrading to Magento 2 right away is if the site has few or no issues. While there are advantages to Magento 2, the saying ‘if it ain’t broke, don’t fix it’ is certainly applicable when dealing with what is often the main revenue stream for a company.
Ready? Time to Plan Your Magento Migration
If a shop owner has decided that upgrading to Magento 2 is right for them, the next step is to plan the “jump.” Design, development and training workflows are different for everyone, but a well thought out plan will mitigate the chances for failures across the board. Ensure a smooth migration by establishing ahead of time what each department will require –
Developers should know which Magento 1 extensions exist for Magento 2 and what needs to be custom coded,
Designers should know what is possible within the new base themes,
Admins should know how Magento 1 processes translate to Magento 2, and
Project managers need to understand any changes in how long something takes after the switch to Magento 2 is paramount to the success of a migrated Magento 2 shop.
The Bottom Line
If a shop has a successful Magento 1 site, or is migrating to Magento from another platform, there is no reason to delay the planning and development process. Magento has supplied a brand new documentation portal in preparation for Magento 2 and the Magento community will be learning / sharing more about their experiences with Magento 2 as time goes on.
If you’re wondering if you are ready for Magento migration, contact us to find out more and get started today.
“During customer registration on the storefront, a user can provide an email address that contains JavaScript code. Magento does not properly validate this email and executes it in Admin context when viewing the order in the backend. This JavaScript code can steal an administrator session or act on behalf of a store administrator.”
In a nutshell, SUPEE-7405’s most important fix is that it blocks hackers from breaking into your admin and taking over your store. Clearly SUPEE-7405 is critical to have installed. Developers should estimate around 3-4 hours to install the patch locally, test and fix, push to dev, allow the client to test, and then deploy to production.
However, below is a list of changes that may arise after SUPEE-7405 is applied. These will need to be evaluated on a site-by-site basis, depending on the extensions you have installed.
Changes from patch:
Admin
Better validation in admin when logging in via URL
Protect against executable code within order comments and exported grid data
Improved case handling when validating admin actions
New validation for admin file uploads so executable files can’t be uploaded as images
Image validator
Improved forgot password validation
Frontend / Core
Protected un-sterilization of user data
Improved validation for new accounts
Cleaned up Authorize.net integrations related to order data at the time of order placement / success
Sanitize product option data so code can’t be executed
Improved exception handling in email queue process
Added the ability to renew a form key
Escape data that’s output on the frontend (products, reviews, etc)
Improved guest data handling
Added Zend XML security class
Possible issues after patch:
Extensions
Mass action / report extensions that override CSV exports
Product / slider / swatch extensions or anything else dealing with image uploads
Auth.Net
Payflow (PayPal)
Grid extensions
Misc
Themes should be sanitizing all object data output on the frontend (this is already a best practice)
We stress that Magento Security Patch SUPEE-7405 is VERY important. Without it, you’re exposed to vulnerabilities that exist throughout your Magento installation on both the front end and the admin.
Magento offers a very powerful, enterprise-level platform on which to base an e-commerce store. There aren’t many that rival what Magento offers in overall functionality, versatility, and price. However, along with that enterprise-level experience comes the price of maintaining a robust software package that usually takes a developer (or team of developers) several years to master.
To appreciate the level of knowledge necessary to be a certified Magento developer, consider the dozens of hours of direct training and hands-on experience necessary to successfully complete the Magento certification exams. Notably, there are different certifications for different areas of code development: Frontend Developer; [Backend] Developer; [Backend] Developer Plus; and Solution Specialist. Yet, as with most knowledge in this world, everything is up for interpretation and humans are simply innovative and self-sustaining creatures. Plus, with the ever-evolving and improving internet, knowledge is ever more at our fingertips than at any point in history.
Why should we bother hiring certified plumbers, electricians, or Magento certified developers? We can easily find a DIY or how-to video on YouTube or better yet, that friend who tinkers in plumbing, electric, or web development.
We hire the trained professionals because there’s always that one thing (or several) the DIY videos or your buddy didn’t tell you. Before you realize your mistake, it is money and time wasted that could have been saved if only the pros had been called in the first place.
Yep, we’ve all been there. So now it’s time to call upon a certified professional.
Before you decide to have someone open the hood of your Magento customization project, decide if it’s really necessary. Maybe somebody else had your same functionality issue and a trained developer created a nicely packaged extension ready to easily run on top of your Magento package. In many cases, this is the most likely scenario.
Yet, sadly, some merchants go straight for the operating table to a “budget-priced” developer willingly ready to take on your unique needs without considering the scenario above.
This is usually where things begin to go very wrong for so many.
Yes, your budget developer(s) delivered on your Magento customization project as promised relatively on-time, relatively on-budget, and relatively without too many bugs. Your new functionality feels like a brand new pair of shoes that were custom made for you. …ahhh, feels nice.
Until… [cue scary music]
It’s several weeks down the road, orders are flying through your store, and accounting notices that something isn’t adding up quite right. Your shipping rates aren’t always calculated correctly, the tax tables are wrong, your discounts aren’t applying to all orders the same way, etc.
You’ve got a nightmare on your hands, and your budget-friendly developer that originally authored your custom functionality has fired you over “too many complaints.” You’re up a creek and need some expert triage on your hemorrhaging web store. You call up an agency with certified Magento developers, and they tell you the news isn’t good, it’s going to take some risky surgery, but they think they can save your store. There’s just one catch: It’s going to take dozens of hours to effectively “learn” what the other crafty developers did and to effectively undo and redo what they were trying to do correctly. In addition, they’ll (likely) need to install several updates and security patches – if not upgrade the version altogether! This also requires many hours to, again, undo direct edits to core files that should never have been edited in the first place.
Why? Because any Magento developer worth their salt will tell you, as a golden rule, that Magento core files should never be altered for custom functionality. Repeat, Magento core files should never be altered for custom functionality. Yes, of course, the core files are touched all the time by updates and patches, but those are from Magento’s core development team and are guaranteed to work assuming everything is intact as the current working version of your site dictates. Everything else should be an add-on that doesn’t directly alter the core, and should theoretically be removable without “breaking” the website. If everything was done correctly, this is exactly how it should go every time.
This developer has seen this sad story one too many times. A Magento customization job so hacked that much of the default functionality had been either hidden or removed from the dashboard altogether and a client asking for features that should have already been there out-of-the-box.
Good developers want to be proud of their work. They enjoy working in environments where other good developers show the same pride and care. We enjoy knowing that others who share our passion also take pride in our work. There’s always a good chance somebody else is going to eventually get a peek under the hood to see our handiwork, so why not do a good job before signing your name on something?
Many merchants find themselves in the Magento customization trap. They begin to brainstorm every site function possible while simultaneously hiring a consultant or developer to try and recreate the wheel. The truth is that 99.9% of the problems have been solved already, whether it is in a published form or not. If only merchants had taken the time to find the right Magento development team that could have handled the majority of their issues quickly and effectively right out of the gate.
In most cases, it pays to hire that certified plumber after all.
By Brad Leslie, Certified Magento Developer at InteractOne
Magento released SUPEE-6788 on October 27, 2015, which fixes a number of security issues relating to customer registration, forgotten customer passwords, admin actions, SQL injections and more. The difficulty with this patch, in particular, is how invasive it can be when applied to a highly customized shop.
“Magento Enterprise Edition 1.14.2.2, Community Edition 1.9.2.2 and the patch bundleSUPEE-6788 address several security issues. Unfortunately, addressing these issues required some changes that may possibly break backward compatibility with customizations or extensions.” – Read More
Magento is modular, meaning that individual features are packaged together and can be added or removed without impacting the other features. 6788 fixes all of the core, read ‘out-of-the-box’, modules, but those same changes must also be made to the local and community, read ‘custom’, modules. There are various scripts on the web that will attempt to fix the custom modules automagically, but these will rarely work 100% due to inconsistencies in acceptable coding practices within Magento, namely the admin routers.
Standardizing these inconsistencies is typically the most time consuming aspect of applying 6788. Since magic scripts can’t fix every issue, the changes must be evaluated and, if necessary, corrected by hand. Correcting modules that the developer wrote himself would take a fair amount of time, but the number of third party modules installed that the developer is not completely familiar with is directly proportional to the amount of time required to fix those modules. Some modules are more complex than others, but they all must be evaluated and most will require updates for consistency.
Magento has also altered their support for backticks when working with collection filters. A find-and-replace can fix most of these fairly easily, but there are a number of extensions that use direct queries with backticks that need to be rewritten on a case-by-case basis.
In addition to fixing the custom modules, custom themes may require updates due to several template changes. The customer registration form now requires a ‘form_key’ field and the forgotten password layout XML has been updated to use a new block.
The front end has received some more attention with the addition of permissions for custom variable and CMS blocks. These are managed via the ‘variables’ and ‘blocks’ menu items within the admin panel at System > Permissions. Any custom variables or CMS blocks that will be used on the front end must be whitelisted via those pages.
It’s important to understand that running SUPEE-6788 alone is not enough for a shop to be protected from the vulnerabilities that it fixes. While magereport.com may say that the patch has been applied, if all of the modules have not been evaluated and updated, the shop is still at risk.
Some tell-tale signs of an issue with 6788:
Admin URLs / actions throw 404 errors
Missing content on the front end
API connection issues
Do you know if your site has the SUPEE Patch 6788 installed? Better yet, was it installed correctly? When it comes to Magento, Security patches should be taken seriously and installed by true Magento trained experts.
By Amanda Watkins, Marketing Communications Manager at InteractOne
Top eCommerce platforms, which is best for you?
We chose to compare and contrast the top eCommerce platforms by market share for the top 10k sites based on data from BuiltWith.
Starting an eCommerce business can be exciting and rewarding. One of the first important steps is deciding on the type of platform to use. When it comes to building, managing and running your website, you want to choose the right platform that will propel you to success, not a failure – especially if financial resources are limited.
As a long time senior Magento partner, we have worked on a lot of websites for many different levels of companies. While Magento is our platform of choice, we understand that it isn’t for everyone and every business. Whether you are just starting out or are ready to take your business to the next level it’s important to understand what you are getting into.
According to BuiltWith, Magento, WooCommerce, and Shopify are top platforms by market share for the top 10k eCommerce sites.
All three platforms are chosen by top companies, but which is the top eCommerce platform for you?
Magento
Magento Community and Magento Enterprise editions are dominating the eCommerce platform community with a combined total of 20%. Free to download for the community edition, open source, powerful and scalable, it’s no surprise that Magento is the most used eCommerce platform worldwide.
Magento Pros:
Feature-rich, out-of-the-box with flexible options for nearly all languages and currencies
Thousands of extensions are available thanks to the flexible API architecture
Manage multiple stores from one admin
Supportive Community with a slew of developers and partners ready to build and solve problems
In-depth training available to help you get started
Two editions are available, community for small businesses and enterprise for larger merchants
Magento Cons:
Magento can be very complicated for a non-tech savvy merchant
Development can get expensive, especially for custom work and qualified help
Self-hosted, meaning it requires a Magento hosting provider
WooCommerce
Gaining a lot of attention with 8% of the eCommerce platform community, WooCommerce is quickly becoming one of the most used eCommerce platforms. Different from Magento and Shopify, WooCommerce is a plugin for WordPress and easily integrates into any WordPress site. Free to install, user-friendly, familiar and open source it’s no surprise WooCommerce is gaining popularity.
WooCommerce Pros:
Easily integrates with WordPress
Easily customizable with plugins
Developmental resources widely available via WordPress developers
Built-in blogging for easy Marketing and SEO
User-friendly interface
WooCommerce Cons:
Lacks scalability
Basic features require plugins that are becoming more costly as the platform gains popularity
While aspects of WordPress are simple, plugin additions can get complicated
Self-hosted, meaning it requires a hosting provider
Shopify
With also 8% of the eCommerce market share comes Shopify. Shopify is notably different from Magento and WooCommerce in that it is a SAAS (software as a service) platform – not open source or downloadable (the code is proprietary). Designed for ease of use, Shopify is a one-stop-shop supplying hosting, set-up and customer support, making it an easy choice for busy or less tech-savvy merchants.
Shopify Pros:
Easy to use and set up
Hosting provided
Technical support provided
Comes installed with many basic payment options
Shopify Cons:
A commercial product requiring monthly fees
Inventory restrictions dependent on your payment plan or level
A limited number of available free themes
Lack of flexibility – Limited number of available add-ons
Which is best?
All three are top eCommerce platforms and have their pros and cons. The key is choosing which one you can live with, or more importantly, can afford. Magento is a market leader for a reason. It’s scalable, customizable and ready for global eCommerce. Although potentially pricey for smaller companies expecting a customized shop, Magento is a great investment for businesses whose growth is dependent on a flexible and powerful platform. WooCommerce’s easy integration into WordPress is worth noting. Bloggers turning merchants with basic tech savvy could likely profit from WooCommerce. However, WooCommerce merchants are discovering increasing prices with the increasing popularity of the platform. Finally, Shopify provides real benefits for smaller companies with all-inclusive pricing for hosting, support and set up and is a great choice for the busy or less tech-savvy merchant. Nevertheless, successful merchants could quickly outgrow the platform and need to migrate to a more scalable platform.
