Buying stock and using stock are two different events, and they should have two different records. OpenStax's managerial accounting text describes a company that buys materials "in order to have enough inventory on hand for all of its jobs." The purchase builds the balance. The job draws on it. Mixing the two into one line makes it hard to see what came in, what went out and what is still on the shelf.
The same text ties materials to jobs through a materials requisition form, using the form for Job MAC001 as its example. A requisition is the document that says which job took the material and how much. For a parts store, the equivalent is the issue note: it names the job or order, the part, and the quantity issued. Use the sale unit on that note, so the cost of each job can be traced back to the stock it used. For the dispatch side, read Field Service Work Order Checklist for Dispatch Handoffs.
Hold the stock balance in one place. Most teams find it simplest to keep the balance in the sale unit, since that is what leaves the building, and convert the purchase into kilos when goods arrive. Whichever unit you choose, the balance should not be kept in two places, updated by two different methods. Two balances will disagree sooner or later, and then nobody knows which one to trust.
Decide, too, who is responsible for the balance. One person or one role should be able to answer for the figure in the system, and should be the only one who adjusts it. When several people can change the balance with no shared record of why, the balance stops meaning anything, and every count becomes an argument about who touched it last.