Mobile ecommerce: your store on a phone, with 12 checks in 15 minutes

In short: mobile ecommerce (m-commerce) is shopping on a phone, and the mobile version of your online store now decides most of your sales. In Bulgaria 63.37% of web visits in October 2026 came from a phone (StatCounter), and Google indexes every site by its mobile version. Orders lag behind visits, because retail converts at 3.7% on desktop and around 2% on mobile (Contentsquare, 2026).

This guide is for merchants selling in Bulgaria, from Bulgaria or across the EU. CloudCart facts come from the platform documentation and the Design, Cart and Checkout, CloudCart Pay and Analytics pages, with admin menu names as they appear in English.

How many orders come from a phone

Almost two out of three visits in Bulgaria arrive on a phone, but the share of orders from phones is usually smaller. People browse more on the phone and more often fill in the form and pay on a computer, so watch the two numbers separately.

Measure	Value	Source
Visits from a phone, Bulgaria, October 2026	63.37%	StatCounter Global Stats
Visits from a computer, Bulgaria, October 2026	35.82%	StatCounter Global Stats
Visits from a tablet, Bulgaria, October 2026	0.81%	StatCounter Global Stats
Visits from a phone, Europe, October 2026	54.45%	StatCounter Global Stats
Retail conversion rate: desktop and mobile	3.7% and around 2%	Contentsquare, 2026 Digital Experience Benchmarks

Take a store with 1,000 visits: 634 from a phone and 366 from a computer. At 2% the phone brings about 13 orders, and at 3.7% the computer brings about 14. The phone delivers 63% of visits and a little under half of the orders. That gap is your room to grow: at 2.5% mobile conversion the same visits bring 3 more orders per 1,000.

Cross-border sellers: Bulgaria is more mobile-heavy than the European average, and each country shows its own mix.

Important: StatCounter measures all websites, not only stores. A store running ads on Instagram and TikTok sees more phones, while a store selling office equipment to companies sees more computers. The exact number for your store is in Analytics.

How to see visits and orders from phones in CloudCart

In CloudCart the phone share sits in Analytics, in four boxes, with nothing extra to install. Admin sessions are not counted, so your own test visits do not skew the numbers.

1. Open Analytics and pick a period. Take the last 30 days. If your plan includes comparison with the previous period, turn it on to see whether the phone share is growing.
2. "Online store sessions by device type". Sessions and percentages for mobile, desktop and tablet, sorted from the largest.
3. "Conversion Funnel". Three stages, Cart, Initiated Checkout and Orders, with a switch between Desktop, Mobile and Total. If on Mobile you lose far more people between Initiated Checkout and Orders, the problem is your mobile checkout.
4. "Abandoned carts rate". The share of abandoned carts, with a separate line for phone and computer.
5. "Sales by location". Orders and revenue by country and city, split into phone and computer. A tablet order counts as a phone order here.

The Analytics settings (the gear icon) have a switch for showing devices, and when it is off the phone and computer split disappears. In the funnel and in abandoned carts, tablets count as desktop.

What mobile-first indexing is and why it drives your SEO

Mobile-first indexing means Google crawls and ranks your site by the version a phone sees. Google announced on 31 October 2023 that the move to mobile-first indexing is complete for the whole web (Google Search Central).

For an online store this has three practical consequences:

• What is hidden on the phone does not exist for Google. If the product description, the size chart or the reviews appear only on desktop, Google ignores them. The mobile page needs the same text, headings and structured data.
• Images have to load on the phone too. The same alt text and image URLs, with no images that appear only after a tap.
• Pop-ups hurt. A window that covers the content as soon as a visitor arrives from Google can push the page down in the results (Google Search Central). Cookie banners and legally required age checks are the exception.

Google recommends responsive design as the easiest way to meet these rules. The full SEO checklist is in the guide to SEO for an online store: a 30-point checklist.

Responsive design, a separate mobile site, a PWA or an app

For an online store the best choice is responsive design: one URL, one HTML page and a layout that rearranges itself for the width of the screen. A separate mobile site (m.yourstore.com) means two versions of every page, which is why few stores use one today.

Option	What it is	Pros	Cons	Best for
Responsive design	One page for every screen	One URL for SEO, one set of content, one thing to maintain	Check the design on a phone after each change	Almost every store
Separate mobile site (m.)	A second site only for phones	Full control over the mobile view	Two versions of content, redirects, indexing risks	Rarely worth it today
PWA (Progressive Web App)	A site the customer adds to the home screen like an app	An icon on the phone, Web Push on iPhone too	The customer has to add it themselves	Stores with many repeat purchases
Native app (iOS and Android)	A program in the App Store and Google Play	Notifications, loyalty, quick login	Development, upkeep, the customer has to download it	Large brands with thousands of regular customers

CloudCart's ready-made themes are responsive, and the themes screen shows the active theme in a desktop and a phone view. Storefronts ship with a PWA manifest by default, so a customer on iPhone can add your store to the home screen. A storefront built entirely to your own design is made on Nitrogen, CloudCart's headless technology, for example with an AI agent using vibe coding, while the catalog and orders stay in the same admin. Choosing a theme is covered in the guide to ecommerce website design in CloudCart.

How to test the mobile version of your store: 12 checks in 15 minutes

The most reliable test is a real order from your own phone over mobile data, the way your customers shop. Do it on an iPhone and on an Android phone, because Apple Pay and Google Pay appear differently.

