AGENTIC COMMERCE

Meet Mercury

The Agentic Operating System for Retail

Book a Demo
AqueriusMERCURY
Footwear Retail
—Project
Q3 Planning⌄
KKyle⌄
«
Ops & Planning⌄
Demand · Inventory · Fulfillment
What's New
Decisions
Conversations
Timeline
Trends
Planning Workbench
Inventory Health
Fulfillment
Returns
Suppliers
Open-to-Buy
What's NewOps & Planning
What's on your mind today⟳ Briefing updated just now
Friday, July 31, 2026
☆ AI Briefing
Hey Kyle! Demand forecast accuracy is holding at 87.4% (WMAPE 13.7%, target <15%) — nice work. I've flagged 5 critical issues I think you'll want to address today: 4 SKUs are at critical ATP risk (Trail Runner — Series A has just 7 days of cover) and 1 supplier delay is now threatening peak-season readiness, which sits at 82% with 38 days to go. Fill rate slipped to 96.2% (target 97%) — Carrier SLA at 83.2% is the main drag. Want me to draft the 3 PO expedition requests?
Page-0 Metrics
Forecast Accuracy
87.4%
↗ +2.1pp
WMAPE target <15%
Open POs
23
↘ −5 this wk
3 critical
Peak Season Readiness
82%
— 38d to go
3 POs need expedition
ATP Risk SKUs
4
⚠ Critical
Reorder now
NPI On-Track
3 / 4
⚠ 1 at risk
Artwork pending
Forecast Accuracy (WMAPE) — 10-Week
90%85%80%75%
87.4%
target 85%
W1W2W3W4W5W6W7W8W9W10
Inventory by Category (Weeks of Cover)
Supply & Demand Decisions
Planning inbox: 4 ATP risk alerts (Trail Runner at 7 days cover), 1 NPI risk flag, 2 PO expedition requests, and 1 S&OP budget variance.
RFP: Team Footwear for 2027
Cambridge Public Schools, Region New England-CAM2. 200 Units Requested (3 SKUs). Response Required.
● HIGH›
SKU-4821 Stock Out in 6 Days
12 Units Left. Daily Velocity of 2/Day. Lead Time is 15 Days, Reorder Window...
● CRITICAL›
Competitor Footsy Lowers Price by 18%. Buy Box at Risk.
Pricing Agent has flagged a shift in 3 SKUS that directly compete with our...
● HIGH›
Live context · Q3 Planning
Can you highlight the critical issues I need to address before peak season?
K
Kyle · 8:42 AM
✦Ask Mercury
On it, Kyle. With 38 days to peak, here are the 5 critical issues that need a decision — ranked by time-to-impact:
1
Series A Trail Runner: Near StockoutCRITICAL
ATP at just 7 days of cover heading into peak. No expedite request open yet.
2
SKU-4821 Stock Out in 6 DaysCRITICAL
12 units left at 2.0/day, but 15-day lead time — reorder window is effectively closed.
3
Supplier Delay Hits Peak Readiness in PNWHIGH
Inbound delay drops readiness to 82%. 3 POs need expedition to recover.
4
Fill Rate Slipped Below TargetHIGH
96.2% vs 97% target. Carrier SLA at 83.2% is the main drag.
5
NPI Artwork Pending: 1/34 At RiskHIGH
3 of 4 on track; 1 blocked on artwork, risking the launch window.
Mercury Recommends: 2 Stockout Risks + 1 Supplier Delay are the peak blockers. I can draft the 3 PO Expedition Requests for you.
Yes, Draft Them!
Open Planning Workbench
Snooze
Sourced from Social Listening & Search Trends·Sources↗
Ask Mercury about demand, inventory, or suppliers...→

THE CHALLENGE

What Retail Finds Challenging

The Cold Start Problem

Demand forecasting typically relies on historical sales, yet new products, emerging categories, and market expansion require decisions before a directly comparable record exists. Retail teams must assess likely demand using evidence from analogous products, customer behavior, and broader market conditions, while accounting for the uncertainty inherent in a new offering.

Fragmented Context

Retail data is distributed across commerce platforms, planning systems, marketing channels, and supplier networks, each with its own definitions and reporting cycles. Bringing these sources together requires more than consolidation. Teams need a consistent understanding of how products, customers, inventory, and commercial activity relate to one another before that information can reliably inform decisions.

Decisions Travel Across Functions

Retail decisions are interdependent, with changes in merchandising, pricing, or promotions carrying implications for inventory allocation, supplier commitments, and financial performance. Coordinating these decisions requires teams and external partners to work from shared assumptions and understand how changes within one function affect the plans and constraints of another.

Signals Outpace Interpretation

