Clover vs. Drupal

Clover is well suited for high-volume environments where quality and dependability are paramount. The hardware can scale easily and always looks good on the counter. I have even seen Clover hardware used in small mom-and-pop type stores. The ability to swing the monitor around for signature is really nice. Customers appreciate the ease of use. The stations we have to use nice large bright screens. Not familiar enough with the Clover product line to know if the smaller screen sizes are available for applications where space is a concern.

Incentivized

If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.

Incentivized

• BluePay has been very responsive when we've had questions and gone out their way to make sure that users understand the answers that are given.
• During our cut over to BluePay we found that there were reports that our users were used to having that didn't have an equivalent on BluePay's site. Our account rep went above and beyond to make sure that our users had the information that they needed by having custom reports sent on the schedule that we determined.
• Overall our interchange rates are much lower with BluePay than they were with our previous gateway provider.

Incentivized

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

• Focus functionality on retail use and not broad based with focus on food services
• Build a turn table into the countertop unit so both the employee and customer can use the tablet
• Offer color choices in units (white is not always friendly with long term use)

Incentivized

• This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
• Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
• The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.

Incentivized

The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.

There are numerous aspects to Clover's usability: the usability of their point of sale systems, the usability of their CRM and web dashboards, and the technical side of integrating with other third-party services. All are top tier. Clover's usability is excellent and I have never had a problem figuring out how to use their services at any level. The POS system has a very low barrier to entry and an easy learning curve for newcomers.

Incentivized

As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.

Incentivized

Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).

Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.

Incentivized

We rarely have problems, but when we do, they are major and the system becomes unusable. While Customer Support does eventually respond and fix the issue, they can take a long time. If a major problem occurs on a weekend during the dinner rush, it can be catastrophic to sales and customer returns.

Incentivized

As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.

Incentivized

I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.

The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.

Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%

Incentivized

None are available on the list. Clover competes with HotSauce, Paradise, Poynt, and many more POS systems. We easily sell Clover more than anything else and everyone loves it. It's easily one of the best products I've seen since I have been in integrations. The sales managers love it, our sales reps love it, and most importantly our merchants love it.

Incentivized

Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.

Incentivized

Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.

Incentivized

• Definitely makes us look more professional, and we are able to handle products much smoother and faster
• The reporting allows us to see what is really selling and how much money we have actually made, which is also great, especially when you are selling things you have made or grown because you may not always have an inventory, but you can tell how much you've sold.
• We can't pause the fees for the "off-season," so it definitely is wasted money during those times.

Incentivized

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs