Skip to content

Inventory and operations management built on one shared record.

We can build a system that tracks items, locations, orders and jobs in one place, with roles for who can change what, alerts before something runs out and reports drawn from the same records. It can replace the spreadsheets and memory holding the picture together today.

Who it is for

Businesses that stock parts or products, or run orders and jobs through several stages, and are tired of counts that disagree.

The problem

When nobody sees the live picture.

Operations run on a few facts: what is in stock, where it is kept, what has been ordered and which jobs are in progress. When those live in separate spreadsheets, supplier emails and one person's memory, everyone works from a slightly different picture.

Counts disagree because every update is typed by hand and nothing records who changed what. Reorders go out late because nobody sees a level falling until it hits zero. Whether an item is on the shelf, or where a job stands, gets answered by walking over to look.

Inventory and operations management keeps one current record of items, locations, orders and jobs, with rules about who may change it, so everyone sees the same picture.

Situations

Where the picture breaks.

Common ways the problem shows up.

  1. Two lists, two answers

    The sales counter and the stockroom keep separate lists. A customer is promised an item already used on another job.

  2. The reorder that comes late

    A supply runs out before anyone notices, because the only warning is someone remembering to look.

  3. Jobs with no status

    A small manufacturer must ask the floor lead which orders are late, waiting on parts or ready to ship.

  4. Edits nobody can trace

    A quantity is wrong and nobody knows if it was a typo, a transfer or a miscount. Without history, the fix is to count again.

Before and after

The path of one part, from the dock to the job.

The same stock and the same jobs, tracked by hand and tracked in one record. The right column shows one way a system can work; each project is scoped to its own needs.

  1. Receiving

    Tracked by hand

    A delivery is checked against a paper slip and typed in later.

    Tracked in one record

    Receipt is recorded against the purchase order, so the quantity updates on arrival.

  2. Locating

    Tracked by hand

    You ask whoever knows where things are kept.

    Tracked in one record

    Every item has a location on its record, and moves are logged.

  3. New order or job

    Tracked by hand

    A note or message, plus a guess about whether there is enough.

    Tracked in one record

    The order checks availability and reserves what it needs.

  4. Running low

    Tracked by hand

    Someone notices a shelf looks thin.

    Tracked in one record

    A level you set triggers an alert or a draft reorder for approval.

  5. Counting

    Tracked by hand

    Each count becomes a new spreadsheet that disagrees with the last.

    Tracked in one record

    A count is compared with the record, and any difference is posted as an adjustment with a reason and a name.

  6. Reporting

    Tracked by hand

    Reports are rebuilt by hand whenever someone asks.

    Tracked in one record

    Stock, order and job views come from the same records, so numbers can be traced back to their source.

What we can build

What goes into an operations system.

The scope follows what you track. Many businesses need only some of these.

  1. Item and location records

    Items with units, variants, suppliers and storage locations, loaded from your existing spreadsheets.

  2. Stock movements

    Receipts, transfers, usage and adjustments recorded as events, so a quantity is the total of what was recorded.

  3. Orders and jobs

    Customer orders, purchase orders or jobs moving through stages you define, with the materials each one uses linked to it.

  4. Roles and permissions

    People can be limited to seeing and changing what their role needs: the counter views stock, the stockroom adjusts it, a manager approves write-offs.

  5. Alerts and reorder prompts

    Notifications when stock falls below a level you set, a job is overdue or a count does not match the record.

  6. Reconciliation and reporting

    Count sheets compared against recorded quantities, approval for each adjustment and views built from the live records, not assembled by hand.

Is it worth it?

Five checks before you replace the spreadsheet.

Answer these for your own operation. They usually make the decision clear.

  1. How often do the numbers disagree?

    If a count is off now and then at little cost, a tidier spreadsheet may do. If it costs you sales or forces rush orders, the spreadsheet is already the expensive option.

  2. How many people change the data?

    One person with a spreadsheet is a habit. Several people editing the same lists is where a shared record earns its place.

  3. Is the item list consistent enough to load into a system?

    A system needs stable names, units and locations. If one item is described several ways, clean-up comes first.

  4. Will the team record changes as they happen?

    A live picture exists only if movements are logged, so recording must be quick enough that people do it.

  5. What does a stockout or a double promise cost?

    Set that against the cost of building and maintaining the system, including the time now spent counting.

If you handle few items in one place and one person knows them, a good spreadsheet and a regular count are the right answer. A system makes sense once several people, locations or stages share the records.

Questions

Questions about inventory and operations.

Straight answers to what people usually ask before a project starts.

Not seeing your question?

Tell us about your business and what you want to change. We will answer directly, and tell you if something simpler would do.

Or write to us at hello@samasadigital.com

01Can you replace our spreadsheet without losing the data?

Existing spreadsheet data can usually be imported. Duplicates and inconsistent names typically need to be sorted out, and it is wise to run the old and new systems side by side before switching. How clean the result is depends on how consistent the spreadsheet is.

02Should we buy an inventory product instead of building one?

Often, buying a product is the better choice. If a product matches how you count, order and track jobs, it is usually cheaper and quicker. A custom build makes sense mainly when your process fits no product, or must connect to other systems in ways products do not support.

03How can the numbers stay accurate once it is running?

A system cannot guarantee accuracy by itself; it can make errors visible. Changes can be logged with who made them and why, counts can be compared with the recorded quantity and differences can require an explanation. Accuracy still depends on people recording what they do.

Which list does the business really run on?

Tell us what you track, who updates it and where the numbers go wrong. We can help you decide whether a tidier spreadsheet, an existing product or a purpose-built system is the right size of fix.

Complimentary preview

See what your business could look like online.

Send us your existing website or business information. We'll create a complimentary homepage concept so you can see what's possible before deciding to work with us.

Request My Free Preview

No commitment. No template.

What to send

  1. 01Your current website or business information
  2. 02What you'd like to improve
  3. 03The kind of customers you want more of