Skip to content
Help Center

Landing page buy box: price per day and the mobile buy bar ​

The buy box on a landing page is where visitors choose how to buy and select Add to cart. Commander can add three things to it: your product's name, a price per day under a purchase choice, and a buy bar that follows visitors on a phone. It can also repeat the buy box price in the page heading area and above the last button. You see all of them on the live page. To create and publish pages, see Landing pages.

Problem and intended user ​

The ecommerce manager (the person who runs the store) sells a product in several sizes or on a subscription. A visitor compares "60 capsules" with "180 capsules" by the total price, and the bigger pack looks expensive. On a phone the buy box scrolls out of sight, and the visitor has to scroll back up to buy. Both slow the decision and can cost the sale.

Current workflow ​

Without Commander, the ecommerce manager works out the price per day by hand, types it into the variant title or a text block in the Shopify theme editor, and fixes it each time a price changes. On a phone, a visitor who wants to buy scrolls back up to the buy box.

Prerequisites ​

  • A landing page for a product, written by Commander. A page for your brand alone has no buy box.
  • For the mobile buy bar: Theme Access, so the page publishes as a Full-width page with your store's own Add to cart. See Theme Access. The basic layout shows no bar. The price per day needs no Theme Access: both layouts can show it.
  • For a price per day: a product that states how much each variant holds. See When no price per day shows under How Commander works.

How Commander works ​

Commander calculates the price per day. AI does not write the number. For a purchase choice, Commander divides the price of that choice by a count it reads from your product, and rounds the result to the cent. For a plan that charges once for several deliveries, Commander divides the price of one delivery, not the whole charge. Fixed rules read the count when Commander writes the page.

Commander reads the count from these places, in this order:

  1. The variant title. Titles such as "14 shots", "60 capsules", "30 servings" and "30 day supply" all work.
  2. The facts you state about the product: the daily dose, the serving size and the nutrition facts. A daily dose such as "take 2 capsules daily" turns a count of capsules into a count of days.

A day count in the variant title is taken as it is.

The words after the price are Commander's own, in the language of the page. They read / day when Commander read a daily dose, and / serving otherwise. AI does not choose them, so the unit always matches the arithmetic.

When no price per day shows ​

Commander shows no figure when it is not sure of the count. A missing line is better than a wrong price. Commander shows nothing when:

  • The variant title and the product facts state no count. A title such as "Starter kit" or "Bundle" gives Commander nothing to divide by.
  • A count is a range or a maximum, such as "1-2 capsules" or "up to 4 a day".
  • The dose is described in words Commander cannot read with certainty, such as "every other day".
  • Two places give different counts, or the count does not divide into days evenly.
  • The count is very large, as for a pack size, and not a supply.
  • The product facts give the total only as "servings per container" and the product has several variants. That total describes no single variant, so Commander does not use it.
  • A plan charges once for several deliveries, and neither your store nor your product page states how many deliveries one charge covers. Commander then does not know the price of one delivery.

The page is then complete without the line. The page does not show an error.

On the basic layout, a product with a very large number of variants gets a link to the product page in place of the purchase choices. That page has no price per day.

To get a price per day, state the count where Commander reads it:

  1. Open the product in Shopify admin.
  2. Put the count in each variant title, for example "60 capsules".
  3. State the daily dose and the serving size in the product facts.
  4. Generate the page. A page that already exists keeps what it was made with. Generating a page uses credits, and the dialog shows the cost.

Your product's name ​

When a page's text never states your product's title, Commander prints the title at the top of the buy box. It uses the title exactly as your store writes it. AI does not write this line, and it appears only in a buy box that Commander built for the page.

The mobile buy bar ​

On a phone, a bar sits at the bottom of the screen once the visitor scrolls past the top of the page and the buy box is out of sight. It shows the price, the selected purchase choice and a button.

  • The bar copies the price, the choice and the button words from the real buy box. It never shows anything the buy box does not.
  • Tapping the button presses the real Add to cart button. The variant, purchase choice, quantity and options the visitor picked are what is added, and your theme's own cart behaviour runs.
  • The bar hides while the buy box is on screen.
  • The bar does not appear on wider screens.
  • The bar does not appear on a page that has the sticky button at the bottom of the screen, so a phone never shows two bars. See A sticky button on long product pages.
  • The bar is part of the live page on your theme. The preview inside Commander does not show it, so you see the bar only after the page is live. Check it on your phone after you publish.

