Daily E-Commerce Pulse Report (Photo by Denny Müller on Unsplash)

Top 2024 resources on bad

Best bad resource in 2024.
Learn more about bad to improve your e-commerce strategy.

  • 10 Ways Bad Data Hurts an Ecommerce Business - Data is essential for ecommerce businesses. Order quantities, shipping addresses, sales history, marketing performance — all rely on accurate data. Thus missing or inaccurate data can harm a business.  Here are 10 ways that poor data can reduce ecommerce performance.
    Topics: product, hurts, customers, missing, typically, shipping, poor, shipments, rate, ways, ecommerce, problem, business, bad, data.
  • 10+ Reasons Why Overworking is Bad for Your Health (and Your Career) - Overworking has become the norm for many professionals. While being constantly plugged in can make us feel safe, connected, and in the know — both at work and at home — it also means we never really clock out.
    Topics: stress, overworking, health, work, hours, bad, career, sleep, heart, youre, reasons, mental, overwork.
  • 12 Bad Link Building Practices & What to Do Instead - Gaining inbound links from other websites is one of the best ways to improve your website’s rankings on search engines. However, link building can require a significant investment of time and resources and it may be tempting to take shortcuts.
    Topics: links, way, website, instead, practices, site, bad, web, content, building, link, websites.
  • 20 Bad Habits That Are Making You Less Productive - There are a host of bad habits many of us do every day, and research shows these habits really hurt our productivity, especially at work. The more aware we are of how these things are affecting our productivity, the more proactive we can be at taking responsibility for our choices.
    Topics: break, making, bad, work, productive, phone, youre, productivity, help, day, habits, habit.
  • 27 Quotes About Design to Get Your Creativity Flowing - Inspiration can often seem illusive and out-of-reach when you need it most.
    Topics: quotes, designer, values, innovate, creativity, writer, things, author, flowing, design, graphic, bad, good.
  • 3M files suit over third-party price gouging of N95 masks on Amazon - Amazon has promised vigilance against third-party price gouging since COVID-19 achieved global pandemic status. The company’s efforts have had mixed success, however, due in part to the sheer volume of vendors that utilize the company’s massive commerce platform. In a suit filed in California this week, 3M claims the seller was charging massively inflated prices […]
    Topics: products, gouging, n95, respirators, bad, files, thirdparty, techcrunch, prices, 3m, suit, amazon, claims, masks, price.
  • - I’m willing to bet you already know what kerning is -- you just don’t realize it.
    Topics: comprehensive, click, word, letters, photoshop, look, k, typography, guide, tool, kerning, bad, space.
  • A Simple Explanation of a 502 Bad Gateway Error & How to Resolve It - When your website experiences a 502 Bad Gateway Error, it can be like solving a mystery. You don't know what exactly happened or why -- all you know is that something's wrong and you need to fix it.
    Topics: fix, explanation, bad, gateway, error, resolve, page, website, server, firewall, simple, websites.
  • Amazon’s new rewards card targets those with bad credit - Amazon this morning announced the launch of Amazon Credit Builder, a new secured credit card offered in partnership with Synchrony Bank. As the name implies, the card is aimed at those who are looking to build their credit history — either to recover from bad credit or to establish new credit. Like other credit products […]
    Topics: pay, way, builder, credit, techcrunch, rewards, targets, amazons, purchases, amazon, online, bad, customers, secured, card.
  • Deliverr’s nearly flat exit price isn’t as bad as it looks - If Deliverr’s final private round did not include onerous downside-protection provisions, its sale could wind up winsome for all.
    Topics: investors, techcrunch, bad, exit, value, startup, nearly, deal, set, recent, flat, looks, wouldnt, price, isnt, money, deliverrs.
  • Ecommerce Microservices: The Good, the Bad and the Ugly - This post was originally published on October 21, 2018 and has been updated for accuracy and relevancy in the market. Hardly a day goes by without an article about eCommerce microservices. Microservices are small services that are loosely coupled, independently deployed and are organized around business capabilities that enable the rapid, frequent and reliable delivery of large complex applications. Though they were established a decade ago, Microservices still remains as a hot new paradigm for commerce back end among many commerce practitioners. While many developers are experimenting with microservices and others are embracing them head on, others have continued to shy away from them because of the perceived complexity and risk.Over the next upcoming years however, we do expect many more practitioners to get on the microservices bandwagon as concepts like Composable Commerce continue to democratize working with Microservices architectures. In the meantime, we want to continue to educate the market on what to expect when adopting a Microservices Architecture. Therefore in this article we will quickly highlight the good, the bad and the ugly about ecommerce microservices everyone should know about. The Good: Microservices offer unparalleled flexibility and modularity when it comes to standing up a new customer experience and rapidly adding additional ones. Microservices share nothing: platform, deployment and data storage are all independent. If a developer needs to make a new microservice and s/he works in Javascript, they can just do it in Javascript. They don’t need to learn a new language in order to keep growing the platform. Developers can work in parallel and release all day long, which significantly reduces time to market for any new application. This is the complete opposite of a full-stack monolithic suite where the majority of functionality lives in a single service that is tested, deployed, and scaled as a single unit. It requires integration phases of the project, quality assurance, etc. to make sure the platform works as one unit because it shares everything. Expanding it into other touchpoints and devices requires a significant amount of customization, making it cost-prohibitive to explore new ideas.   The Bad: When companies are moving from a monolith to a microservices eCommerce solution it can be very difficult depending on the process that is taken. Imagine, you have already invested in a monolithic pattern that you have established through your company. You would have already had your licenses from institutions like Oracle, and have your infrastructure and organisational inertia to continue business as usual. Then, if you choose to replatform your solution that was not built from ground up with APIs and microservices based, you could incur quite a bit of problems. You may end up having to lay off or retrain workers; have duplicative data and connections; lose control of the database and overall are left with a distributed monolith to handle the cross-functional concerns. However, if you end up choosing an API-first, Microservices-based commerce solution like Elastic Path, then it becomes a lot easier. Of course, microservices will require a higher digitally mature team, but teams are able to incrementally replace their monolithic system that makes the management, retraining and implementation of your new solution more seamless. The Ugly: The real downside of microservices is the complexity the mini-services introduce into the architecture. Developers end up needing a microservice to search for a microservice. The more microservices are being used, the more there is a risk of things getting out of control. In her post, Goodbye Microservices: From 100s of problem children to 1 superstar, Alexandra Noonan of Segment described the pain developers went through with the explosion of the microservices and what they did to end it. Another great story, What I Wish I Had Known Before Scaling Uber to 1000 Services, is from Matt Raney, Chief Systems Architect of Uber. You end up breaking the services into so many pieces that you no longer know what is going on. You can’t bring change because every time you make a tiny change and you think it is independent, it actually turns out not to be. To make matters worse, you may run into a problem where you may not know how a particular service exists. You couldn’t rebuild it if it died. You don’t know how to make changes to it because the person who made it is gone. You end up in a pretty big mess. One way we have begun to address these issues is with the Packaged Business Capabilities(PBC’s) with Composable Commerce. Many may think PBCs and Microservices are the same, but not really. All Microservices are PBCs but not all PBCs are microservices. The key difference is business capability, and the acid test is whether a microservice is designed to deliver a well-defined business capability, recognized as such by business users. By packaging these microservices to specifically satisfy business needs, users will experience reduced complexity, enhanced clarity, and business centric planning. Learn more about how they are beneficial to your business here. To sum up: Great News! Defining the structure of the data required to perform the service is key. Exactly the same structure of the data is returned from the server, therefore preventing excessively large amounts of data from being returned. After all, if you set things up the proper way and learn from the mistakes the pioneers have made, you are on your way to success!
    Topics: way, developers, bad, microservices, good, business, solution, microservice, data, know, ecommerce, ugly, commerce, end.
  • Ecommerce Microservices: The Good, the Bad and the Ugly - As previously published on LinkedIn, Ana Milevskaja outlines the facts about microservices that commerce pros should know about. Hardly a day...
    Topics: platform, ecommerce, need, microservice, way, bad, microservices, data, dont, ugly, know, developers, end, good.
  • Flexible Schedules: The Good, Bad, & the Surprising - There’s plenty of science to suggest flexible work schedules are critical for happier, more productive employees, and a more successful company overall.
    Topics: employees, surprising, flexible, hours, remote, schedule, good, working, way, youre, bad, schedules, work.
  • How to A/B Test Your Pricing (And Why It Might Be a Bad Idea) - A/B testing the pricing for your product is a little bit like Goldilocks.
    Topics: ab, bad, product, testing, test, customers, idea, pricing, revenue, price, prices, different.
  • How to Buy Instagram Likes (And Why It's a Bad Idea) - Instagram’s new algorithm uses engagement as the most important metric to determine a post’s popularity. Essentially, the more likes and comments your posts get, the more your posts will be seen by a larger audience.
    Topics: buy, bot, fake, follow, idea, likes, accounts, service, engagement, posts, bad, real, instagram.
  • Leveraging microservices for your business, Part 2: The good and the bad - This article reviews the benefits and difficulties with a microservice architecture. While avoiding the "anti-patterns" and horror stories that are prevalent while sticking to the architecture qualities themselves.
    Topics: qos, leveraging, services, system, business, microservice, team, requirements, bad, ecosystem, service, microservices, good.
  • SEO: 2 Good Ways to Remove Duplicate Content, and 8 Bad Ones - Ecommerce sites often create duplicate content, which saps the ability to drive organic search traffic. There are two good ways to remove duplicate content from search-engine indexes — and eight to avoid.
    Topics: seo, pages, ways, link, content, good, ones, authority, indexed, redirects, remove, search, page, duplicate, bad, engines.
  • SEO: Catchall Redirects Are a Bad Practice - At first glance a catchall redirect page seems like a good solution. Instead of fixing thousands or tens of thousands of redirect errors, set up a simple catchall rule and send all users (and bots) to a single page. But it’s a bad idea.
    Topics: seo, page, search, engines, redirect, redirects, practice, bad, url, catchall, pages.
  • Shopify’s App Store Is Good and Bad, Says ‘Unofficial’ Expert - Kurt Elster's "The Unofficial Shopify Podcast" has been downloaded more than 1 million times. His agency, Ethercycle, helps Shopify merchants drive revenue and profit. You might call Elster the unauthorized Mr. Shopify.
    Topics: bad, theme, store, merchants, expert, team, unofficial, app, dont, apps, menu, shopify, good, thats, shopifys, themes.
  • The 4 Reasons You Chose a Bad Company Name ... Now What? - Picture the scene from the film The Social Network where a fast-talking Sean Parker (played by Justin Timberlake) glides into a lunch meeting with Mark Zuckerberg, Christy Lee, and Eduardo Saverin.
    Topics: facebook, reasons, social, bad, brand, chose, google, names, company, naming, dunkin, business.
  • The 7 Fastest Ways Leaders Kill Company Cultures Without Realizing It - Culture is critical for your business's long-term growth and profitability.
    Topics: culture, cultures, turnover, fastest, company, bad, managers, employee, trust, certain, leaders, gossip, kill, way, realizing, ways.
  • The Bad Remote Work Habits You Should Avoid - A few years ago I was at one of those Big Group Dinners with my marketing team and our clients. There were about 15 of us.
    Topics: work, mental, avoid, habits, working, bad, youre, health, know, feel, team, things, group, remote.
  • The Good News and Bad News for Ecommerce Shipping - Ecommerce sales are up and shipping carriers such as USPS, UPS, and FedEx have responded admirably to demand in the face of numerous coronavirus-induced shutdowns and restrictions. That is the good news for ecommerce sellers. Unfortunately, supply chains have suffered. That’s the bad news.
    Topics: merchants, ecommerce, covid19, bad, volume, paganini, good, shipping, businesses, orders, domestic, cyber.
  • Think Emotion-Driven Decisions Are Bad? Behavioral Economists Disagree. - When it comes to strategy, "emotion" is a dirty word. But experts say the data shows you should embrace your feelings when making tough calls.
    Topics: behavioral, bad, voices, decisions, disagree, word, unlimited, vital, economists, access, hear, zendeskbecome, words, useless, valuablea, think, emotiondriven.
  • What Happens When a Former Tesla Employee Decides to Solve Bad Hangovers? - In this episode of Shopify Masters, you’ll learn how a former Tesla employee discovered a business idea during a trip to South Korea, quickly launched a simple landing page, and then went back to design a real brand after validating demand. Sisun is the founder of Morning Recovery: a science-backed, breakthrough hangover drink that helps counter the negative effects of alcohol.More
    Topics: tesla, things, hangovers, product, actually, yeah, kind, decides, thing, thats, really, employee, think, solve, sort, happens, bad.
  • Why Buying Email Lists Is Always a Bad Idea (And How to Build Yours for Free) - You need people who you can email, and you need them quickly. Oh, and if you could get them pretty cheap, that'd be great, too.
    Topics: content, idea, list, optin, free, addresses, address, dont, lists, build, email, marketing, emails, buying, bad.
  • eCommerce Microservices Explained: The Good, the Bad, and the Ugly - This post was originally published on October 21, 2018 and has been updated for accuracy and relevance to the current market. In today’s world, a one-size-fits-all commerce approach won’t get the job done. It is crucial that brands within eCommerce consistently evolve with today’s market demands and the needs of customers. One of the best ways to do this? eCommerce microservices. eCommerce microservices allow you to meet customer expectations in a fast and flexible manner, so you can always stay up-to-date with eCommerce best practices and new technologies.  But are you aware of all there is to know about eCommerce microservices? Let’s break down the good, the bad, and the ugly truth about microservices in eCommerce that brands like yours should know. What Are eCommerce Microservices? Microservices are small services that are loosely coupled, independently deployed, and organized around business capabilities that enable the rapid, frequent, and reliable delivery of large complex applications.  Though they were established a decade ago, microservices are still new to many commerce practitioners. While many developers are adapting to and experimenting with microservices for eCommerce, others have continued to shy away because of the perceived complexity and risk. That’s likely to change in future years, as Composable Commerce makes it easier to work in microservices architecture. As you decide whether an ecommerce microservices architecture is right for you, here’s what to consider: Need help evaluating eCommerce Solutions? Connect with an Elastic Path expert to answer all of your questions, set up a demo, access a free trial, or discuss pricing options. Get in Touch The Good: Benefits of eCommerce Microservices Microservices are known for unparalleled flexibility and modularity. Standing up a new customer experience and adding additional customer experiences can be done fast with microservices technology.  Microservices are fully independent: Separate platforms, deployments, and data storage capabilities exist separately from each other. If a developer needs to make a new microservice and works in Javascript, he or she can make the microservice in Javascript. They don’t need to learn a new language in order to keep growing the platform. This way, any new application can be built quickly and has a reduced time-to-market. This is the complete opposite of a full-stack monolithic suite, in which the most functionality lives in a single service that is tested, deployed, and scaled as a single unit. To get a platform working requires integration phases, quality assurance, and a shared language. Expanding the monolithic suite to include other touchpoints and devices requires a substantial customization, making it cost-prohibitive to explore new ideas.   The Bad: Common eCommerce Microservices Challenges When companies are moving from a monolithic to a microservices eCommerce solution, challenges do arise. After all, having a monolithic pattern means having infrastructure, licenses, and organizational structure built around a monolithic technology. The possible challenges of a full-on replatform of a solution that was not built from the ground up with APIs and microservices include: Laying off or retraining workers Dealing with duplicative data and connections Losing control of your database Adjusting your cross-functional organizational capabilities and communication These challenges don’t override the benefits of an eCommerce microservices architecture. Choosing an API-first, microservices-based commerce solution such as Elastic Path ensures that you have support as you incrementally replace your monolithic system and retrain your team. The Ugly: The Downside of Adopting eCommerce Microservices Without Support The biggest downside of microservices is the complexity that the mini-services introduce into your team’s developer architecture. When eCommerce microservices first came onto the scene, developers found that they were managing multiple microservices at once. It made for unlinked, challenging work and a process that wasn’t streamlined. Some developers have also encountered challenges tracking their changes and work after adopting a microservices architecture. The autonomy and independence microservices provide your team may also mean that the departure of a single teammate renders some of your architecture impossible to edit. For these reasons, having support when adopting eCommerce microservices is essential. One way Elastic Path Commerce Cloud helps is the inclusion of Packaged Business Capabilities (PBCs).  PBCs and microservices are not the same. PBCs are a grouping of APIs that serve a specific business capability. Microservices are tightly scoped and specific. PBCs are useful because they reduce complexity, enhance clarity, and are developed via business-centric planning. For brands looking for a business-centric eCommerce solution, PBCs are a strong option – and selecting and managing PBCs is made easier with Elastic Path. Should You Adopt an eCommerce Microservices Architecture? An eCommerce microservices architecture will provide the flexible foundation businesses today need to keep up with the ever-evolving commerce landscape. Implementing a microservices architecture benefits both developers and end users with: Abundant opportunities for customization. With the addition of multiple front-ends, you can easily and seamlessly integrate multiple new touchpoints for customers – all while staying connected to the same back-end. Quick and easy implementation. Due to the decentralization of the development process, microservices allow for rapid implementation of changes. This means you can go to market faster with new updates. A leaner technology stack. Since you are only adding what you truly need, you will be able to enjoy a streamlined and more efficient tech stack.  Front-end traffic won’t impact the back-end. In the past, developers have typically had to adjust the entire system to extend services. With microservices, the front-end and back-end are individually scaled, which means high traffic won’t impact what’s happening in the back-end.  Pick and choose the solutions you want. With eCommerce microservices, you can select services and solutions that specialize in your exact needs and enjoy a specialty-tailored approach. Moving Forward with eCommerce Microservices eCommerce microservices may be a major benefit for your business. While the developers of the past have experienced many pain points when adopting microservices for eCommerce, you can learn from their mistakes and adjust your microservices strategy to achieve business success.  At Elastic Path, we want to ensure that the ugly side of microservices never rears its head. Talk to an expert to discover how our team can help you implement a microservices architecture that fits your business needs and objectives.  
    Topics: ugly, explained, business, good, bad, microservices, monolithic, elastic, developers, solution, architecture, commerce, ecommerce, path.