Presell order
The customer order is recorded in product units before delivery.
Sales representativeModel scenario
Keep the order in pieces and the delivered weight in one linked workflow. This model explains the mechanism; it is not a named customer's result.

Evidence level
Presell + van-sale for goods sold by weight
The sales representative takes an order in pieces. At the outlet, the driver records the actual weight and closes the order in kilograms. The system keeps the original order linked to the actual delivery.
Model scenario · no named customer
The customer order is recorded in product units before delivery.
Sales representativeThe weight is recorded at the outlet and used to close the order against the actual delivery.
Driver / van-seller01 · Order
02 · Link
03 · Weight
04 · Document
05 · Closing
Order fulfilment
The process keeps the preliminary quantity and actual weight distinct, while preserving their link.
The representative records the agreed number of product units.
The driver receives the linked order for fulfilment.
The actual weight is determined at delivery.
The document records the quantity of goods actually handed over.
The order is closed at the outlet on the day of delivery.
Process participants
The scenario changes both the document flow and how work is shared between field sales, delivery, the office and the system.
Linked records
The value of this model is a traceable link between what the outlet ordered and what was actually delivered.
Original intent
Actual weight recorded in the field
Closing document
Fulfilment complete
Units of measure
Pieces reflect the original agreement with the outlet; kilograms reflect actual fulfilment. The closing document preserves the link between them.
Process change
The operator receives the delivery note after the route, revises the original order and re-enters the kilograms.
The driver enters the actual weight at the outlet, creates a linked document and closes the order online.
What the workflow includes
What to agree during implementation
These questions do not claim additional capabilities. They define the implementation scope for products, documents, roles and field operations.
Products and units of measure
01Recording accuracy
02Roles and permissions
03Process exceptions
04Evidence and its limits
This page presents the confirmed workflow for working with two units of measure. It does not publish measured improvements, team productivity or project financial results.