MoSES is a NeurIPS 2025 neural solver for many truck routing problem variants. It mixes small add on weights experts on shared backbones to handle sixteen truck route task types with one gating network.
The short version
Logistics AI teams want one model that adapts when constraints change. MoSES pretrains on capacitated routing, then fine tunes low rank experts for open routes, time windows, pickups, and more. arXiv 2510.21453 documents the method with open PyTorch code.
What the researchers did
Authors introduce Mixture of Specialized Experts Solver under a State Decomposable MDP view. The NeurIPS 2025 paper link is on arXiv as 2510.21453.
Training has three stages. First a shared backbone learns standard capacitated truck route task. Next frozen backbone weights host small add on weights adapters for basis variants like open truck route task, length limits, backhauls, and time windows.
Finally an adaptive gate blends experts so one policy serves sixteen combined variants. Implementation builds on RouteFinder and CaDA code lines.
GitHub repo panyxy/moses_vrp publishes shell scripts for each stage and pretrained checkpoints for tests.
Photo: RDNE Stock project / Pexels
What they found
Experiments span sixteen truck route task variants with node counts such as fifty and one hundred in training scripts. Authors report MoSES beating prior multi task routing models on their test suite suite.
small add on weights rank thirty two experts appear in default multilora scripts. That keeps fine tunes small compared with full weight copies per variant.
Test scripts include generated instances and CVRPLIB style sets for out of distribution checks. Read the paper tables for gap percentages versus classical solvers.
Photo: Tom Fisk / Pexels
Why it matters for you
Retail and parcel planners juggling mixed constraints can evaluate one neural solver instead of six separate models. Chip and pharma cold chains with time windows may map cleanly to VRPTW experts if your data matches training distributions.
Teams teaching routing tradeoffs can compare learned policies with classical OR tools using the released checkpoints.
What to keep in mind
Neural solvers excel on trained sizes but can fail on odd city maps. Always keep OR-Tools or HGS as a safety net for production routes.
Training multi stage MoSES needs GPU clusters and careful checkpoint paths in config files.
Peer reviewed NeurIPS text may add errata. Recheck arXiv version dates after conference.
School students curious about tech can follow the GitHub links. You do not need a lab badge to read code and watch issue threads. That is a free way to learn how research turns into software.
Small clinics, farms, and shops should ignore hype posts. Ask vendors whether their product cites a peer reviewed paper or only a blog recap. A clear source link is a sign of respect for your time.
Teams that ship fast should still read the full PDF tables. Headline wins on clean test suites often fade once real data adds noise, broken tools, and slow networks.
Readers at home feel this work through safer apps, cheaper goods, or better research tools over time. None of these papers alone change your phone tonight. They show where labs spend effort this month.
If you train models, log which paper version you used. Authors may post fixes after peer review. A date stamp in your internal wiki prevents stale citations in slide decks.
Public posts on social sites may show demo videos without context. Treat those clips as ads until you read the methods section. Good science explains limits as clearly as wins.
Write down one question you still have after reading. Bring that question to your next vendor call or lab meeting. Smart teams reward curiosity more than buzzwords.
Key takeaways
- MoSES mixes small add on weights routing experts with adaptive gating for sixteen truck route task variants.
- arXiv 2510.21453 and NeurIPS 2025 frame the State Decomposable MDP story.
- Open repo panyxy/moses_vrp ships training and test shell scripts.
- Shared backbone plus experts cuts retraining cost versus separate models.
- Supply chain AI leads should validate on their own city graphs before rollout.
Sources
- Primary — arXiv, Multi-Task Vehicle Routing Solver via Mixture of Specialized Experts under State-Decomposable MDP (2025). Method, theory, and test suite tables.
- Secondary — GitHub, panyxy/moses_vrp (2025). Official PyTorch training and testing scripts.
Related in Supply Chain
- Supply Chain · 3 min readLipBR Algorithm Learns Where To Move Shared Bikes Without Full Demand Data
- Supply Chain · 4 min readColumbia Team Studies Blocking Model Theft From Planning APIs
- Supply Chain · 4 min readNeural Operator Planning Under Noise Targets Uncertain Supply Decisions
- Supply Chain · 4 min readNVIDIA cuOpt 26.10 Targets Million Variable Logistics Models
- Supply Chain · 3 min readSam Altman Bets OpenAI Custom Silicon Stays on TSMC Flow
Continue reading
LipBR Algorithm Learns Where To Move Shared Bikes Without Full Demand Data
