See Setu Move on your own data.
A working session against your estate and your processes. Bring the thing that costs you money.
WHAT IT DOES
Inside Setu Move.
01
The digital journey slip
Replaces the white slip, the pink slip and the government royalty slip with one role-gated state machine from issue to stocked-in, with hold and cancel, a duplicate-truck guard, and multi-truck dispatches that print one combined slip and close when every child arrives.
02
Trip types with consequences
Sale, mine-to-mine transfer, registered plot transfer and third-party purchase each carry their own royalty and SAP behaviour; a registered plot transfer deliberately posts nothing, and the manual says why.
03
Royalty compliance
Two configurable routing (weigh at the centre before or after loading, auto-suggested from the mine-to-center distance), a government QR scrape that fills the royalty number, tonnage and paid amount from the state portal with the source URL retained for inspectors, a variance auto-incident above 5%, and an audit pack kept seven years.
04
Weighbridge evidence
Indicators read over RS-232 or Modbus by SetuEdge, ANPR correlating the plate to the weighment, swap guards on tare and gross, and a design rule worth quoting: edge events annotate a trip as evidence; they never silently drive a state change.
05
The SAP posting chain
Outbound delivery, batch selection, pick, PGI and goods receipt posted over O Data and CPI as the trip exits and stocks in; each binding configurable per state; per-step retry that never re-posts a succeeded document; failures shown with full request and response and one-click retry.
06
Transporter portal
Journeys, documents and freight invoice booking routed into SupplierX for payment.
07
Field surfaces
An operator app for every checkpoint role, WhatsApp flows for the people who won't install one, and bulk upload for master data and batches.
AI INSIDE
Shipped, not shown.
Everything below runs in the product today. Where a capability is deterministic rather than a model, we say so.
01
Agents that chase, not agents that act
Two scheduled agents run daily: one finds slips missing royalty or plant acknowledgement and WhatsApps the chase list; the other raises one replenishment approval per low-stock item. Neither mutates journey state, neither posts to SAP that rule is written into the code
02
TAT risk, without a model
Per-lane baselines from completed journeys; an active slip past its lane's 80th percentile is flagged with its position. Statistics defensible to the customer whose truck it is.
03
Exception triage
The live exception feed ranked by business impact with a next-best action per item. The model suggests; a person acts.
04
Slip readers
Truck plates, weighbridge slips, royalty slips and pink slips read server-side, so the vision
BULK MATERIAL LOGISTICS
The digital trail for bulk material, mine to plant.
Three paper slips replaced by one journey verified at every checkpoint, weighed at every bridge, royalty-proven, and posted to SAP on exit and arrival.
10
Checkpoints per journey
7
yrs
Audit pack retention
5
%
Royalty variance auto-incident threshold
24X7
Journey tracking
INTEGRATIONS
What it connects to.
1
SAP outbound delivery, PGI, goods receipt over OData and CPI
2
SetuEdge weighbridges, ANPR and barriers over Pub/Sub
3
The state royalty portal via QR scrape
4
SupplierX for transporter invoices
5
WhatsApp Cloud API
BULK MATERIAL LOGISTICS
The digital trail for bulk material, mine to plant.
Three paper slips replaced by one journey verified at every checkpoint, weighed at every bridge, royalty-proven, and posted to SAP on exit and arrival.
See SetuMove on your own data.
A working session against your estate and your processes. Bring the thing that costs you money.
Request a proposal
Talk to us
Sign up to learn more
SAP. Cloud. AI. One accountable partner.
Get Started
Who we are
Foundation
Leadership
Culture
Career
Contact us
Services
All services
RISE with SAP
GROW with SAP
SAP AMS (AXIOM)
AWS
Google Cloud
Multi-cloud CMS
Products
All products
SupplierX
OrderX
Xpense
Logystix
ManuFeX
AXIOM AI Platform
Industries
Manufacturing
Metals & Engineering
Energy & Oil & Gas
Textiles
FMCG & Distribution
Automotive & Aerospace
Alliances
About Us
Case studies
Trust & security
Blog
Investor relations
BSE disclosures
Follow Us
Twitter
LinkedIn
sales@aeonx.digital
Terms & Conditions
Privacy Policy
© 2026 AeonX Digital Technology Limited. BSE-listed. | All rights reserved. · SAP Gold Partner · AWS Advanced Tier · Google Cloud Partner
Cookies
Sitemap
Get an AI summary of this page
Get the latest from Aeonx
WHAT WE DO
Inside SetuMove.
01
The digital journey slip
Replaces the white slip, the pink slip and the government royalty slip with one role-gated state machine from issue to stocked-in, with hold and cancel, a duplicate-truck guard, and multi-truck dispatches that print one combined slip and close when every child arrives.
02
Trip types with consequences
Sale, mine-to-mine transfer, registered plot transfer and third-party purchase each carry their own royalty and SAP behaviour; a registered plot transfer deliberately posts nothing, and the manual says why.
03
Royalty compliance
Two configurable routing (weigh at the centre before or after loading, auto-suggested from the mine-to-center distance), a government QR scrape that fills the royalty number, tonnage and paid amount from the state portal with the source URL retained for inspectors, a variance auto-incident above 5%, and an audit pack kept seven years.
04
Weighbridge evidence
Indicators read over RS-232 or Modbus by SetuEdge, ANPR correlating the plate to the weighment, swap guards on tare and gross, and a design rule worth quoting: edge events annotate a trip as evidence; they never silently drive a state change.
05
The SAP posting chain
Outbound delivery, batch selection, pick, PGI and goods receipt posted over O Data and CPI as the trip exits and stocks in; each binding configurable per state; per-step retry that never re-posts a succeeded document; failures shown with full request and response and one-click retry.
06
Transporter portal
Journeys, documents and freight invoice booking routed into SupplierX for payment.
07
Field surfaces
An operator app for every checkpoint role, WhatsApp flows for the people who won't install one, and bulk upload for master data and batches.
10
Checkpoints per journey
7
yrs
Audit pack retention
5
%
Royalty variance auto-incident threshold
24X7
Journey tracking
INTEHRATONS
What it connects to.
1
SAP outbound delivery, PGI, goods receipt over OData and CPI
2
SetuEdge weighbridges, ANPR and barriers over Pub/Sub
3
The state royalty portal via QR scrape
4
SupplierX for transporter invoices
5
WhatsApp Cloud API
AI INSIDE
Shipped, not shown.
Everything below runs in the product today. Where a capability is deterministic rather than a model, we say so.
01
Agents that chase, not agents that act
Two scheduled agents run daily: one finds slips missing royalty or plant acknowledgement and WhatsApps the chase list; the other raises one replenishment approval per low-stock item. Neither mutates journey state, neither posts to SAP that rule is written into the code
02
TAT risk, without a model
Per-lane baselines from completed journeys; an active slip past its lane's 80th percentile is flagged with its position. Statistics defensible to the customer whose truck it is.
03
Exception triage
The live exception feed ranked by business impact with a next-best action per item. The model suggests; a person acts.
04
Slip readers
Truck plates, weighbridge slips, royalty slips and pink slips read server-side, so the vision
Signup to LlamaParse for 10k free credits!