Commodity reservation
Record the commercial context: counterparty, commodity, quantity and agreed terms within the enabled module.
RESERVATIONS · TRANSPORT · DOCUMENTS
From a commodity reservation.
To a connected transport workflow.
Connect the commercial agreement with a transport request, an individual transport and receipt or dispatch records. MATMASY helps keep each step in its business context.
Reservation80 t
80 t of wheat · DEMO-R104
Transport request20 t
20 t planned · DEMO-Q204
Individual transport
DEMO-T304 · final weighing pending
Linked documents
Receipt / dispatch as recorded
Fictional data · no available-stock calculation
01 / FROM AGREEMENT TO RECORD
Four connected steps.
Each with its own meaning.
A reservation, a transport request and a completed delivery answer different questions. Connecting them gives visibility; keeping them distinct preserves the meaning of the data.
Transport request
Link planned movement to the reservation, dispatch and receiving locations, and the planned quantity.
Individual transport
Review the linked transport and its status. An overall request and an individual movement are different records.
Weighing and documents
Connect the actual recorded weighings, receipt and dispatch. Check delivery status against the corresponding sources.
02 / A CONCRETE EXAMPLE
80 t reserved.
One transport planned for 20 t.
In this fictional example, wheat reservation DEMO-R104 exists. Transport request DEMO-Q204 covers part of the agreement and is linked to transport DEMO-T304. A final weighing has not yet been recorded.
- Which reservation does the request belong to?
- Which individual transport is linked?
- Is there a weighing and a related document?
CONNECTED RECORDS · FICTIONAL DATA
- ReservationDEMO-R10480 t of wheatCommercial context
- Transport requestDEMO-Q20420 tPlanned quantity
- TransportDEMO-T304Linked to the requestCompletion unconfirmed
- Final weighingNot recordedNo confirmed massMissing data
03 / AN OVERVIEW FOR DAILY WORK
Return from the overview
to the linked record.
Operators, dispatchers and managers need different levels of detail. An overview is useful when it shows scope, period and source, within the user’s company and module permissions.
Business context
Counterparty, commodity, locations and linked record identifiers.
Plan and execution
Distinct planned transport, movement status and actual weighing.
A source to check
The documents and records behind the overview.
MATMASY / AGROBOT
A question for AgRoBot
“Which transports belong to the selected reservation?”
AgRoBot can help review supported MATMASY sources. Access depends on the enabled pilot, user permissions and data scope. An answer does not itself create a transport or change a business record.
Meet the business AI assistants ↗04 / BEFORE GETTING STARTED
Questions about trade and logistics
Does a reserved quantity represent available stock?
Not automatically. Reservations, recorded mass, quality, documents and planned movements have different business meanings. Availability requires defined rules and appropriate sources; this page’s example does not calculate it.
Does a transport request confirm that goods were delivered?
A request describes a plan. Check the actual status, weighings and linked documents for each transport. A planned quantity does not replace a confirmed receipt or dispatch.
Are all modules immediately available to every user?
Availability depends on the agreed scope and enabled modules. Trade, consolidated reporting and AgRoBot have a controlled pilot scope. Appropriate permissions are required for both module entry and its business data.
How does implementation start?
Choose one workflow: a reservation, request and linked transport. Agree counterparties, locations, materials, documents and roles, then verify that example before expanding to additional processes.
MATMASY
Show us one reservation
and its transport workflow.
Describe the commodity, dispatch and receiving locations, and where the connection between plan, transport and documents is currently lost. Together we can define an initial demonstration scope.
matmasy@nebito.rs · A process description is enough for the first conversation. Please do not send passwords or confidential documents.