Four
powersone companion

Meet Magento UK · Hackathon 2026

MMUK Scout

One natural-language bar over your Magento admin. Find anything, ask anything, and get the real reason behind any problem — plus the fix. No tickets, no tribal knowledge, no guesswork.

An AI companion for the Magento admin · The Mermaid, London · 7 July 2026

· MMUK
MMUK Scout01 / 16

Watch the demo

· MMUK
Demo video▶ Watch

The problem

The admin holds
every answer. It just
won't hand them over.

Every answer already lives in your Magento admin — but reaching it means knowing where to look and in what order. That knowledge is tribal. So the same frustration shows up four ways, every day, for everyone who touches the store.

Can't find it

"I know it's in here somewhere."

  • "open the UK store's shipping settings"
  • "go to SKU ABC-123"
  • "show order #100231"

Can't get an answer

"I just want a straight answer."

  • "how many orders are stuck in processing?"
  • "top sellers this week"
  • "is ABC-123 in stock anywhere?"

Can't work out why

"Enabled, in stock, still invisible."

  • "why isn't ABC-123 showing on the UK store?"
  • "why did order #100231 fail at payment?"
  • "why isn't SUMMER20 applying to this cart?"

Can't safely change it

"I daren't touch it."

  • "reindex prices"
  • "enable ABC-123 on the UK store"
  • "flush the full-page cache"

Four flavours of the same problem: the admin knows, but it won't tell you. Each one is a question with an answer already sitting in the store.

· MMUK
The problem02 / 16

The vision

One companion.
Four powers.

Turn each frustration into a power and you get Scout: a single natural-language bar over the whole admin. Four modes, ordered by power and risk — each built on the one before. Same four questions from a moment ago, now answered.

→

01 · Navigate · safe

Navigate

"open the UK store's shipping settings" — take me there. Any page, SKU, order or setting, in the right scope.

Take me there

→

02 · Ask · read

Ask

"how many orders are stuck in processing?" — tell me. Data questions and how-to, answered straight.

Tell me

→

03 · Diagnose · reason

Diagnose

"why isn't ABC-123 showing on the UK store?" — root cause across the whole cascade, plus the fix.

Why isn't this working

04 · Act · write

Act

"reindex prices" · "enable ABC-123 on UK" — do it. Permission-gated, approve before save.

Do it

They nest. Every diagnosis ends in a Navigate jump; every action starts from one — so the four share a single spine.

· MMUK
The vision03 / 16

The product

One bar.
Four powers.

You land not knowing what the user wants — so the four powers are the frame. Pick Diagnose and the panel becomes three worked examples, ready to run against the live store.

Landing
Four powers
Scout⤢✕

How can I help,
Kathryn?

Just say what you need — Scout works out which of its four powers to use.

UK website · EN store-view ▾
NavigateTake me there"Open the UK store's shipping settings"
AskTell meSoon"How many orders are stuck in processing?"
DiagnoseWhy isn't this working"Why isn't ABC-123 showing on the UK store?"
ActDo itSoon"Enable ABC-123 on the UK store"
Say what you need…
Press / to jump straight to a page↑
Scout reads your live store — verdicts, not guesses.
→tap Diagnose
Drilled in
Diagnose
Scout⤢✕
‹ All powers
Diagnose
Why isn't this working?

Pick something that should be live but isn't — or just describe the problem below.

ProductWhy isn't ABC-123 showing on the UK store?
PaymentWhy did order #100231 fail at payment?
PromotionWhy isn't SUMMER20 applying to this cart?
Why isn't…?
Scout walks the whole cascade↑
Three worked examples — or type your own.
· MMUK
The product04 / 16

The name & mark

Why Scout?

A scout goes on ahead, reads the terrain, and reports back exactly what's blocking the path — fast, light, precise. The mark says the same thing: a compass star with four points and one focal core.

Scout

Compass star · four points, one "you are here"

Four spikes, four powers

The mark's four points are Navigate, Ask, Diagnose and Act. The yellow core is "you are here" — the one thing worth looking at, and the fix at the end of it.

It reads the terrain

Point Scout at a product, an order or a payment and it walks the ground, then reports the blocker — a verdict, not raw data.

Short · quick · a verb

One syllable, always active: "Scout this product." It sounds like what it does, and sits naturally under the MMUK banner.

