An inventory difference is not always solved with an adjustment. Goods moved between warehouses need a transfer. Materials consumed internally need an issue. A product returned by a customer needs a return process. Using adjustments for everything may produce the right balance for a moment, but it erases the event and makes routine operations indistinguishable from mistakes.
Transfer: the place changes, not the total
A transfer moves quantity between two company locations. It should decrease the origin and increase the destination as one connected operation. Use it to replenish a store, load a vehicle, or send an item to a repair area. When travel takes time, receipt can remain pending. The destination owner confirms quantity and condition instead of assuming the full shipment arrived.
Suppose ten cases leave the main warehouse and a branch receives nine. Closing the transfer for ten hides the shortage; receiving nine without follow-up leaves one unit floating. Record the difference and investigate. The case may remain in the truck, be damaged, or reflect a dispatch count error. The correct movement preserves the right question.
Issue: a unit stops being available
An issue reduces stock because an item leaves saleable inventory. It may come from a sale, internal material use, an authorized sample, or a documented disposal. The reason matters. An invoice explains a sale; an internal request can explain consumption. Labeling every event manual issue combines unrelated facts and later offers little help with costs, replenishment, or control.
Before disposing of damaged goods in the system, check whether they still exist physically and should stay isolated. A transfer to Damaged may be more accurate than removing them immediately. Once the company authorizes final disposal, record the corresponding issue with support. The software should reflect the actual state rather than anticipate a decision nobody has made.
Adjustment: a verified difference
An adjustment raises or lowers the balance when a count proves the system differs and no pending movement explains it. Record a reason, date, responsible person, and evidence. It should not be a shortcut for making a report balance. Frequent adjustments call for a review of receiving, dispatch, units of measure, and permissions because the pattern often exposes a weak process.
A count finds 47 units while the system says 50. Before posting negative three, inspect recent invoices, purchases awaiting receipt, open transfers, and returns. If an unposted sale explains the difference, record the sale correctly. Only when the investigation cannot recover the cause should the physical difference become an adjustment. The history then avoids blaming the count for an earlier error.
Returns and repairs have their own story
A customer return is not automatically available stock. The item may come back sealed, damaged, or incomplete. Receive it into review, then decide whether it returns to sale, enters repair, or is written off. Supplier returns also benefit from separate dispatch, supplier receipt, and replacement events so the same unit never appears to occupy two places.
Repairable assets move through statuses and locations. Equipment leaves an employee, enters the workshop, goes to an outside vendor, and eventually returns to service or is retired. A negative adjustment at the start loses custody information. Transfers and repair outcomes show who has the item, for how long, and what must happen before closure.
A short decision rule
First ask whether the item still belongs in stock. If it does but changed place, transfer it. If it left through a known operation, record the issue and its origin. If it came back, handle the return and condition. If a count reveals an unexplained difference, investigate and then adjust. This sequence prevents adjustments from becoming a drawer for every exception.
Tario keeps locations, movements, assignments, and repairs in a history the team can review. Configuration helps, but the operating rule remains a human decision: who records, who approves exceptions, and what evidence is required. Test recent business cases and inspect the resulting kardex. If a colleague understands the event without calling its author, the movement has done its job.