1. Arrive from Google. Open the store from a search result, as a new customer would.
2. The first screen. Without scrolling, it should be clear what you sell, with one obvious button. A large banner that pushes products down loses the customer here.
3. Text reads without zooming. If you reach for two fingers to zoom in, the font is too small. Readability is also part of store accessibility under the European Accessibility Act.
4. Buttons work with a thumb. Google's Lighthouse accepts tap targets of at least 48 × 48 pixels.
5. Menu and search. Find a product in 10 seconds with the menu, then with search. Type a word with a typo, and in Latin letters if your catalog is in Bulgarian.
6. The product page. Photos swipe and zoom, price and stock sit above the button, and choosing a size or color needs no precise taps.
7. Pop-ups. The close button is visible and easy to hit.
8. The cart. The shipping price shows in the cart, before the form.
9. The form. The phone field opens a numeric keypad, the email field shows the @ key, and errors are explained next to the field.
10. Payment. Try Apple Pay or Google Pay and a card, with no redirect to another site.
11. The order email. Open the confirmation on your phone and check that the buttons and product table are readable.
12. Speed. Run a product page through PageSpeed Insights and look at the Mobile score.

In the CloudCart admin you can preview the phone view without a phone: in Design → Colors and typography the live storefront is on the right, with Mobile (about 375 pixels), Tablet and Desktop buttons at the bottom right. The last test is still an order from a real phone.

Phone speed and Core Web Vitals

Core Web Vitals are the three measures Google uses for how a page feels to the visitor (web.dev). Google reads them at the 75th percentile of page loads, separately for mobile and desktop:

Measure	What it measures	Good value
LCP (Largest Contentful Paint)	When the largest element appears: the product photo or the banner	2.5 seconds or less
INP (Interaction to Next Paint)	How quickly the page reacts to a tap	200 milliseconds or less
CLS (Cumulative Layout Shift)	How much the content jumps around while loading	0.1 or less

Slow mobile stores usually carry heavy photos, video in the first screen and many third-party scripts. Check every new storefront app in PageSpeed Insights before and after you turn it on. The Core Web Vitals report in Google Search Console shows which groups of pages are slow on phones.

How to make checkout easier on a phone

Checkout on a phone gets easier when the customer types less: one page, guest checkout, Apple Pay or Google Pay, and delivery to a courier office or parcel locker. In Bulgaria many orders go to an office or locker of Econt, Speedy (DPD Bulgaria) or BOX NOW, the local couriers and locker network. On a phone the customer picks a point from the list or map and skips the address fields.

CloudCart uses a one-page checkout by default. The settings are in Settings → Cart and Checkout:

• Who can order. Guests, registered customers or both. For phones choose both: a guest orders without a password and can get an account automatically after the order.
• The fields. First name, last name, phone, street, number and an extra address line can each be required, optional or hidden, as can the region and postcode. Hide everything the courier does not need.
• The shipping price. The courier returns the price for the exact office, locker or address before the customer pays. With a Google Maps key in the settings, a map helps the customer pick the nearest point with a finger.
• What happens after "Buy". Set the product button to go straight to checkout, skipping the cart.

For customers who prefer cash on delivery (paying the courier when the parcel arrives), the Fast Order app (Apps → Fast Order) adds a product page button with a short form: only email is required, and phone and name are optional. Fast Order works only with cash on delivery. The Click to Call app adds a floating button that opens the phone's dialer with your number in one tap.

Does your online store need a mobile app?

Most online stores do not need a native app: a good mobile version, a PWA and browser notifications cover what the customer needs. An app makes sense with thousands of regular customers who buy every month and a budget to build and maintain it for iOS and Android.

Notifications without an app go through Web Push. In CloudCart you turn the channel on in Marketing → Channels → Channel settings → Web Push. On iPhone, Web Push works from iOS 16.4 onwards and only once the customer has added the store to the home screen (WebKit), and inside the in-app browsers of Instagram, Facebook and TikTok nobody can subscribe. So Web Push complements email, SMS and Viber.

The app you are more likely to need is the one for you as the merchant. CloudCart Admin for iPhone and Android notifies you of every new order, and from it you change the status and create the shipping label (the CloudCart Admin mobile app).

Mobile mistakes that cost you orders

• Testing only on a computer. A shrunk browser window does not show the keyboard, Apple Pay or real speed on mobile data.
• A pop-up in the first second. Show the newsletter sign-up after a scroll or on exit intent.
• Long product names. A 120-character name takes three lines and pushes the price down. Put the brand, type and main feature in the first 60 characters.
• Ads that land on the homepage. A customer from Instagram saw a specific product and expects to see it right away.
• Mandatory registration. A password on a small keyboard is the surest way to make a customer put off the order.

How to track your mobile results every month

Track three numbers once a month: the share of visits from phones, the conversion rate on phones and the abandoned cart rate on phones. If the share grows while mobile conversion falls, something in the mobile path has broken.

1. Write the numbers down. The phone share from "Online store sessions by device type", the three Mobile stages from "Conversion Funnel" and the phone line from "Abandoned carts rate".
2. Compare with the same month last year. November and December bring more phones.
3. Change one thing at a time. After 2 to 4 weeks compare the Mobile funnel with the period before.

The numbers from your AI assistant, without opening Analytics

CloudCart Analytics is also available through the platform's Admin GraphQL API (the analyticsMetadata and analyticsReport queries). Create a PAT token in Settings → PAT tokens (it can have an expiry date and an IP limit), connect Claude Code, ChatGPT Codex, Gemini CLI or Cursor with the sentence from the AI integration with CloudCart page, and ask: "Give me sessions by device for October and September, the Mobile funnel and abandoned carts on phones. Put them in a table and tell me where the biggest difference is." Then ask which checkout fields are required, and the assistant suggests one change for the next 2 to 4 weeks.

Frequently asked questions