Build Your Average Order Value Stack in Merchant with AI
Have the AI read your real order data, then configure frequently bought together, spending goal, and volume discounts as one system instead of three unrelated settings.
Prerequisites
Merchant Pro with WooCommerce on a connected site, and enough completed orders for an average to mean something. Turn on AI write access under Merchant > Global Settings, in the WPVibe panel.
My store runs WooCommerce with Merchant Pro. Discover Merchant's abilities first. I want to raise my average order value. Read my data before you configure anything, and keep reading and building as two separate steps. Step 1, read only. Pull my completed WooCommerce orders for [the last 90 days] and tell me my current average order value, the distribution of order totals, and which products are most often bought together. Then run merchant/get-analytics at global scope, and at module scope for any of these modules that is already active. Show me the numbers before you propose anything. Step 2, propose. Recommend a configuration for three Merchant modules as one system: - frequently-bought-together: which products to pair, based on what my orders actually show. - spending-goal: the free shipping or reward threshold, set from my order distribution rather than a round number. Tell me which percentile you picked and why. - volume-discounts: the quantity breaks and the discount at each one. Set every threshold from a number in my store and say which number it came from. Check the three against each other and stop to ask me when two settings pull in opposite directions, for example a spending goal threshold that a volume discount makes unreachable. Wait for my go-ahead. Step 3, build. Run merchant/get-module-settings with include_schema=true on each module before writing to it, then apply the configuration. When you are done, list every setting you changed with its previous value, and restate the baseline average order value you measured in step 1 so I have a before and after to judge this against.
Skip pasting the full prompt. Drop this into your AI on a site that already has WPVibe:
Run the “Build Your Average Order Value Stack in Merchant with AI” recipe from the WPVibe cookbook on my connected site.
Frequently bought together, a spending goal, and volume discounts all raise average order value, and configuring them one at a time is how they end up fighting each other. A free shipping threshold set at a round $50 when your median order is $31 gets ignored, and a volume discount that pushes orders just under that threshold cancels the goal it was meant to support. The numbers that would settle all three sit in your order history, which nobody opens before filling in a settings screen.
The AI reads the order data first and sets each threshold from a number in your store rather than a round figure, telling you which number it came from. It then builds the three modules as a set, checks them against each other, and stops to ask when two settings pull in opposite directions. Reading and building stay separate steps on purpose, because these modules change what customers actually pay.
Read the plan before approving it, and check the numbers behind each threshold rather than the thresholds themselves. If the recommendations come back as round figures with no reference to your actual orders, that usually means there is not enough order history to work from yet, and it is worth waiting rather than shipping it. Write down the baseline average order value the AI reports in step one, since a stack like this is only judgeable against a before and after.
Outcome
Frequently bought together, spending goal, and volume discounts configured as one coherent system from your own order data, with a recorded baseline average order value to measure against.