Forex lots, contract size and base units
Translate entered lots into a declared linear quantity before comparing instructions, fees or account outcomes.
The unit belongs to the actual offer
A lot label is not enough to establish an economic quantity. Record the exact symbol, product type and contract size supplied for the intended account. The same familiar currency name can be attached to different specifications. A review should carry these fields beside the named subscription rather than assume the publisher and every subscriber use identical units.
The practice packet expressly assumes one hundred thousand base units per lot for its fictional rows. That assumption is not a claim about every broker or product. MetaTrader documentation describes symbol specifications as an account-level source for contract and volume properties. Consult the relevant account specification before translating a real instruction.
Convert quantity before money
For the packet's FX-A, one tenth of an entered lot times one hundred thousand gives ten thousand base units. A reduction of four hundredths of a lot removes four thousand units and leaves six thousand. The result is quantity conservation, not a portfolio allocation recommendation. A lot amount without its contract multiplier cannot establish the same calculation.
Retain the original requested lots and the actual executed lots as different fields when they differ. Rejected, partially filled or rounded requests need their own state. An instruction that says reduce half should identify the quantity to which half refers; it should not silently refer to a later enlarged position.
One entry lot is a deliberate boundary
The journal accepts one original entry lot and subsequent reductions. An addition at a different price needs another entry lot rather than an invented blended execution. A broker may display a net position, but that display does not remove the need to understand its underlying quantity changes when reconstructing a service workflow.
Keep entry price, entry time and contract basis attached to the original lot. Compare summed reductions with that original quantity before evaluating the remaining mark. The over-exit teaching variant requests more lots than the original contains. Rejecting it preserves the inventory; quietly capping it would manufacture a different action from the supplied instruction.
Volume increments do not determine suitability
Minimum, maximum and step values answer whether a supplied quantity fits a declared grid. They do not say whether the resulting exposure is appropriate for an account. The order-grid exercise floors a requested amount on an explicitly zero-origin grid and never rounds a below-minimum result upward to force acceptance.
Some arrangements may use a different grid convention or impose other constraints. Such conditions need their own documentation rather than a claim that this exercise models the whole broker. A valid arithmetic volume still needs actual order acceptance, instrument access, cost terms and the reader's independent decision about whether to use the workflow.
Keep a units-first comparison sheet
A useful comparison row contains offer identity, account type, symbol identifier, contract size, requested lots, executed lots, volume convention and source date. A second row records the action attached to the quantity: original entry, reduction, additional lot or cancellation. Keep the two layers linked without turning message count into trade count.
The packet exposes all four fictional original quantities and three reduction events in downloadable records. Inspect the quantity before the outcome and keep any unresolved contract specification visible. This makes unlike forex workflows easier to compare without claiming a new provider performance test or treating an example contract size as a universal market rule.
Reference documents
These references cover mechanisms and source definitions. The worked numbers on this page are invented teaching inputs, not provider or account records.