When a Spare Part Becomes a Machine
A boxed sewing machine on a rack is stock. Bolted to a floor with an operator on it, it is an asset. Our system can move it across that line properly — and the moment it crosses, it gains three things it never had and loses one it did.
Most of what we publish about our own product is about a join that is missing. This one is about a join that is there, because a factory buying its own equipment crosses it constantly and almost no inventory system handles it at all.
The line is between a thing you hold to consume or sell, and a thing you hold to use. A carton of machine needles is stock. A machine is an asset. The difficulty is that they arrive on the same purchase order, from the same supplier, into the same warehouse, and for a while they sit on the same rack.
What the conversion actually does
You issue the unit out of stock and, in the same act, create an asset record from it. The conversion is a record in its own right: it keeps the adjustment it came from, the issue line, the resulting asset, the stock row it was taken from, the item, and the payload of asset details captured at the time.
The timing is the part worth noticing. The asset is finalised on the approved adjustment, not on the requested one. So a conversion that is raised and never approved does not leave an orphan asset behind, and the register does not fill up with machines that were thought about and not issued.
One unit, two records, one link between them that survives an audit. That is the whole feature, and it is more than most inventory systems attempt.
What the unit gains when it crosses
Three things, and they are the three that make an asset register worth having.
What the unit carries on each side of the line
Ownership type
An asset is owned, leased or borrowed, and the value is validated in five separate places. Stock has no ownership concept at all — every unit in it is yours by assumption. See Stock That Is Not Yours.
A working serial number
On an asset it is a field on the record itself: stored, searchable, bulk-importable, used in movement, and entered when the asset is created from the issue. Stock tracks serials of its own now, captured at receipt and named on every movement out — see A Register That Cannot Be Filled for how that register started empty.
Custody
An asset has a custodian, a location, and a movement history covering check-out, check-in, transfer, relocation, verification, damage, loss and retirement. Stock has a location and no keeper.
A cost that moves with a market
Stock carries a weighted average cost that is recalculated as you buy. An asset carries what it cost, and stays there.
A service schedule
Only the asset side has one. Once the machine is an asset it can carry a preventive schedule that opens its own work orders when a service falls due, and a work order that takes it out of service measures the downtime. A carton on the rack has none of that, and neither side reads an hour meter or holds a calibration date.
The last row is the one to read twice if you are buying for a plant. Servicing begins at the conversion: a machine still on the rack as stock has no schedule to fall due, which is one more reason to convert it the day it goes to the floor.
Why a garment or footwear plant crosses this line more than most
Because the capital equipment and the consumables come through the same door and often from the same supplier, and because the ratio between them is unusual. A line runs on machines that are individually modest, numerous, moved between lines, and occasionally cannibalised for parts.
That last habit is the one that breaks most systems. A machine comes off the line, its motor goes into another machine, and the carcass sits in the corner. Was that an asset disposal? A stock receipt? Both? Neither?
| The event | What the system supports | What you have to decide |
|---|---|---|
| A boxed machine is issued to the floor | Stock issue plus asset creation, linked, on approval | Who approves — the conversion inherits the adjustment approval, so the person who can approve an issue can create an asset |
| A machine moves between lines | Asset movement, recorded with custodian and location | Whether a line counts as a location in the register or just a note |
| A part is taken off a machine | Nothing automatic | Whether the part re-enters stock as a receipt, and at what value — there is no reverse conversion |
| A machine is retired | Asset retirement, recorded | Whether to post the disposal in accounting too — a depreciation profile carries the book value and posts the gain or loss, but retiring the asset does not post it for you |
| A machine is borrowed from a buyer | Ownership type on the asset | Nothing — this one the register handles properly, and it is genuinely useful in this industry |
The third row is the honest gap. The conversion runs one way. Stock becomes an asset; an asset does not become stock. If you strip machines for parts routinely, that return has to be a stock receipt you raise yourself, valued by a decision rather than by a link.
Getting the boundary right before go-live
Four decisions to make once, in writing
- Set a value threshold and stick to it. Above it, everything converts to an asset. Below it, nothing does, however durable it is. An argued threshold beats a case-by-case judgement, because case-by-case means two people classify the same item differently within a month.
- Decide whether a production line is a location. If it is, asset movements tell you where every machine is. If it is not, the register knows the building and your supervisor knows the rest.
- Write down what happens to a cannibalised part. There is no reverse conversion, so this needs a rule: either it re-enters stock at a stated value, or it does not re-enter at all and the asset is retired whole. Both are defensible. Silence is not.
- Put the machines that stop a line on a preventive schedule. A schedule opens the work order when the service falls due and the work order records when it was done, what it cost and how long the machine was off the line. Intervals run on the calendar, so for a machine rated in running hours, set the interval from the weeks those hours take on your shifts. Calibration dates are not held, so plan for those outside the register or raise them as a requirement.
Three questions about the stock-to-asset boundary
Issue a unit from stock and make it an asset, in front of me, in one flow.
A good answer sounds like
One action, two records, a visible link between them.
What it actually means
Most inventory systems make you do this twice, by hand, with nothing joining the two. Then a stocktake and an asset verification disagree and nobody can say why.
What happens if the issue is never approved?
A good answer sounds like
No asset is created.
What it actually means
The alternative is a register that fills with equipment that was requested and never went anywhere.
Does the asset register hold a service schedule?
A good answer sounds like
A straight yes or no, then what it runs on.
What it actually means
Ours is yes, on the calendar: a schedule opens its own work order, and the hour meter is not read. This is the single most over-claimed capability in asset management software, so ask which clock it runs on.
What AWRA OpsHub does today
- A one-step conversion from a stock issue to an asset, recorded as its own linked record holding the adjustment, the issue line, the source stock row, the item and the resulting asset.
- The asset finalised on approval of the adjustment, so an unapproved conversion leaves nothing behind.
- Ownership type on every asset — owned, leased or borrowed — validated on creation, update, conversion from inventory, the API and bulk import.
- A working serial number, custodian, location and a nine-action movement history on the asset side.
- Asset labels, verification and retirement, with who and when on each.
- Preventive schedules on the asset, on a fixed calendar or from the last service, opening work orders that record labour, parts and other cost and the downtime they caused.
- Book depreciation per asset in accounting — straight line or reducing balance, a useful life and a salvage value — posted to the ledger monthly, with disposal and its gain or loss.
More we can add to your workspace
- A reverse conversion. An asset cannot become stock again; a cannibalised part re-enters stock only as a receipt you raise and value yourself.
- Running-hours readings and schedules that fall due on them, calibration records, and a utilisation figure per machine.
- Depreciation defaults per asset class, so a machine converted from stock picks up its method and useful life without a profile being set by hand.
- A depreciation disposal posted when an asset is retired, rather than as a separate step in accounting.
- Component accounting — an asset is one record, not a parent with replaceable children.
- An equivalent of ownership type on the stock side of the line.
Where we point you to a specialist
- This is one of the joins that works. We publish a great deal about the ones still to be built, and it would be misleading to leave the impression that everything here is outstanding.
- The conversion inherits the adjustment's approval, which means asset creation is gated by whoever can approve a stock issue. That is a role-design decision you should make deliberately.
- This is market-neutral. It is the arithmetic of a plant that buys its own equipment; this is simply where our reader is most likely to be running one.
What we can build for your market on top of the standard product
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point for your market, not a limit on what AWRA OpsHub can do there. Kenya's eTIMS integration and its maintained payroll engine are in the product because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a tax authority pipeline, a local-language interface, a bank or mobile money feed, a statutory return format, a rule specific to how your operation runs, or a link to a system you already have is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
Tax authority pipelines and reporting
Electronic invoicing against your authority's published interface or its accredited network, with retries, a failure queue and a daily report of sales that never reached it. The regimes here range from a live clearance model to a purely voluntary scheme, so this is one build per country and we will say which country rather than sell an ASEAN integration that does not exist.
Local-language interface, banks and wallets
Interface text and document templates in the language your finance floor and your statutory documents actually require, plus real-time payment collection, e-wallet settlement and bank statement feeds wired into the Payments Register.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
Payroll and statutory returns
Social security, provident fund and withholding computed on live records, with the contribution files produced in the layout each agency expects and any statutory bonus accrued through the year rather than found at the end of it.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedOur position
If your equipment arrives through the same door as your consumables, this join is worth having and it is properly built — use it, set a value threshold on day one, and write down the cannibalisation rule before somebody needs it. Give the machines that stop a line a preventive schedule once they are assets. If what you actually want is maintenance planned on running hours, that part is still to be built, and the register will not become it by being filled in carefully.
Draw the line before you load anything
The value threshold and the cannibalisation rule take an hour to agree and are painful to change once there is history. We will go through both with you against your own equipment list.
Agree the boundaryFrequently asked questions
Can I convert several units at once?
The conversion is tied to the issue line it came from, so the shape follows how you issue. Plan the issue around how you want the assets to appear rather than converting first and tidying up afterwards, because there is no reverse path.
Does the asset keep the stock cost?
The conversion carries an asset payload captured at the time, and the asset then holds its own cost rather than tracking the item's weighted average. That is the correct behaviour — an asset's cost should not move because you later bought more of the same item cheaply.
What about equipment a buyer lends us?
That is exactly what ownership type is for, and it is one of the few places where the product is stricter than most: an asset is owned, leased or borrowed, and the value is validated on every path that creates or edits one. Borrowed equipment is a first-class record rather than a note.