Retailers have access to a growing volume of demand signals, from transaction data and customer feedback to creator activity and social engagement. Interpreting these signals requires an understanding of their relevance to a particular assortment, audience, and planning horizon. A surge in attention may warrant investigation, but it does not necessarily indicate sustained demand or justify a change in commercial strategy.

Peaks Put Plans Under Pressure

Peak trading periods, promotional events, and major launches concentrate commercial activity into short execution windows. Although preparation begins months in advance, teams must continually reconcile actual demand, inventory availability, and supplier performance against their plans. Fragmented information and manual coordination limit how quickly they can respond, particularly when an adjustment requires action across several functions.

THE SOLUTION

How Mercury Helps

An Agentic Operating System

Mercury operates autonomously across connected retail processes, maintaining context as business conditions evolve. Aquerius Agents monitor developments, coordinate interdependent tasks, and carry decisions forward within defined permissions and approval requirements. Temporal reasoning allows the system to account for prior decisions, current conditions, and future commitments when determining what needs to happen next.

Channel Intelligence in Context

Mercury brings together signals from commerce channels and social media to evaluate emerging interest in relation to the retailer’s products and existing demand patterns. Teams can assess where channels reinforce or contradict one another, how trends develop over time, and whether the evidence warrants a change in assortment, planning, or marketing activity.

End-to-End Demand Planning

Mercury connects demand signals, forecasting, and allocation within a shared planning context. Agents support the ongoing evaluation of demand against inventory availability and commercial objectives, helping teams identify where assumptions need to be revisited. Planning becomes a continuous process that responds to changes across the business while preserving coordination between functions.

SWITCH LENS Marketing Active

Role-Specific Lenses

Mercury’s role-specific lenses organize information and decisions around the responsibilities of each retail function. Merchandising, Planning, Marketing, and Finance teams work from a shared business context while examining the measures and trade-offs relevant to their roles. This supports cross-functional coordination without losing the specialized perspective each discipline brings to a decision.

Starting Point for New Products

Mercury’s analogue-based approach uses evidence from comparable products to establish an initial demand range and production recommendation before a new item has its own sales history. This gives Merchandising and Planning teams a basis for evaluating launch quantities and inventory exposure, with assumptions that can be reassessed as actual performance becomes available.

INDUSTRIES

Who is Mercury For?

Mercury supports brands and retailers whose commercial decisions depend on coordination across products, channels, and partners. Its shared operating context accommodates the distinct planning cycles, customer expectations, and operational constraints of each industry.

1

Consumer Packaged Goods

Connect product innovation, demand planning, and channel performance to inform launch volumes, promotional activity, and distribution priorities. Mercury helps teams assess consumer demand alongside retailer requirements and supply commitments across the product lifecycle.

2

General Retail

Connect merchandising, inventory, marketing, and financial planning across stores and digital channels. Mercury helps teams assess commercial trade-offs and coordinate decisions as customer demand, product availability, and trading conditions evolve.

3

Grocery

Coordinate assortment, replenishment, and promotional decisions in an environment shaped by frequent purchases, perishability, and local demand. Mercury helps teams evaluate availability and inventory exposure in the context of shelf life, supplier lead times, and store-level performance.

4

Luxury Fashion

Bring collection planning, merchandising, and client demand into a shared commercial context. Mercury supports decisions about assortment depth, regional allocation, and product introductions while accounting for seasonality, exclusivity, and the integrity of the brand.

THE MERCURY DIFFERENCE

Intelligence That Carries Through

Retail decisions unfold over time and across functions. Mercury brings persistent business context, temporal reasoning, and autonomous execution into a shared operating environment, allowing agents to carry work forward as conditions change.

Product Comparison
Conversational Apps
Aquerius Mercury
Workflow Automation
Intelligence & Context
Business Context
Uses Information Available to the Interaction
Maintains Shared Context Across Retail Functions and Decisions
Uses Inputs and Rules Defined for the Workflow
Response to Changes
Produces Updated Response When Asked
Reassess Ongoing Work As New Evidence Becomes Available
Follows Configured Branches and Exception Rules
Temporal Reasoning
Examines Historical Information When Prompted
Relates Prior Decisions, Current Conditions, and Future Commitments
Follows Schedules and Event Conditions
Execution & Oversight
Decision Coordination
Helps Individuals Investigate and Prepare Work
Coordinates Interdependent Decisions and Tasks Across Functions
Connects Pre-Defined Steps Across Systems
Human-In-The-Loop
Users Initiate and Direct Interactions
Teams Establish Objectives, Permissions, and Approval Requirements
Teams Define Workflows and Manage Exceptions
Operating Model
Responds to User Questions and Answers
Pursues Objectives Through Coordinated Aquerius Agents
Executes Configured Sequences and Triggers

ARCHITECTURE

Why Mercury Works

