The platform
The spine is the product and the mental model. Each pillar is a real surface your merchants work inside, not a slide. Start with one, expand from there.
Plan
Plan sets the financial frame and the open-to-buy. Top-down targets meet bottom-up reality, and the OTB recalculates as actuals land, not three weeks later in a spreadsheet someone forgot to refresh.
See Plan in the platform →| Category | Plan | Actual | OTB open |
|---|---|---|---|
| Womens | 4.20M | 3.94M | +0.31M |
| Mens | 2.85M | 2.91M | −0.06M |
| Accessories | 1.10M | 1.18M | −0.12M |
OTB recalculated on last night’s sell-through. Illustrative.
Buy
Buy builds the order, not a hint about it. Range architecture, drops, MOQ and lead time resolve into a store-level buy plan you can edit inline, with the reasoning on every line.
See Buy in the platform →| Attr group | Drop 1 | Drop 2 | Options |
|---|---|---|---|
| Denim / slim | 200 | 80 | 10 → 5 |
| Knit / crew | 120 | 60 | 6 → 4 |
| Tee / graphic | 210 | 70 | 7 → 7 |
Buy plan across drops, store-style level. Illustrative.
Allocate
Allocate places stock at store-SKU level and rebalances as demand moves. It kills the grunt-work of pulling reports. It is the most automatable workflow and the quickest to show value day to day, which is why we usually start a pilot here.
See Allocate in the platform →| Store | On hand | Cover | Move |
|---|---|---|---|
| DXB-014 | 38 | 6d | +12 |
| AUH-006 | 71 | 21d | −16 |
| KWI-002 | 12 | 3d | +20 |
Store-SKU rebalance within your ±guardrail. Illustrative.
Sell
Sell manages in-season replenishment and markdown timing. It watches true rate-of-sale, not broken-size noise, and proposes the reorder or the markdown at the moment that protects the most margin.
See Sell in the platform →| Style | ROS/day | Sell-thru | Call |
|---|---|---|---|
| SW-2241 | 4.1 | 62% | Reorder |
| SW-1108 | 0.6 | 28% | Mark −20% |
| SW-3390 | 2.7 | 54% | Hold |
Replenish / markdown timing on true ROS. Illustrative.
Analyze
Analyze is the metric tree your merchants already think in. Sell-through, GMROI, turn, markdown, OTB, on-shelf availability. No export to a BI tool, no chart to decode. The numbers come to the decision.
See Analyze in the platform →| Metric | Now | Plan | Δ |
|---|---|---|---|
| GMROI | 3.1 | 2.8 | +0.3 |
| Sell-through | 58% | 61% | −3pt |
| Stock turn | 4.6 | 4.2 | +0.4 |
The metric tree, live. Illustrative.
Decide
Decide is where MEGA acts within your guardrails, traces every action, and graduates from suggest to execute as the calls prove out. Every decision is explainable, approvable, overridable, and logged.
See Decide in the platform →| Action | Guardrail | Status | Projected |
|---|---|---|---|
| Cut WMN receipts 8% | ±10% | Needs you | +1.4pt mgn |
| Rebalance AUH→KWI | ±20% | Approved | +0.6pt avail |
| Markdown SW-1108 | timing | Sent back | pending |
Decision trace. Projected deltas, on your data. Illustrative.
How it acts
The buyer-recognized ladder runs chatbot, recommendation, execute-in-guardrails, full autonomy. We claim the third rung, execute-within-guardrails on narrow, measurable wedges, and we refuse the one above it. The refusal is the point.
Answers questions about a dashboard. Most "AI" in this category stops here.
Surfaces a suggestion. A human still does the work. Where the specialty tools sit.
Takes the typed action inside bounds you set, traced and reversible. Where MEGA sits, on narrow measurable wedges.
A hands-off supply chain. We do not claim this. Industry analysts, Gartner among them, have cautioned that fully autonomous supply chains are years out.
You set the ceiling
Autonomy is earned. It starts at suggest and graduates as the calls prove out. You set the ceiling.
Integration and data
A widely cited 2024 MIT study put roughly 95% of enterprise AI pilots in the failure column. In our experience the cause is usually integration and data, not the model. Here is exactly what connects, what the first 30 days require, and what your IT actually has to provide.
What your IT provides: read access in your own cloud, and a named data owner. That is the ask.
Phase 1, not a platform bet
Pick the workflow that hurts most, usually Allocate or OTB. We run MEGA alongside your current process, on your data, in your cloud, on pre-negotiated terms. Day 30 you are configured. Day 90 you see modeled lift on the one KPI you chose, measured against your own baseline.
Day 30 configured · Day 90 modeled lift on your chosen KPI · measured on your own data
