MoneyLeak
Realistic example output (not customer data)

Example findings

Realistic example cases that show how Money Leak surfaces hidden revenue loss in ecommerce order data.

Open cases

6

High priority

2

Total estimated loss

81,850 DKK

Example findings

P1Actionable

Incorrect B2B pricing

A segment of B2B customers received lower prices than intended across multiple orders.

Estimated loss

22,400 DKK

Likely reason: Role-based pricing rules did not apply as expected.

Recommended action

Review role-based pricing setup and affected customer groups.

Ask the assistant

"What could have caused this pricing issue?"

P1Actionable

Legacy price logic still active

Older pricing conditions remained active after a commercial change.

Estimated loss

18,100 DKK

Likely reason: Outdated logic continued to affect selected orders.

Recommended action

Audit active pricing rules and remove outdated conditions.

Ask the assistant

"Which orders are still hitting the old logic?"

P2Actionable

Quantity pricing mismatch

Volume discounts were triggered outside the intended quantity thresholds.

Estimated loss

14,200 DKK

Likely reason: Quantity break logic did not match the intended commercial rules.

Recommended action

Review volume thresholds and affected SKUs.

Ask the assistant

"Which SKUs are affected by the threshold mismatch?"

P2Review

Promotion-led margin erosion

Campaign orders increased volume but reduced margin below acceptable levels.

Estimated loss

11,600 DKK

Likely reason: Discount and shipping logic interacted unfavorably.

Recommended action

Review campaign profitability and shipping thresholds.

Ask the assistant

"Which campaign window contributed most to margin loss?"

P2Actionable

Discount stacking error

Multiple discounts were applied together in a way that reduced margin more than expected.

Estimated loss

8,750 DKK

Likely reason: Coupon and campaign rules overlapped.

Recommended action

Review discount combinations and campaign logic.

Ask the assistant

"Which discount combinations should we review first?"

P3Review

Unusual order quantity pattern

Order quantities deviated from normal patterns and may indicate unit or packaging logic issues.

Estimated loss

6,800 DKK

Likely reason: Quantity assumptions or unit pricing may be incorrect.

Recommended action

Review affected SKUs, package sizes and order patterns.

Ask the assistant

"Why is this case marked for review?"

Want to see findings on your own data?

Request a leak analysis. We will walk you through what is hiding in your orders.

Request leak analysis

See what may be hiding in your orders.

Request leak analysis