The price outside the buy box ​

A page can show the price of the buy box once more, in the line under the main heading and above the last button of the page, as a few words and the price. The words come from a short fixed list in the language of the page and name no plan, period, quantity or saving. The price is the one the buy box shows, copied from it. AI does not type it.

  • The line follows the visitor. When the visitor picks another purchase choice or variant in the buy box, the price in this line changes with it, so the page shows one price.
  • On the Full-width layout, the line appears once the page has loaded and the buy box has shown its price. Without scripts in the visitor's browser, the line stays hidden.
  • On the basic layout, the line shows the price Commander read when it wrote the page, and does not change with the visitor's choice.
  • The line never shows when a plan charges once for several deliveries. Commander then shows that charge in the buy box only.
  • Commander removes the line when the buy box cannot show a price of its own, for example when the page links to the product page in place of the purchase choices.

Whether a page carries the line is the choice of the AI that writes it. When it leaves the line out, the page is complete without it.

Nobody approves anything for these features. They come with the page when it has a buy box. You review the page as you do for any generated page.

Exact output ​

PartWhat it shows
Product nameYour product's title at the top of the buy box, when the page's text does not state it elsewhere.
Price per dayA figure under a purchase choice, such as the price followed by / day or / serving. The words follow the language of the page.
Mobile buy barA bar at the bottom of a phone screen with the price, the selected purchase choice and a button.
Price outside the buy boxA short line with a few words and the price, under the main heading and above the last button. It shows the same price as the buy box.

The bar's button uses the words of the real Add to cart button. It is disabled when that button is disabled, for example when the variant is sold out.

What to do with it ​

What you seeDecision or actionOwner
A price per day that looks rightNothing to do. Check it against your own arithmetic before you send ads to the page.ecommerce manager
No price per dayPut the count in the variant titles or the product facts, then generate the page again.ecommerce manager
A price per day that looks wrongCheck the variant title and the product facts, because Commander reads the count from them. Do not publish the page until they agree.ecommerce manager
The mobile buy barOpen the live page on a phone and check that it hides, shows and adds to cart.ecommerce manager
A price line outside the buy boxPick another purchase choice in the buy box and check that the line shows the same price as the box.ecommerce manager

Expected value and measurement ​

A price per day can make a larger pack easier to compare, and the bar keeps the button in reach on a phone. Neither is a promise of more sales.

To check, compare the conversion of the page with the same page before the change, in your own analytics, and compare mobile with desktop. You cannot isolate the effect when other changes, such as new ads, a new offer or a price change, ran at the same time.

Limitations and exceptions ​

  • The page is written by AI, and you must review it before you publish. The price per day is the exception to the rule that AI writes the numbers: it is calculated.
  • Commander reads the count when it writes the page. If you change a variant title afterwards, the count on the page stays as it was, and the figure can then be wrong. Generate the page again to read the new title.
  • On a full-width page the price comes from your live product. On the basic layout the price and the figure are the ones Commander read when it wrote the page, so a later price change does not reach them.
  • A price per day appears only for a purchase choice of a product page. A page for your brand alone has none.
  • The product name line needs a buy box that Commander built for the page. Any other page can go without your product's title if its text never states it, so read the page before you publish.
  • The mobile buy bar needs a page with a buy box, and it needs Theme Access. The basic layout has none.
  • The price outside the buy box needs a buy box that Commander built for the page. A page that links to the product page in place of the purchase choices has none, and neither does a plan that charges once for several deliveries.
  • The words before the price in that line come from a fixed list for each language. The page shows the price alone when the words are not on the list.
  • The line shows the price in the buy box and not the price per day. The price per day stays under the purchase choice.
  • The preview inside Commander never shows the bar, by design: the bar belongs to the live theme page. Publish the page, then open the live page on a phone.
  • The bar stays hidden when the browser cannot detect scrolling, and when it would cover too much of a small window, for example on a phone held sideways or with the text zoomed in. The visitor then uses the buy box.
  • The bar is part of how the live page is drawn. You cannot edit it, move it or remove it in the landing page editor. The sticky button is a different thing: it is a section of the page, and you can reword, hide or remove it in Sections.
  • In Demo Mode, the list shows fixed sample pages. Commander reads no store, so a sample says nothing about your own products. See Demo Mode.

Commander is built by Omniconvert.