كل المقالات
croab-testingecommercesalla

Free Shipping Threshold: How to Test Your Way to the Right Number

Free shipping threshold optimization without losing money. The margin-vs-AOV tradeoff, the testing method, and Salla and Shopify-specific guidance.

5 مايو 2026

Most stores set their free shipping threshold by copying a competitor or rounding to a nice number. 200 SAR. 250. 300. None of those are necessarily wrong — but none of them are right for your store either, because nobody tested them on your traffic, your products, your margins.

Free shipping threshold optimization is one of the highest-leverage tests an e-commerce store can run. Move the number up by 30 SAR and you might lift average order value by 8% without losing customers. Move it the wrong way and you bleed margin without seeing AOV move at all. The only way to know which direction is yours is to test.

The trade-off in plain numbers

Every threshold sits between two costs. A low threshold (or no threshold at all) means you eat shipping on most orders — a direct hit to margin. A high threshold means fewer shoppers qualify, fewer feel pushed to add the extra item, and conversion can dip.

The sweet spot depends on three numbers about your store:

  • Current AOV — what's your average order value today?
  • Shipping cost per order — what does it actually cost you to fulfill a Saudi domestic delivery? UAE? GCC?
  • Margin per order — what's left after product cost, payment fees, and shipping?

The standard advice is to set the threshold at roughly 130–145% of current AOV. If your AOV is 180 SAR, that means a threshold somewhere between 235 and 260. The logic: low enough that shoppers feel they can reach it with one more item, high enough to actually shift behavior. But standard advice is a starting point, not an answer.

Why testing matters more than the formula

The 130-145% rule assumes shoppers respond to thresholds the same way everywhere. They don't. A fragrance store sees different behavior than a home goods store. A 30 SAR shipping fee feels different in Riyadh than in Jeddah where COD is more common.

Three stores in the same niche, with similar AOVs, will have three different optimal thresholds. The only reliable way to find yours is to test, not to copy.

We've seen stores assume the formula and ship a threshold that lifted AOV by 4% — only to find on testing that a slightly higher number lifted it by 11% with the same conversion rate. That extra 7% on every order, every day, compounds fast.

How to set up the test on Salla and Shopify

Both Salla and Shopify let you set free shipping rules, but neither has native A/B testing for them. The clean way to run this test is to split traffic at the platform level — half see threshold A, half see threshold B — and measure both AOV and total revenue per visitor.

Watch out for a common mistake: measuring only AOV. A higher threshold can lift AOV while dropping the number of orders, and your total revenue stays flat or falls. The metric that matters is revenue per visitor, not AOV alone.

The setup looks like this:

  1. Pick three threshold candidates — current, current +20%, current +35%. Three is plenty; don't over-test.
  2. Run the test for at least three full weeks to capture different campaign cycles and salary weeks.
  3. Track all three metrics: conversion rate, AOV, and revenue per visitor.
  4. Don't change anything else during the test — no new ads, no homepage redesigns, no product launches that skew AOV.

For the broader walkthrough on running a test cleanly, see how to run an A/B test on a Salla store — the same setup pattern applies here, just with the threshold as the variant.

The math problem most stores get wrong

Stores often calculate threshold ROI based on the lift in AOV from buyers who would have bought anyway. That's the wrong base. The real question is: of the shoppers who saw the threshold, how many added an item they wouldn't have, and what did that item cost you?

An example. Your AOV was 180 SAR. You raised the threshold to 250. Buyers who bought 230 worth of items added one 25 SAR product to qualify, bringing their order to 255. The lift looks great — until you remember that the 25 SAR add-on item probably has lower margin than your average product (it's an impulse fit, not a hero product), and you're now eating shipping on the 255 order anyway.

The honest calculation is: incremental revenue from threshold-prompted adds, minus product cost on those adds, minus shipping cost (since you still pay it), minus payment fees on the higher total. Sometimes the threshold that maximizes AOV is not the one that maximizes margin. Both are valid choices, but you should make the choice deliberately.

An easy sanity check after the test: pull the orders whose value landed between the old threshold and the new one. Look at the invoices. Are the added items the same mix as your core catalog, or are they noticeably cheaper? If they're cheaper, you lifted AOV but paid an invisible cost that won't show up in your dashboard's headline number.

Special cases for MENA stores

A few patterns specific to MENA worth keeping in mind:

  • COD orders fail more. If you offer cash on delivery, your free shipping threshold should account for the fact that 5–15% of those orders will be returned undelivered. A higher threshold concentrates this risk.
  • Cross-border (GCC shipping) is its own problem. If you ship from KSA to UAE or Kuwait, the threshold for those orders should usually be different — and most stores forget to set it separately. Salla supports per-country shipping rules; use them.
  • Tabby and Tamara complicate the math. Buy-now-pay-later splits the perceived cost across installments, and the urgency to hit a threshold drops. Some stores find their threshold needs to be lower for BNPL shoppers than for upfront payers.

Next steps

Pull your AOV from the last 60 days. Calculate your true shipping and margin per order. Pick three threshold candidates around the 130-145% range and run them as a three-way test for at least three weeks. Track revenue per visitor as the deciding metric, not AOV. The right threshold is rarely the one that sounds nicest — it's the one your data picks.