M3CloudSlam
Now onboarding founding customersSee it live at M3UA Benelux · 3-4 Nov

Infor M3 · Cloud & On-Premise

Know what M3 will do, before it does it.

M3CloudSlam understands how your M3 behaves, field by field and step by step. Explain what happened, predict what will happen, and govern the master data that decides it.

  • ✓ Connects to your own M3
  • ✓ Read-only by default
  • ✓ Cloud and on-premise
PredictorPreview
If I do this
Report receipt · manufacturing order 7001234100 pcs
Releasedstatus 20lot?Stock placedA-01 · approvedOperationcompletedReported60Inspection ?other route
  • 1Checks the receiving location and the item's lot control2 checks
  • 2Places 100 pcs in stock at location A-01, status approvedstock
  • 3Reports the last operation as completedoperations
  • !Quality inspection request: depends on a setting it will read from your M3open question
  • 4Order moves from status 20 to 60, "Reported"status
M3 will accept this. 43 records written, listed with their values.Predicted

Sound familiar?

The questions every M3 team keeps asking

Today they are answered by searching, testing in copies of production, asking the one colleague who knows, or calling in a consultant. M3CloudSlam answers them directly.

“You don’t need a consultant for that anymore.”

Your own team gets the answers, straight from your M3: what happened, why, and what will happen next.

How it works

One graph that knows how M3 behaves

At the heart of M3CloudSlam is a knowledge graph of M3: what every screen, API call and job does, which settings steer it, what it checks and what it writes. Connected to your environment, it answers with your configuration and your data.

ShowExplainClarifyPredictTrace
17.5 M
elements of M3 knowledge
34 M
connections between them
Per release
rebuilt for each M3 version
M3 behaviourConfigurationYour dataExpert knowledgeShowExplainClarifyPredictTrace

The platform

Nine ways to ask your M3 a question

Every feature asks the same graph a different kind of question. Most are available today; the newest are in preview for founding customers.

Flow Viewer · landscape
SALES & DELIVERYSUPPLYSTOCKFINANCEDelivery / shipment14 statusesCustomer order8 statusesOpen ›Picking9 statusesCustomer invoice10 statusesPurchase order14 statusesManufacturing order8 statusesDistribution order14 statusesRequisition order14 statusesStock on handbalances, no statusesStock move order13 statusesCustomer payments6 statusesGeneral ledger5 statusesreceiptallocates
Click a process to open it.Available
All features →

Release readiness

Every April and October, Infor changes M3. Know what changes for you.

Around 70 to 80 feature toggles expire each release, and an expired toggle can’t be switched off. M3CloudSlam shows what each one changes in your flows and checks your own data for the situations it affects.

Affects youExample: 120 of your 124 open replenishment deliveries would get a priority
Not met by your data on 7 OctoberThe situation it changes does not occur in your environment
Can't tell yetWe say so, instead of guessing
How to prepare for a release →
Release readiness · April 2027 release · your PRDRelease Toggle Impact · Preview
74toggles expire with this release
9Affects you
58Not met by your data on 7 October
7Can't tell yet

Affects you, by area

  • Warehouse4
  • Sales2
  • Purchasing2
  • Finance1

Needs a decision 3 of 9 planned

  • Replenishment deliveries get a priorityTest pickingWarehouse · in your data: 120 of 124 open deliveries
  • Credit check moves to order entryInform salesSales · in your data: 38 customers near their limit
  • New matching tolerance on invoice linesDecide ownerPurchasing · in your data: 212 lines last month

Checked against your data on 7 October. Example toggles and figures.

Master data

Your master data decides how M3 behaves

An item, a customer or an order type is more than a description. Its settings decide whether orders allocate, release, ship and invoice. M3CloudSlam knows which fields steer what, and governs them accordingly.

Item/warehouseAllocation method decides how customer order lines get stock
CustomerCredit limits decide whether an order stops at entry or release
Order typeRelease settings decide whether deliveries go to the warehouse automatically
Why master data matters, and how M3CloudSlam keeps it right →

Data Governance · three levels per field

L1FollowEvery change recorded, old and new value
L2Follow + ApproveChanges in M3 signed off afterwards
L3Write-backProposed, approved, then written to M3

Environment Intelligence

Audit, compare and document your M3 environment

Compare environmentsPRD, ACC and TST side by side, with every difference listed
H5 personalisations and scriptsWhat is in each environment, and what changed
ION data flows and interfacesDocumented and mapped, including MEC agreements
Automated documentationGenerated from the environment itself, always current

Where we are going

From understanding M3 to improving it

RoadmapRelease VerifierEach April and October: affected flows found, tests generated and run, a verdict per flow.
RoadmapAutomated Test SuiteA test case for every path through a process, with its expected outcome from the Predictor.
RoadmapScenario LabChange a setting on paper; replay last month through it; compare before and after.
RoadmapProcess InsightsVariants, waiting times, bottlenecks and deviations, linked to the setting that causes them.
RoadmapSolution Proposer & BuilderDescribe a wish, a requirement or a problem. M3CloudSlam proposes possible solutions, each with its effect, risk and effort. Build the chosen one in a simulated M3, run it and simulate real volumes, then turn it into real M3 objects with one click: in test first, then production.
DescribeProposalsBuild virtuallyRun & simulateMake it real
See the full roadmap →
Your own M3Connect M3CloudSlam environments to your PRD, ACC and TST.
Read-only by defaultNothing is written to M3 unless you approve a change.
Cloud and on-premiseOn-premise through an outbound-only connector.
Honest answersWhen something can't be known, M3CloudSlam says so.

From the founder

“The same problem kept surfacing on every M3 project: teams making big decisions about their environment without ever being able to actually see what’s in it. M3CloudSlam is the tool I always wished I had. We’re building it now with a first group of M3 teams - and shipping to early customers this autumn.”
AK

Alexander van der Kuijl

Founder · 15+ years in Infor M3 · LinkedIn

Be among the first to ask your M3 anything

We are onboarding a small group of founding customers. You get the newest features first, a direct line to the team, and founding pricing.

Become a founding customer
  • Preview features firstPredictor, Debugger, Release Toggle Impact and Value Provenance
  • Shape the roadmapYour M3 questions decide what we build next
  • Founding pricing, locked inYour rate stays as the product grows