How to Increase Average Order Value on Shopify
Average order value is a useful starting point for understanding basket size, but it is not a goal that should be pursued independently of margin, returns or conversion. A larger order can cost more to fulfill, require a costly discount or replace several purchases a customer would otherwise have made. Begin with a diagnosis before adding another promotion.

Average order value is a useful starting point for understanding basket size, but it is not a goal that should be pursued independently of margin, returns or conversion. A larger order can cost more to fulfill, require a costly discount or replace several purchases a customer would otherwise have made. Begin with a diagnosis before adding another promotion.
This guide explains how to identify useful offer opportunities and evaluate them without promising a revenue increase. FairRev's verified development example is a product-page accessory add-on. Other feature journeys still need complete demonstrations. The examples here are hypothetical decision exercises, not merchant results.
Establish your current average order value and basket size
Define average order value as the revenue measure you choose divided by the number of eligible orders in the same period. Document whether that revenue includes shipping, tax, discounts and refunds, and which orders are excluded. A metric is only comparable when the definition remains consistent.
Use complete periods that suit the purchase cycle. Avoid comparing a short promotion day with an ordinary full month and treating the difference as an offer effect. Note changes in product mix, traffic source, prices, seasonality and inventory. Those changes can move average order value without any contribution from an upsell.
Measure items per order separately. A store can increase average order value by selling a more expensive main item while basket quantity stays flat. It can also sell more units at a discount and leave revenue or contribution unchanged. The two measures answer different questions about shopper behavior.
For a hypothetical baseline, suppose a store records 100 eligible orders and 8,000 USD of consistently defined net product revenue. Its average is 80 USD. If those orders contain 140 units, items per order is 1.4. These are arithmetic examples, not forecasts or FairRev results. Their value is the explicit denominator and scope, not the size of either number.
Keep the calculation reproducible. Save the period, filters, currency and definition beside the result. If returns arrive later, decide whether to restate the period or report both initial and settled views. Do not compare an unadjusted sales total with a refund-adjusted total under the same label.
Diagnose single-item baskets and missing related products
Review single-item orders by product and context. Some products are naturally complete purchases. A replacement part, a high-value item or a consumable refill may not need a companion. A single-item basket is a clue, not proof that the merchant failed to cross-sell.
Look for a practical omission. Does the main product require an accessory that is difficult to find? Is a compatible consumable useful soon after purchase? Does the product page explain what is included? Improving those details can be more helpful than adding a discount prompt to every template.
Inspect a sample of shopper journeys and support questions where evidence is available. Separate customers who could benefit from another item from customers who are simply completing the intended purchase. Do not infer motives solely from order totals. If research or session evidence is unavailable, label the explanation as a hypothesis to test.
Prioritize opportunities by relevance, operational cost and ease of verification. An accessory with a clear fit and predictable stock is easier to support than a complex group with ambiguous variants. Consider the effect on picking and returns before deciding that the largest possible basket is desirable.
Write one testable problem statement. For example: shoppers buying this main item may overlook a compatible companion because it is not shown in the purchase journey. That statement points to an offer and an observation. A vague target such as make everyone spend more does not tell the merchant what to build or how to judge it.
Choose relevant upsells and cross-sells
An upsell usually offers a more valuable version; a cross-sell adds a related product. Choose according to the problem you identified. If the customer needs more capacity, explain the upgrade. If the main item needs a companion, explain the relationship. Avoid disguising an unrelated product as a necessary accessory.
Evaluate a Shopify upsell app by the actual flow it supports. Can the shopper identify the item and variant? Does acceptance replace or add something? Can the customer decline and continue? Does checkout honor the displayed amount? Those questions matter more than a broad feature count.
FairRev's recorded development-store example offers selected ski wax beside a snowboard. It demonstrates a manually chosen catalogue add-on, not a personalized purchase-history recommendation or a replacement upsell. For related products, review the Shopify cross sell app evidence and its limits before using the workflow publicly.
Keep the message concrete. State the product, quantity, compatibility and final price. If a saving is shown, the shopper should understand its basis. A prompt that needs several qualifications is a sign to simplify the offer or move it to a more suitable point in the journey.
Start with one relevant offer so its behavior can be checked. Showing many competing suggestions can obscure the original product decision. Watch rejection, cart changes and support questions as well as acceptance. A suggestion that customers accept accidentally is not a successful customer experience even if it initially raises the basket total.
Use bundles and quantity discounts where appropriate
A fixed set can reduce the effort of finding complementary products. A quantity discount can make a larger purchase attractive when the customer actually needs more units. These are different mechanisms and should be evaluated separately.
A Shopify product bundle app should make the component list, variants, quantities and pricing clear. Decide whether you need a native bundle product or a grouped offer added to a cart. Do not assume the inventory and fulfillment behavior are identical. The free native Shopify Bundles option can be sufficient for a fixed bundle requirement.
A Shopify volume discount app needs explicit threshold semantics. Does the discount apply to every unit, reward units or only units above the threshold? What happens when the shopper reduces quantity? A buy more save more headline cannot answer those questions by itself.
Use hypothetical contribution calculations before a test. If the extra units create revenue but the incentive consumes their contribution, the higher average order value is not an economic improvement. Include additional packing, shipping and likely returns. A larger basket can also change future purchase timing, which is another reason to avoid equating the immediate basket with lasting incremental revenue.
FairRev contains fixed-bundle and quantity-tier configuration, but complete shopper walkthroughs remain missing. Quantity-tier display and acceptance also need reconciliation with the Function result. Ask for an end-to-end demonstration before choosing either FairRev workflow. A list of possible ways to increase basket size does not establish that a particular app supports every method.
Consider free gifts and Buy X get Y offers
A gift can make a qualifying purchase feel more useful, while a Buy X get Y rule rewards a specified quantity or product combination. Both can create extra operational cost and confused expectations if the condition is unclear. Define the rule before choosing the incentive.
For free gift with purchase Shopify promotions, state the exact gift and how it is claimed. Merchant-selected variants are different from a shopper reward selector. Automatic insertion and removal are separate capabilities that must be demonstrated. Test the cart after qualification changes rather than assuming the original reward remains valid.
A Shopify Buy X get Y app needs a clear distinction between qualifying and reward units. Not every BOGO variation is the same. Check repeated rewards, mixed variants, an existing reward item and a quantity below the threshold. Those boundary cases determine what a promotion actually promises.
Consider cost and relevance together. A gift with a high catalogue price may have a low merchant cost, but it can still be irrelevant to the purchase. Conversely, a modest useful companion may be more understandable without a dramatic savings claim. Use actual costs and customer evidence where available.
Do not assume the whole qualifying basket is attributed to a gift. Under FairRev's matching rule, a zero-priced gift line has zero item revenue itself. A promotion's business effect requires separate measurement. A compelling gift headline cannot supply the missing counterfactual of what the customer would have purchased anyway.
Measure offer acceptance, items per order and margin
Define acceptance with a clear denominator. An acceptance rate based on eligible offer impressions is different from one based on all site visits or all orders. Decide how repeat impressions and repeated clicks are counted. A reporting label without that definition is difficult to compare across tools.
Track the funnel from an eligible interaction to the added item and completed order when those events are available. A click can fail to add a line, an added line can be removed and an order can later be refunded. Report those as distinct stages instead of treating the earliest event as a sale.
Compare items per order, average order value and contribution using consistent scopes. Include the offer discount, gift cost, variable fulfillment, returns and app fee. If product costs are missing, say margin is unavailable rather than treating revenue as profit. Missing data is a measurement gap, not a favorable result.
Watch the cost of supporting the offer. Reconciliation failures, billing questions, incorrect variants and drawer refresh problems create work even when the dashboard shows acceptance. Retention and support burden help determine whether the workflow is useful to merchants over time.
Keep website acquisition metrics separate from app and storefront metrics. A website visit, an App Store listing visit, an installation, a published offer and a shopper acceptance describe different people and stages. Do not combine them into one conversion number without a documented connection. If source attribution between stages is missing, record the missing integration.
Separate attributed revenue from incremental lift
Attributed revenue is revenue assigned under a rule. A controlled comparison estimates what changed because an offer was shown. Those are different questions. A customer can accept an offer for an item they would otherwise have found and bought, so a correctly attributed item is not automatically an additional sale.
Use a suitable comparison design if the store has enough data and the test is appropriate. Keep groups comparable, state what differs and preserve the metric definitions. Small samples can produce noisy or negative differences. Do not hide that uncertainty or use an early favorable result as a guaranteed effect.
FairRev's attribution is used for billing and order explanation. Its control-group infrastructure is a separate area, not evidence that every merchant currently has a complete controlled experiment running. Review revenue verification for the distinction and the checks needed to reconcile charges.
Use a practical decision at the end of the test: keep an offer that is relevant, repeatable and economically justified; revise one with an understandable problem; remove one that creates confusion or unacceptable cost. The decision should use the observed journey and the available evidence, not a promise that every store ought to increase average order value by a particular amount.
Begin with a period of baseline collection and a clearly defined offer test. Later reviews should assess shopper relevance, contribution, returns and support questions using the same definitions. A review date is a decision checkpoint, not a prediction that the offer will increase revenue. Keep or change the promotion according to the evidence available from your own store.


