Inventory, store operations, and fine-tuning: Nebius provides early access to three NVIDIA retail agent blueprints
Inventory, store operations, and fine-tuning: Nebius provides early access to three NVIDIA retail agent blueprints
An inventory agent’s purchasing recommendation can leave a retailer carrying excess stock or unable to fulfill orders, while a store operations agent needs clear limits on which systems it can access and what it can change. Both need constant evaluation as products, suppliers, and operating conditions change.
Nebius is running three new NVIDIA retail blueprints that address these challenges, launched at GTC Berlin
If you’re a retailer looking to deploy one of these blueprints, we’re offering a no-commitment POC. And if you’re looking to use the blueprints yourself, join the Nebius x NVIDIA webinar where we’ll walk through an example blueprint, deployment options on Nebius, and how to adapt it to your systems.
Blueprint 1: inventory lab
Supply-chain planners need to understand the consequences of a purchasing decision before changing a real order. What happens to cost and fulfillment if a distribution center carries less safety stock? If a supplier’s lead time doubles? If the business changes how it replenishes slow-moving products?
NVIDIA’s Inventory Lab Blueprint combines agents with algorithms, mathematical solvers, and simulation to build and evaluate inventory replenishment policies. The policies can range from learned policies leveraging PyTorch or cugraph-gnn to optimized policies leveraging cuOpt. Agents orchestrate the end-to-end experiment workflow and development and evaluation best practices are enforced with a Nemotron as a judge. The initial goal is to reduce inventory costs while maintaining fulfillment.
The blueprint has four components:
- Supply-chain simulator: Models the movement of products through suppliers, distribution centers, and stores under uncertain demand and lead times.
- Developer agents: Build and test purchasing rules and models.
- Manager agent: Tracks the developer agents and decides which strategies to explore next.
- Arena and judge agent: Evaluate the strategies against the experiment’s objectives.
On Nebius, the experiments run as Slurm jobs on a Managed Soperator cluster of NVIDIA H100 GPUs. Nebius’ Managed Service for MLflow tracks runs so teams can compare results across different assumptions and purchasing strategies. The agents access their reasoning models through the Token Factory model catalog
Blueprint 2: agent harness for store operations
Resolving a store incident can require information from several systems and action from several people. An agent helping with that response needs relevant context, access to permitted tools, and boundaries around its actions.
NVIDIA’s Agent Harness for Store Operations Blueprint provides the framework for that workflow. It helps an agent identify an incident, propose a response, and guide a store manager through the next steps — including providing a morning brief report that highlights the most important information they need to know at the start of their day. Built with NVIDIA Agent Toolkit and an open-source agent runtime, it combines:
- Hermes agent: Manages memory, tool use, and task execution
- NVIDIA OpenShell: Provides a sandboxed runtime and policies governing system access, tool use, and inference traffic.
- Model routing: Directs requests to the appropriate model for the task.
- NVIDIA Nemotron 3 Ultra: Provides the reasoning model, with a vision model for image-based incidents.
In the Nebius deployment of the blueprint, Token Factory serves the models through its public endpoints — NVIDIA Nemotron 3 Ultra for reasoning and a vision model from the catalog for image-based incidents, with NVIDIA Nemotron 3 Nano Omni available as a dedicated endpoint for teams that want an all-Nemotron stack. The Hermes agent and its OpenShell sandbox run on a Nebius CPU virtual machine; no GPUs are needed on the agent side. Teams can scale the agent runtime and model inference independently, without managing a GPU cluster for inference.
Blueprint 3: intelligent warehouse fine-tuning flywheel
A retail warehouse agent must interpret operational data, use enterprise systems and optimization tools correctly, and respect business constraints as products, processes, and operating conditions change. Training may begin without labeled examples, but the deployed agent must work with real warehouse data.
NVIDIA’s Intelligent Warehouse Fine-tuning Flywheel Blueprint turns synthetic data, model training, simulation, and operational feedback into a continuous improvement loop, built around NVIDIA Nemotron models and the NeMo platform:
- Build and expand training coverage: Use a Nemotron teacher model to generate domain-specific examples for labor allocation, inventory exceptions, wave management, and disruptions — including rare scenarios that production data may not capture often enough.
- Specialize and refine models: Use supervised fine-tuning to develop a compact Nemotron warehouse expert, then NeMo RL for reinforcement learning against a warehouse simulator to improve its decisions through reward feedback.
- Evaluate and deploy: Assess task performance, tool use, constraint adherence, and safety before a controlled rollout, with NeMo Guardrails and human oversight.
- Capture experience and repeat: Record operational context, actions, tool calls, and outcomes. Use newly discovered failures to improve datasets, evaluations, and subsequent training cycles.
On Nebius, the flywheel runs entirely on serverless services: teams iterate in Nebius Serverless AI DevLabs, run fine-tuning and evaluation as Serverless AI jobs on NVIDIA accelerated computing, and consume the base and improved models from Token Factory public endpoints
Right-sizing infrastructure for each blueprint workload
Each blueprint comes with different demands on infrastructure. Inventory experiments need compute while simulations run, a store agent needs an application runtime and access to inference, while fine-tuning requires a separate training workflow, followed by evaluation before an updated model reaches users.
Catalog enrichment shows how these choices play out. A pipeline can turn a product photo and sparse metadata into localized descriptions, FAQs, and visual assets. Running that pipeline for thousands of products across multiple markets means deciding how to allocate compute across several models, and whether the work needs to happen interactively or in batches.
Teams can start with the models deployed together on a Nebius virtual machine with NVIDIA H100s. Managed Kubernetes allows them to separate model deployments and scale the busiest components independently. Token Factory provides managed inference for supported language, vision, and embedding models, reducing the number of model services the team operates itself.
A catalog refresh can run offline, while an interactive editing tool needs responsive inference. Model training can run separately from either workflow. Where enrichment needs supplementary product information from the web, Tavily
The new blueprints follow the same principle: match the infrastructure to the work each step performs, connect the workflow to the retailer’s systems, and evaluate it against the business’s requirements.
See the blueprints in action
Join Nebius and NVIDIA engineers in a practical webinar, where we’ll walk through an example blueprint, deployment options on Nebius, and how to adapt it to your systems.
To learn more about how retailers run AI on Nebius, see the Retail & Commerce solutions page.





