Pricing and offer testing

Price is the most sensitive thing on your page and the one merchants worry about most. So here is the rule up front: Luria never changes a price on its own. Everything below fits inside that.

What Luria can test around price

There is a lot of room to improve how an offer lands without touching the number itself. These are the things Luria works on within your rules:

All of these are presentation. The visitor pays the same amount either way. Luria is finding the clearest way to say what you already offer.

What Luria will not do without your explicit approval

These are locked. Luria may suggest them in Approvals, with its reasoning, but nothing happens until you say yes.

• Change a price. Up or down, any product, any amount.
• Deepen a discount. No bigger percentages, no new codes, no extended sale windows.
• Add or change a claim. Nothing about what the product does, contains, or achieves.
• Break a constraint you set. Margin floors, never-discount items, and your do-not-say list are hard walls.

This holds even if a suggestion looks like an obvious win. The decision is yours, every time.

Set your offer constraints

Luria only knows your limits if you tell it. Set these during training and update them whenever they change. See How to train Luria.

• Margin floors. Per product or per collection: the minimum margin Luria must protect when it suggests bundles or discount presentation.
• Never-discount items. Products that never appear in a discount frame, never get a compare-at price, never go in a "save" bundle.
• Offer rules. Minimum order for free shipping, which codes exist, which bundles are real. Luria presents only offers you actually honor.
• Wording rules. Words you do not want near price ("cheap," "clearance," "lowest ever") go on your do-not-say list.

These live in your Brand Brain, apply to every page and every traffic source, and survive seasons; a BFCM event cannot override a never-discount item.

Approvals: how offer changes reach you

Anything that touches price, discount depth, or claims shows up in Approvals with:

• what the change is, side by side with the current version,
• why Luria is suggesting it (which traffic, what it has seen),
• what it expects to affect (conversion rate, order value, or both).

Approve, edit, or decline. Declined suggestions teach Luria what not to bring back. If you find yourself declining the same kind of suggestion twice, add it as a rule in training so it stops appearing.

Margin vs revenue: pick the goal on purpose

This is where offer testing gets real. A discount-forward presentation can raise conversion rate and revenue while lowering profit per order. A margin-protecting presentation can do the opposite. Neither is wrong; they are different goals, and Luria needs to know which one you want.

In Goals you choose what Luria optimizes toward. The rough tradeoff:

Set margin floors alongside a revenue goal and you get the best of both: Luria chases revenue but cannot cross your floor. Most merchants land here.

You can change the goal at any time. Give Luria a week or two after a switch before judging the new direction; your traffic decides the pace. See What to expect.

Common questions

Next steps

• Goals
• How to train Luria
• Approvals
• What Luria changes