Back to Blog
Digital Transformation

A Ninety-Day Roadmap for Digitizing Your Factory: Where to Start and in What Order

Origami TeamEditorial Team
7 min read
A Ninety-Day Roadmap for Digitizing Your Factory: Where to Start and in What Order
Like what we publish? Pin Origami as a preferred source on Google.Add as a preferred source on Google

A Ninety-Day Roadmap for Digitizing Your Factory: Where to Start and in What Order

Part six connected the invoice to the issue transaction, completing the six pieces: the accuracy gap, scanning, the production order, the reorder point, lot traceability and the invoice link. But knowing the pieces is one thing and assembling them is another, and this is exactly where most projects fall over.

The common failure is not that the owner chose the wrong tool. It is that they started in the wrong place. They start from reports before there is any data to feed them, or from invoicing before an item has a single code, or from all of it at once, so operations stall for a week and everyone quietly returns to paper. Sequence is not an organisational detail. It is the difference between a system that lives and a system that is bought and then abandoned.

Before day one: the numbers that make progress visible

Before you buy or switch on anything, take one week to record a baseline. The reason is purely practical: in three months you will need to know whether operations genuinely improved or whether you simply got used to the new normal. Without a number for before, there is no number for after.

  • Stock accuracy on a sample. Pick twenty of your fastest-moving items, compare the system balance with a physical count, and record the share that matched exactly. This is the same exercise described in part one.
  • Stockouts on critical items. How many times last month did a line stop or an order slip because a material recorded as available was not there.
  • Emergency purchase orders. Urgent buying at a higher price is the direct financial trace of weak accuracy.
  • Stocktake downtime. How many days the warehouse closes or issuing halts when you count.
  • Duplicate codes. How many items you suspect are recorded under more than one code or description.

Write those five on a single page and put it aside. You need no system to capture them, and you will not be able to capture them retroactively once everything has changed.

The first thirty days: items, codes and the opening count

The first month contains no automation and no new screen for anyone on the floor. It is a month of putting data in order, and it is the month everyone wants to skip because it does not feel like progress. Skipping it means you will automate the mess instead of fixing it.

  • One code per item. Merge duplicates, retire what has not moved in years once verified, and fix a single naming rule that does not depend on one employee's memory.
  • Settled units of measure. One base unit per item, with a defined relationship between pack, piece and carton. In most factories this, not theft, is the source of the majority of count variances.
  • Defined locations. Main store, raw materials, work in progress, quarantine and inspection, and the scrap area. Movement between undefined locations is exactly where quantities disappear.
  • A full opening count. A complete physical count that becomes your zero point. Any system that starts from a wrong opening balance inherits the error permanently and loses everyone's trust by month two.

There is one completion test for this stage: open the item file and find no duplicate item, no ambiguous unit of measure, and no balance that is no longer real.

The second thirty days: warehouse movement on the scanner

Only now does a device reach the warehouse floor. The goal this month is not reports or costing, but capturing every movement at the moment it happens: the five movements detailed in part two, namely receiving, put-away, issuing, transfer and cycle counting.

  • Start with receiving and issuing only. They are the two gates quantity enters and leaves through. Controlling those two alone closes the largest share of the gap before anything else.
  • Print the labels before go-live. A scanner is meaningless when half the items carry no barcode. That is preparation work for month one, not for launch day.
  • Shut down the parallel paper route. As long as issuing is possible with a slip, it will happen with a slip. Running both is the single biggest cause of failure at this stage, because it hands everyone an escape hatch under pressure.
  • Replace the annual stocktake with cycle counting. Count a small sample weekly, weighted by item importance, instead of closing the warehouse once a year. Errors then surface in days rather than twelve months later.

At the end of this month, re-measure stock accuracy on the same twenty items. The difference between the two figures is the project's first tangible return, and the number that convinces management to keep going.

The third thirty days: production orders and the invoice link

Now that stock reflects reality, you can build on top of it. This month adds two layers that depend entirely on the accuracy beneath them, which is why they come last rather than first.

  • Bills of material and production orders. Define each product's components, then run production orders through their stages, and record scrap and losses as transactions rather than notes. Actual cost per order against planned cost then becomes visible, and that number turns pricing into a decision instead of a guess.
  • Reorder point and safety stock. After two months of recorded movement you finally hold real consumption and real lead times, the two inputs without which any reorder formula rests on estimation.
  • Sales order to issue to invoice. As explained in part six, the invoice is generated from the issue event, with returns and credit notes handled explicitly. On compliance, the only reference here is what the Zakat, Tax and Customs Authority publishes.
  • Lot traceability where your sector requires it. In food and pharmaceuticals it is a requirement rather than a refinement, and the reference for it is the Saudi Food and Drug Authority.

