| Date | Product | Type | Price Change | Margin | Outcome |
|---|---|---|---|---|---|
| Mar 26 | Sony WH-1000XM5 | AI Recommendation | €349.00→€339.00 | 22.4% | +€1,840 revenue, week after |
| Mar 24 | Galaxy Buds3 Pro | Manual | €219.00→€229.00 | 31.2% | +4% revenue, week after |
| Mar 22 | AirPods Max | Autopilot | €585.00→€579.00 | 18.7% | No clear change |
| Mar 20 | JBL Tour One M2 | AI Recommendation | €289.00→€279.00 | 25.1% | +9% units sold, week after |
| Mar 18 | Bose QC Ultra | Manual | €399.00→€389.00 | 19.8% | −6% revenue, week after |
Most teams change prices blind
Without outcome tracking, pricing teams cannot learn from past decisions. Mistakes repeat, patterns go unnoticed and the strategy is hard to justify to leadership.
- No way to tell whether a price change helped or hurt
- Leadership asks what a price change achieved and there is no answer
- The same mistakes repeated because there is no feedback loop
- No record of who changed a price, or why
- No structured data for comparing pricing approaches
How Luska tracks pricing impact
A decision log for every price change, and a before-and-after comparison wherever sales data is available.
Decision history
Each price change is recorded with the old and new price, who approved it and when, and the recommendation text and confidence behind it.
Before and after
Between 7 and 30 days after a change, Luska compares revenue and units sold in the 7 days before with the 7 days after. This needs sales data, imported by CSV, entered by hand or sent through the API.
Outcome score
Each measured decision gets a score from the revenue and unit changes, shown in the decision history and on the product page.
Expected impact up front
Before applying a recommendation, the impact preview shows the margin before and after and an estimated range for the revenue change.
CSV export
Export the decision history to CSV for leadership reviews or your own analysis.
Key Benefits
Frequently Asked Questions
How does Luska measure the impact of a price change?
For changes made 7 to 30 days ago, Luska compares revenue and units sold in the 7 days before with the 7 days after, and turns the difference into a score. Without sales data there is nothing to compare, and the decision is marked as not measurable.
Can I export the decision history?
Yes, as CSV. It includes the old and new price, who approved the change and when, and the recommendation behind it.
Does it account for other things that changed at the same time?
No. The comparison is a simple before-and-after on your own sales, so seasonality, promotions or competitor moves in the same week also show up in the result. Treat the score as a guide, not proof.
How far back does the history go?
Decision history is kept for as long as your account is active.