· MMUK
The name & mark05 / 16

Who's it for

It opens the
admin to everyone.

Scout collapses the escalation chain into a self-serve answer — meeting every skill level where they are, and freeing the experts to do expert work.

Merchants & owners

Non-technical. Ask "why isn't my product showing?" and get the fix — no ticket, no jargon.

The biggest unlock

Catalog & marketing admins

Live in "why isn't this promo / product live?" Skip the Stack Exchange detour.

Self-serve daily

Support & ops

Answer "why did this order fail?" on first contact, without escalating.

Fewer escalations

Junior devs & new starters

The diagnosis teaches the platform's rules. Ramp faster on the job.

Learns the platform

Senior devs & agencies

Scout absorbs the repetitive "did you reindex?" triage.

Protected focus time

A multi-person, multi-hour escalation becomes a ten-second, one-person answer.

· MMUK
Who's it for06 / 16

Where we focus first

Of the four,
one is the hard one.

Navigate, Ask and Act are real powers — but generic AI can fake them well enough to start. Diagnose is the one only deep Magento knowledge does right, and the one generic AI gets confidently wrong. So that's where our time goes. And because every diagnosis ends in a Navigate jump, we get Navigate almost for free — so that's what we're showing today.

Diagnose · our focus

The differentiator we're investing in. Deterministic cascades that kill the escalation chain — no generic AI can fake them. This is what we're proving today.

Navigate · rides for free

Every verdict deep-links to the exact fix — that link is Navigate. Built on Diagnose's spine, so we get it as upside.

Build the spine once for Diagnose, and Ask & Act inherit it next.

· MMUK
Where we focus first07 / 16

Why Diagnose is the hard one

"Why isn't this working?"
is a black hole.

Navigate, Ask and Act are tractable. This is the one that black-holes. A product's enabled, in stock, and live — still invisible — and the answer walks up an escalation chain nobody can short-circuit but the last person on it.

Merchant

"My product's gone. Is the site broken?" Raises a ticket.

→

Support

Checks the obvious, can't see it, escalates upward.

→

Junior dev

Clicks through scopes, tries a reindex, still stuck.

→

Senior dev

Knows the cascade by heart. Finds it in 30 seconds — hours later.

Hours

lost per incident to a question with a 10-second answer.

4 people

touch a problem only the last one could solve.

Tribal

the fix lives in one head, not in the product.

That chain is exactly what Diagnose replaces. Encode the senior dev's cascade once, and everyone gets the 30-second answer — instantly, first time.

· MMUK
Why Diagnose is hard08 / 16

How Diagnose works

Not a guess.
A checker.

The AI only reads intent and explains the result. The truth comes from a deterministic decision-tree that walks the real cascade, in order, at the right scope.

A generic AI alone

  • Reasons from training data, not your store's actual state
  • Invents a plausible cause — and is confidently wrong
  • Can't count, can't check an index, can't see store-view scope
  • Gives you a paragraph, not a fix

Scout's checker engine

  • Recognises intent → routes to the right checker
  • Walks encoded gates against live data, in the correct order
  • Scope-aware: default vs. website vs. store-view
  • Returns the first failing gate, the reason, and a one-click fix

"why / why isn't / how come" → Diagnose. The LLM narrates; the checker decides.

· MMUK
How it works09 / 16

Diagnose in action · the hero checker

Product visibility.

One question. Scout walks seven gates against the live store and stops at the culprit — then hands you the fix and the exact field to change.

"Why isn't ABC-123 showing on the UK store?" Scope · UK website / EN store-view
✓Status — EnabledEnabled at default & UK scope
✓Visibility — Catalog, SearchVisible individually
✓Website assignmentAssigned to UK website
✓Category assignmentIn 2 active categories
✕Stock & salabilityOut of stock · qty 0 · backorders off
–Price index rowNot reached
–Index & cache healthNot reached
Root cause: ABC-123 is out of stock, and "Display Out of Stock Products" is off — so Magento hides it from all listings on the UK store. Restock it, or enable that setting to keep it visible. Open stock settings

Seven checks, one verdict, zero escalation — and "Open stock settings" deep-links straight to the field, in scope. That link is Navigate, shared between the two.

· MMUK
Demo · visibility10 / 16

The engine scales