After ninety days: the indicators you run operations with

The end of ninety days is not the end of the project but the start of managing by numbers. Five indicators are enough, read monthly on a single page:

  • Stock accuracy. The share of items where the system balance matched the physical count. This is the parent indicator, and everything below it loses meaning if it drops.
  • Inventory turnover. How quickly stock converts into sales, and which items are tying up capital with no return.
  • Stockouts on critical items. The number that measures inventory's effect on continuity of production and delivery.
  • Value of slow-moving stock. Whatever has not moved within a window you set for your own business. Leaving it undecided means financing goods you are not selling.
  • Actual versus planned cost per production order. A recurring gap in one direction is never coincidence: it is either mispricing or invisible waste at a specific stage.

Five numbers an owner reads in two minutes are worth more than a thirty-page report nobody opens.

The part most projects fail on: people

A storekeeper who has worked fifteen years from a ledger does not resist change because they are against progress. They resist because the ledger never exposed their mistakes to management and the system exposes them instantly. That resistance is predictable and legitimate, and it is handled with four practical things:

  • Make the new way lighter, not heavier. If recording an issue by scanner takes longer than writing it on a slip, the system loses.
  • Train on the exceptions, not the normal case. Anyone learns standard receiving in an hour. The real questions are what to do when a short quantity arrives, or an item has no label, or a return comes back damaged.
  • Separate error from punishment in the early months. If the first consequence of transparency is being held to account for old variances, everyone will learn to hide the gap rather than record it.
  • Name a single owner. Someone inside the factory with authority to decide, not an outside vendor and not a committee.

The Origami view

In the industry and warehouses sector we usually refuse to start from screens. Our first session measures the accuracy gap and puts items and codes in order, because a system built on unreliable data produces reports that are elegant and wrong, which is more dangerous than having no reports at all.

The sequence we recommend is the one above: data, then movement captured as it happens, then production, costing and connected invoicing, then indicators to run operations with. And we would rather have one stage genuinely working than four stages half working, because what convinces a team to keep going is not a presentation but the first number they watch improve.

Closing the series: back to the first question

This series opened with one question: why does recorded stock never match the shelf? After it came scanning, the production order, the reorder point, lot traceability, the invoice, and today, sequence. Look back at the last six and you will find they are all branches of that first question: no accurate cost without an accurate balance, no sound reorder point without recorded consumption, no lot traceability without documented movement, and no matching invoice without a recorded issue.

So the real measure of a digitization project in a factory or warehouse is not the number of screens or the size of the reports. It is a simple answer to the same question after ninety days: has the system's number become the number you trust without walking to the shelf to check? When the answer is yes, everything that follows is improvement rather than rescue.

Sources

#Make the Most of Tech#Factories and Warehouses#Digital Transformation#Operations Management

Frequently asked questions

Where do I start digitizing my factory?+

With the data, not the software. The whole first month goes to giving every item a single code, settling units of measure, defining locations, and then running a full opening count that becomes your zero point. Any system that starts from a wrong opening balance or duplicated codes inherits the error and loses the team's trust quickly.

Why does the order of implementation matter so much?+

Because each layer depends on the one beneath it. You cannot cost a production order accurately while the raw material balance is wrong, cannot set a reorder point without genuinely recorded consumption, and cannot issue a matching invoice without a recorded issue transaction. Starting from reports or invoicing before inventory is under control produces numbers that are elegant and wrong.

Which indicators should I run the factory on after digitizing?+

Five are enough, read monthly on a single page: stock accuracy, inventory turnover, stockouts on critical items, the value of slow-moving stock, and actual versus planned cost per production order. Stock accuracy is the parent indicator, and if it falls the rest lose their meaning.

How do I handle resistance from the storekeeper and supervisors?+

Start by recognising that the resistance comes from the ledger never exposing their mistakes while the system exposes them immediately. Make the new way faster than the slip rather than slower, train on exceptions such as a short delivery, an unlabelled item or a damaged return, separate error from punishment in the early months so nobody learns to hide variances, and name one project owner from inside the factory.

Follow Origami in Google

Pin Origami as a preferred source and our articles will surface first for you in Google Search and Top Stories.

Add as a preferred source on Google

Related articles

Weekly newsletter

The latest articles that matter to business owners, once a week. Just your email.

Have a project in mind?

We build custom systems, apps and websites for your business. Tell us your idea and we will give you a straight answer on it.

One session. Twenty minutes. No commitments.