Manufacturing in NearSync and why it matters

Manufacturing is live in Commerce HQ. You can write down how a product is made, run production against it, and see the cost sitting on the factory floor while a run is open.

This post explains what it does, how the pieces fit, and why we built it at this point rather than later.

What manufacturing in NearSync does

Making things is two separate jobs, and the module is split the same way.

Recipes record how a product is made. What one run consumes, what it yields, and what the labour costs.

Runs are the making. You open a run against a recipe, start it, and finish it.

Keeping them apart matters more than it sounds. A recipe is a template, and opening a run takes a copy of it. So when you change a recipe next month, every run you already completed keeps the costs it was actually built with. Your history does not silently rewrite itself because someone corrected a quantity.

How recipes work

A recipe names an output and a yield. One run of this makes twelve of that.

Against it sit component lines. Each line names a variant, a quantity per run, and an expected scrap percentage, because most processes lose a predictable amount of material and pretending otherwise makes every run look like it overspent.

A recipe also carries a conversion cost, which is the labour and overhead of doing the work. Without it, a manufactured item appears to cost only its parts, which understates it and quietly overstates your margin.

How a production run works

A run is two events with a gap between them.

Starting consumes the components. They leave stock at the moment work begins, because that is when they are actually gone.

Finishing produces the goods. The output enters stock, valued at what the run consumed plus the labour.

Between those two events the value has to be somewhere. It is not components any more and it is not finished goods yet.

Why work in progress is tracked separately

That gap is work in progress, and NearSync tracks it as its own figure.

If you have three runs open, the screen tells you how much value is sitting in them. That is money you have spent, that is not on a shelf and not yet sellable. Businesses that do not track this are usually surprised twice: once at month end when stock is lower than expected, and again when finished goods arrive at a cost nobody planned for.

The manufacturing screen leads with shortages for the same reason. The expensive mistake in production is starting a run you cannot finish, because the components are consumed the moment you start and the half-built output sits on a bench until the missing part arrives. Showing what a shortage would cost before you start is worth more than showing it after.

What happens when a run yields less than planned

You planned twelve and got ten. The two you lost do not disappear from the accounts.

The cost of the run is unchanged, so the same total divides across the units you actually got. Your ten units each cost more than they would have. That is what really happened, and it is the number you need when you price the thing.

Why scrap is separate from moving stock

These get confused constantly, and they are different questions.

Moving stock is a location question. Goods in, to a shelf, to a picking location. The quantity is the same, the value is the same, and nothing posts to your accounts.

Scrapping is a value question. The units are destroyed on purpose. They are gone, and their cost has to leave the balance sheet and land in the profit and loss, because you paid for something you no longer have.

So scrap is its own operation with its own name and its own posting. It is not a transfer to a bin that happens to be a dead end.

How manufacturing connects to purchasing and stock

Manufacturing is not a separate island in NearSync, which is the reason to have it here rather than in a second system.

Components are the same variants you purchase. When you receive goods against a purchase order, that receipt is matched against the order and the supplier bill, so what you were charged is checked against what you ordered and what arrived.

Stock on hand is a consequence of the movements rather than a number someone maintains. Receipts, transfers, runs, scrap and sales all post movements, and the quantity you see is what those add up to. There is no separate stock figure that can drift away from the ledger, because there is no separate figure.

Barcodes and serials run through the same records. A code is a row, and a scan is evidence attached to a real movement rather than a lookup that leaves no trace.

Why we built this for UAE businesses

Most businesses making things here are not large enough to run a dedicated manufacturing system, and the ones they can afford tend to be inventory tools with production bolted to the side. So production gets tracked in spreadsheets next to accounting software that knows nothing about it, and the cost of a manufactured item is worked out by hand, occasionally.

That is the gap. Not the businesses running a full manufacturing suite, who are served. The ones making real products, carrying real stock, and costing it in a spreadsheet because the alternative was priced for someone larger.

Because manufacturing sits with purchasing, stock, invoicing and tax in one system, a finished unit already knows what it cost to make, and an invoice for it already knows how it should be taxed. That is the part a second system cannot give you, whatever it costs.

Commerce is in Alpha

Worth saying plainly: Commerce HQ is marked Alpha in the product, and manufacturing is part of it. It is in daily use and it is still moving. Screens changed underneath people this month as counting, codes and reservations landed.

If you are running production and want to try it, we would rather hear what breaks than have you find out quietly.