One engine.
Many checkers.

Diagnose isn't one feature — it's a framework. Each "why isn't X working?" is its own decision-tree plugged into the same engine. We ship visibility live; the rest slot in behind it.

Live

Product visibility

Why a product won't show on a store.

Next

Payment

Why a payment failed, was flagged, or a method's missing.

Soon

Promotion / price rule

Why a discount isn't applying to a cart.

Soon

Category

Why a category page is empty.

Soon

Order

Why an order is stuck or failed.

Soon

Search

Why a product isn't returned in search.

Soon

Customer pricing

Why a group/tier price isn't applied.

Soon

Index & cache health

Why recent changes aren't live yet.

The pitch isn't a checker. It's the framework that makes every checker cheap to add — encoding senior-dev knowledge once, for everyone.

· MMUK
Checker library11 / 16

Checker spotlight · beyond the catalog

Scout follows
the money.

Payment problems are the scariest and most escalated — a failed checkout is lost revenue right now. The same engine handles it, just a different cascade.

"Why did order #100231 fail at payment?" Scope · UK website · Card gateway
✓Method enabled for scopeActive on UK website
✓Order-total & currency limits£184 · GBP · within min/max
✓Country / customer-group rulesAllowed for GB, General
✕Gateway responseDeclined · AVS mismatch · fraud filter hit
–3-D Secure / captureNot reached
Root cause: the gateway declined on an AVS mismatch caught by your fraud filter — billing postcode didn't match the card. Not a config fault. 14 similar declines in 7 days — worth a filter review. View fraud filter rules

Same verdict shape as visibility — but now it separates "you misconfigured something" from "the customer's card was declined," which is exactly the distinction support can't make today.

· MMUK
Payment checker12 / 16

Shipping today · feature two

Navigate —
skip the menu tree.

The admin is a deep, scoped maze. Type what you want in plain English and jump straight to the page, product, order or setting — no hunting, no remembering paths.

▸where do I set up free shipping
SettingCart Price Rules · Stores ▸ Configuration ▸ Sales ▸ Shipping Methods ▸ Free ShippingJump ↵
SettingFlat Rate · Configuration ▸ Sales ▸ Shipping MethodsUK website
Guide"Free shipping over a threshold" · how-toDocs
RuleFREESHIP-75 · existing cart price ruleActive

Every result is scope-aware and deep-links to the exact screen — powered by the same links Diagnose emits. Build the spine once, ship two features.

· MMUK
Navigate13 / 16

Why now, why us

The pattern's proven.
Magento's gap isn't.

Shopify's Sidekick has shown merchants will talk to their admin. But it stops at analytics and form-filling — and it's blind to exactly what makes Magento hard.

Proven demand

Sidekick made "ask your admin" mainstream for Shopify merchants. The behaviour is established — the appetite is real.

The open gap

Sidekick answers data and fills forms. It doesn't diagnose a cascade — and Magento, not Shopify, is where the cascades are brutal.

Our edge

Magento-native and scope-aware. Sidekick is one-store; Scout reasons across website / store-view — the thing Magento needs and Sidekick structurally can't do.

We're not copying Sidekick. We're building the part it skipped — for the platform that needs it most.

· MMUK
Why now, why us14 / 16

Roadmap

Two today.
The companion after.

Honest scope: today we ship Diagnose and Navigate on a shared spine. Everything else sequences off that same foundation.

Now · hackathon

Diagnose + Navigate

  • Product-visibility checker, live & scope-aware
  • Payment checker as the second cascade
  • Natural-language Navigate command bar
  • Verdict + fix + deep-link, shared across both

Next

Ask

  • Data questions — "top sellers this week"
  • How-to answers grounded in the docs
  • Number + chart + source, on the same spine

Later

Act · Proactive

  • Act — reindex, cache, bulk edits, permission-gated
  • Proactive — Scout flags issues before you ask
  • More checkers: promo, category, order, search
· MMUK
Roadmap15 / 16

The one line

Stop asking why.
Start knowing.

MMUK Scout turns the admin's hardest question into a ten-second answer — and encodes the knowledge that used to live in one senior developer's head into a product anyone can use.

Diagnose + Navigate · live today Ask → Act → Proactive · the roadmap
· MMUK · Meet Magento UK 2026
Thank you16 / 16