Lulu Hypermarket

Lulu Retail Holdings

AI Operating System

DeployOne
Viewing as

Operating scope

Country head

Capability

All capabilities

Active handovers

0

Outcomes written back

0

Information density is explain.

MarginOS · screen 01 of 07

Price position by category

Where we sit against the market, by category and country, weekly.

3 issues · 3 waiting on you

Issues in scope

3

3 instances across 3 places

Waiting on you

3

0 already decided in this session

Three largest

AED 13.0m–AED 39.6m

Modelled annual value, three largest only

Running without asking

0

0 armed and waiting on a threshold

Decision owner

Country head

Returns to Pricing desk, Finance

Scope

Oman

27 stores · all capabilities

Listen

Competitor price feedsOwn price and marginCategory and country

Process

Position by category, not by lineMargin floor before any matchVisible lines matter more than the tail

Act

Weekly pack to the pricing deskResponse chosen by a personFloor confirmed with finance
Written backEvery outcome returns to the systems that produced the evidence.
KindOrder

Queue

3 issues · 3 waiting on you
Approve

Price decisions are being taken on a position up to four weeks old

Jaber Al Ahmad
What happened
The position pack is monthly. Competitor pricing in electronics moves weekly and sometimes faster during promotional windows.
Why it matters
A monthly cycle means every decision in the second half of the month runs on stale data, and the decisions taken look reasonable on paper while being wrong in the market. Moving to weekly costs nothing beyond the routing.
Already done
The computation already runs weekly. Only the routing is monthly.
Worth
AED 6.5m to AED 19.4m a yearModelledHalf of every month's decisions running on data up to four weeks old. Value is the decisions taken on a current position instead.Age of position at decision
Then what
Weekly routing switched onPricing deskReports back 23 Sept
If approved
The position pack routes weekly to the pricing desk
If declined
It stays monthly and half of every month's decisions run on data up to four weeks old
GroupMarginOSDeployOneSenseDeployOnePredictDeployOneDash
Question

There is no margin floor above which a match happens without a meeting

Xpress, Al Raffa
What happened
Every match currently requires a decision, including matches that are obviously inside our margin tolerance. The floor is a finance parameter and has never been set.
Why it matters
Without a floor, the pricing desk spends its time on decisions that do not need judgement and arrives late on the ones that do. With one, the exceptions are the only thing on the desk.
Already done
The distribution of margin headroom across tracked lines is prepared so the floor can be set against real data.
Worth
AED 4.6m to AED 14.3m a yearModelledA margin floor removes the decisions that do not need judgement. Value is pricing desk capacity moved to the exceptions.Matches requiring a meeting
Then what
Floor set and applied, exceptions only to the deskFinanceReports back 26 Sept
GroupMarginOSDeployOneSenseDeployOnePredictDeployOneDash
Choose

Electronics sits above market on 20% of tracked lines while grocery sits at or below on 89%

Oman
What happened
These are two completely different competitive positions inside one business, in one country, and they are currently managed on one cycle with one approach.
Why it matters
Grocery is doing its job on price. Electronics is where we are visibly expensive on the lines customers check, and those are the lines that set whether a customer believes the rest of the store is expensive too.
Already done
The two positions are computed and held separately so the response can differ, with the visible lines identified inside electronics.
Worth
AED 1.9m to AED 6.0m a yearModelledTwo competitive positions inside one business managed on one cycle. Value is the margin and volume at stake on the visible electronics lines.Electronics lines above market
Then what
Response recorded per category, lines updatedPricing deskReports back 23 Sept
Country headMarginOSDeployOneSenseDeployOnePredictDeployOneDash