Witify Logo Witify Logo

An order comes in. A finished product ships.

Statim ERP is the management software Witify develops for manufacturers. Sales, purchasing, inventory and production in a single system, from the office to the operator’s station.

Product
Sector
Witify product, manufacturing ERP
Technologies
Laravel, Vue, TypeScript, MySQL

01 The numbers

Five figures, and where they come from

Nothing here measures a company. These are rules and settings of Statim as it stands today.

  • 21

    features switched on or off, one company at a time From inventory to manufacturing, each has its own switch.

  • 5

    quantities tracked for every item On hand, committed, expected in, expected out, in production.

  • 8

    stations on the production floor Three to decide, five to observe.

  • 6months

    planning horizon for materials By day or by week, item by item.

  • 5min

    between two automatic inventory checks Four checks run every five minutes, a fifth one every night.

Read in the released version of Statim on November 13, 2026.

02 Origin

An ERP for small manufacturers

Statim is built for manufacturers who produce to order or to stock: cutting, welding, assembly, finishing. The office, the floor and the customer all work from the same data.
  1. The office Quotes, orders, purchasing, invoicing and inventory.
  2. The floor Bills of materials, work orders, tasks and each operator’s time.
  3. The customer A portal to place orders and follow them.

03 One order

From an order to a finished product, with nothing typed twice

Let’s follow order SO24180: twelve carts to build. It ties up twelve carts nobody has yet, becomes a work order that reserves the parts, reveals the part that will run short and lands on the welder’s screen.

01 The order

Twelve carts ordered, none in stock

The office accepts order SO24180. From that moment the twelve carts are committed and the cart’s available quantity drops to −12. The line shows what has been delivered, invoiced and manufactured; one button converts the order into a work order.
Fig. 01 An accepted order, with its dated steps

02 The work order

Four operations, each with its parts

Work order WO24512 is built from the bill of materials: cutting, welding, painting, assembly. Accepting it reserves the materials of every operation; those of a finished operation move into production. Worked time shows beside estimated time.
Fig. 02 The tasks of a work order in progress

03 The shortage

28 casters short on Tuesday. They arrive Thursday.

Assembly needs 48 casters; 20 are on hand. The item’s prediction shows the balance day by day: below zero on Tuesday, back above it on Thursday with purchase order PO24077.
Fig. 03 The inventory prediction of an item, over two weeks

04 The shop floor

The welder starts his task, the clock runs by itself

Each operator sees his own tasks. He starts one and the timer runs; once the work is done he submits it, and a supervisor approves it before the task is completed.
Fig. 04 An operator’s tasks

05 The cost

Completed: actual cost beside the estimate

The twelve carts go into stock, the materials come out of it. Material, labor and overhead show actual against estimated: $1,909.00 against $1,944.00.
Fig. 05 A completed work order and its costs

04 Inventory

Nobody types in the stock. It is the sum of the movements.

On hand, committed, expected in, expected out, in production: five quantities per item. Stock is the sum of the movements, and every movement points to the document that caused it. A physical count posts a difference, never a new number over the old one.
Fig. 06 An item’s record: its quantities, and the document behind every movement

05 The floor

Three stations to decide, five to observe

The production floor brings eight stations together. The blue ones change what the shop sees on its tablets. The green ones only show.

Overview

Eight stations, two colors

Blue: what you change reaches the shop floor tablets within a minute. Green: you look, nothing moves.

Task priority

The queue order at each work center

The planner sets the order of the tasks at each work center.

Resource scheduler

Each operation to whoever can do it

A person or a machine, depending on the capability required.

Materials

What is missing, work order by work order

Work center by work center, what is in stock and what is missing: here, 28 parts at final assembly.

06 The modules

Twenty-one switches, one company at a time

Each company works in Statim under its own name and logo, in French or in English. It switches on the features its plant needs and leaves the others aside.
Fig. 07 Statim’s features, switched on or off for one company

07 Our choices

Three choices so that one ERP can serve different plants

Three decisions mattered more than the others. For each: the risk to avoid, what we chose, and what every company gains from it.

  1. Switches, not one version per client.

    The risk
    One copy of the software per company: every fix has to be made everywhere, and the copies end up drifting apart.
    Our choice
    A single version of the software, its features switched on one company at a time.
    The gain
    Every improvement to Statim serves every company that uses it.

  2. No screen edits a quantity.

    The risk
    A stock figure anyone can overwrite: nobody knows why it changed any more, especially when two people work at the same time.
    Our choice
    Every document writes a movement, and stock is the sum of the movements. Even an adjustment writes a movement. One change at a time per item; when the past changes, the cost is recalculated.
    The gain
    Every unit is explained by a document, and the margin follows the true cost.

  3. Deciding and observing on separate screens.

    The risk
    A dashboard where everything can be edited: one careless gesture changes what the shop floor sees.
    Our choice
    Three stations change the floor, five only show, and every screen says which kind it is.
    The gain
    People look without worry, and know where to act.

08 Under the hood

What Statim is made of

Statim is a web application. Here, in short, is what it is made of.
Application
Laravel, Vue, TypeScript, PHP, Tailwind
Data
MySQL, Redis, Horizon queues
Interfaces
Five applications on one back end, office, customer portal, employee portal, shop floor kiosk, customer sign-up
Integrations
QuickBooks, Shopify, card payments, AI document reading, email
Inventory
Stock as the sum of movements, history replayed when the past changes, one lock per item, five scheduled integrity checks
Quality
Over 4,000 automated tests, static analysis

Does your ERP make you work its way?

Thirty minutes to follow one of your orders through Statim, from the sale to the finished product.

Or write to us
Next case study Distribution MA Read the case study

Names and figures shown in the interfaces are examples.