Mercury combines knowledge graphs, retail ontologies, and temporal reasoning to establish a connected understanding of your business. Together, these foundations allow its agents to interpret information within its commercial context, account for dependencies across functions, and reassess decisions as conditions change.

Knowledge Graphs

Mercury connects products, customers, inventory, suppliers, and commercial activity through their business relationships. These connections give agents the context to evaluate how a change in one area affects decisions elsewhere in the organization.

Ontologies

Retail ontologies define the concepts, relationships, and constraints that structure Mercury’s understanding of the business. They establish consistent meaning across systems, allowing agents to interpret information according to the products, processes, and commercial rules it represents.

Temporal Grounding

Mercury accounts for when information applies and how business conditions change over time. Its agents can evaluate current circumstances against earlier assumptions and future commitments, preserving the context needed to revisit decisions as new evidence emerges.

Frequently Asked Questions

What is an agentic operating system and why do I need one?

An agentic operating system is a software layer that connects business knowledge, decision-making, and execution across existing systems. It gives AI agents a shared understanding of the organization’s objectives, relationships, and constraints, allowing them to monitor conditions and carry out coordinated work within defined permissions. That context persists over time, so agents can account for previous decisions and future commitments as circumstances change.

For retailers, its value lies in managing the dependencies between commercial decisions. A change in demand may require adjustments to purchasing, allocation, and promotional plans, each owned by a different team. Mercury brings these activities into a shared operating environment, helping teams assess the implications, delegate execution, and retain oversight of decisions that require their judgment.

How can Mercury forecast a new product with no sales history?

Mercury uses analogue-based forecasting to establish an initial demand estimate from comparable products. Product attributes such as category, material, intended audience, and SKU type help identify relevant comparisons, while available market signals provide additional context. These inputs inform a demand range and production recommendation before the new product generates its own sales data. As results become available, teams can reassess the initial assumptions against observed performance.

What is a temporal knowledge graph?

A temporal knowledge graph represents business information, its relationships, and the periods during which that information applies. In retail, this matters because prices, assortments, inventory positions, and supplier commitments change over time. Mercury uses this structure to interpret current conditions alongside the circumstances behind earlier decisions, allowing its agents to account for what has changed and which assumptions remain relevant.

How is Mercury different from a spreadsheet or business intelligence tool?

Spreadsheets and business intelligence tools support analysis, reporting, and planning. Mercury adds a shared operating environment in which agents maintain business context and carry work through from analysis to coordinated execution. When conditions change, agents can reassess the implications for related decisions and act within defined permissions. Teams retain oversight through role-specific views and approval requirements, with the context behind decisions available for review.

Who on my team uses Mercury?

Mercury supports merchandising, planning, buying, marketing, and finance teams through views organized around their responsibilities. Each function can examine the information, decisions, and trade-offs relevant to its work while retaining visibility into dependencies across the business. Teams bring their domain expertise and commercial judgment; Mercury provides a shared context for applying that expertise and coordinating the resulting actions.

How does Mercury refine its forecasts over time?

As sales results become available, they provide evidence for reassessing the assumptions behind an initial forecast. Mercury uses that evidence to refine demand estimates and inform subsequent planning decisions. The extent of improvement depends on the quality and relevance of the data, the comparability of products, and changes in market conditions. Forecast performance should therefore be evaluated against actual outcomes across relevant products and planning horizons.

Why not build an agentic operating system in-house?

Building internally is an option for organizations with the engineering capacity and domain expertise to develop and maintain the system. The work extends beyond connecting a language model to company data. It includes defining business concepts and relationships, preserving context over time, coordinating agents, managing permissions, and evaluating performance as systems and processes change. Mercury brings these capabilities together around retail operations, allowing teams to focus their implementation effort on their own commercial priorities and operating requirements.

How much autonomy do Mercury's agents have?

Mercury’s agents operate within defined permissions and approval requirements. Their scope can include monitoring conditions, preparing recommendations, and carrying out authorized tasks, with decisions requiring human judgment routed for review. This allows teams to establish where autonomous execution is appropriate and where commercial accountability requires direct involvement.

Does Mercury replace our existing systems?

Mercury serves as a decision and coordination layer across connected business systems. Its role is to bring their information into a shared commercial context and support actions that depend on several functions or sources of data. The systems connected, information available, and actions agents can perform depend on the integrations and permissions established for your deployment.

PRICING

Pricing Built Around Your Business

Mercury pricing reflects your SKU count, sales channels, and operational complexity. Tell us about your business and the processes you want to support. Our team will work with you to define the scope and prepare a tailored proposal.

Our team will follow up to discuss your requirements. No obligation.

Thanks, your request has been received! Our team will follow up within 2 business day with pricing tailored to your business.
Oops! Something went wrong while submitting the form.