Factora

Factory management software

Run every factory from one platform.

Factora brings factory operations, products, jobs, inventory, stores and operational visibility together in one connected workspace — so teams work from the same record instead of the same guess.

Request a DemoExplore the Platform
  • Factory-level data isolation
  • Products, variants and jobs, linked
  • Role-based access

Already using Factora? Sign in →

The Factora workspace. Figures shown are demonstration data.

The problem

Factory operations should not live in disconnected systems.

Most factories do not lack information. They lack one place to keep it, so the same job is recorded four times and reconciled by memory.

  • Operational data is scattered

    Job cards on paper, stock in a spreadsheet, purchase notes in a chat thread. Nobody sees the whole picture.

  • Progress is tracked by asking

    Where a job has reached, who is on it and which machine it is waiting for are questions answered by walking the floor.

  • Inventory is a guess until it is counted

    Finished goods and store consumables drift from the record, and shortages surface when a job is already halfway through.

  • Every factory is its own island

    A second site means a second set of files, a second set of habits and no shared view across them.

The shift

Factora connects the operation.

One workspace holds the product catalogue, the job cards moving through it, the finished goods coming out of it and the store feeding it — with each factory kept separate in the data and joined in the administration. Nothing is entered twice, and every figure on the dashboard traces back to the record that produced it.

  1. Record it once
  2. See it everywhere
  3. Act on what changed

Core platform

Everything a factory runs on, in one workspace.

Eight connected modules, each built around the record the work actually produces — a job card, a variant, a movement, a person.

  • Multi-factory management

    Run several factories from one deployment. Each carries its own users, master data and operational records, and a switcher moves between the ones you belong to.

  • Products & variants

    A product holds what every version shares; a variant holds what tells one apart — size, finish and any attribute axis you define. Stock and jobs reference the variant, not a free-text note.

  • Job cards & production

    Raise a job card for new production or a repair, route it through its processes, assign workers and machines, and carry notes and a full activity trail alongside it.

  • Finished goods

    Completing a job card writes its good quantity into finished goods. Every product keeps a movement ledger, and per-product reorder points decide what reads as low.

  • Factory store

    Receive, issue, return and adjust store items against a running balance, with a reorder level per item and a dedicated alerts view for whatever has fallen below it.

  • Operational visibility

    A live dashboard of open and in-progress work, urgent jobs, machine load, workforce presence and inventory alerts, with fourteen-day trends read from the records themselves.

    Dedicated reporting in development

  • Role-based access

    A Factory Admin runs their factory and the people in it. Everyone else sees the modules their role is entitled to — and the API enforces that independently of what the navigation shows.

  • Connected records

    A variant on a job card is the same variant in finished goods and in the store. The link is the record, so nothing has to be matched up by name after the fact.

Multi-factory

One platform. Multiple factories. Complete separation.

Tenancy is not a setting in Factora, it is the shape of the data. Every operational record belongs to a factory, and every request is answered in that factory's context or not at all.

  • Centralised administration

    Factories and their people are administered centrally, so opening a site or moving somebody between two of them is a change in one place rather than in two systems.

  • Factory-level data isolation

    Every operational request is scoped to a factory. A request that carries no factory context is refused rather than guessed at.

  • Factory-specific master data

    Categories, processes, machines and parties belong to the factory that defined them. No shared default list imposes one industry's vocabulary on another.

  • Configured per factory

    Each factory carries its own configuration, so a module switched off for one site simply is not in that site's navigation. Anything not explicitly disabled is on.

  • Scalable by design

    Adding a factory is a record, not a second deployment. One application, one upgrade path, however many sites.

How it works

From a catalogued part to a number you can trust.

Each step writes the record the next one reads. Select a step to see what it carries.

Product

Product master

A product carries what every version of it shares — its part number, category and unit of measure — plus a reorder point of its own when stock is not held on variants.

Operational visibility

See what is happening across your operation.

Faster decisions come from fewer places to look. The dashboard reads back the same records the shop floor writes, so nobody has to compile a status before a meeting.

  • The floor, at a glance

    Open, in-progress and urgent job cards, free workers and free machines, and what is waiting for handover or dispatch — the four questions a shift starts with.

  • Load, not just counts

    Machine load splits work in progress from what is queued behind it, so a bottleneck reads as a bottleneck rather than as a busy machine.

  • Alerts against a threshold you set

    Finished goods and store items read Low or Out against their own reorder point, per product and per variant — not one flat number across the whole catalogue.

  • Trends from the records themselves

    Fourteen-day movement trends are derived from record timestamps. Where the data does not support a trend, no line is drawn rather than a flat one implying calm.

  • A dedicated reporting area — production, inventory and workforce reports — is in development. What is described above is on the dashboard today.

Products & variants

One product. Every version of it, structured.

A product holds what all its versions share. A variant holds what tells one apart — and it is the variant that job cards, finished goods and store items point at.

Attributes you define
Size and finish are promoted to their own columns because they are what people filter on. Beyond those, any attribute axis your catalogue needs — material, grade, length, packaging — is a key you add.
Codes that reach the shop floor
Each variant carries a stable code, whether the manufacturer printed it or Factora generated it. That code is what appears on the job card, not a description someone retyped.
Stock where it belongs
A product with variants holds its balances on the variants, so a reorder point can differ between a 96mm black and a 192mm chrome. A product without them keeps its own.

Profile Handle V1

PH-V1 · Handles · PCS

Variants
4
On hand
1,598
In use by
6 jobs

Variants

CodeSizeFinishOn handReorder atStatus
V1-09696 mmBlack1,240200In stock
V1-128128 mmBlack310200In stock
V1-160160 mmChrome48150Low
V1-192192 mmChrome0100Out of stock

The same variant codes, carrying their own balances in finished goods.

Security & access

Separation you can point at, not just promise.

Access control in Factora is structural. Factory scope and role are enforced by the API on every request, independently of what any screen chooses to show.

  • Factory-level isolation

    Operational data is scoped to a factory on the server. A request without factory context is refused, not defaulted.

  • Role-based access

    Navigation reflects a user's role and the API enforces it independently — hiding a link is a courtesy, not the control.

  • Factory-level user administration

    A Factory Admin manages the people in their own factory and the role each of them holds. That control ends at the factory boundary.

  • Mobile and passcode sign-in

    Sign-in is a mobile number and a passcode, with remembered profiles for a quick return on a shared shop-floor device.

  • Explicit factory context

    A user who belongs to more than one factory chooses before anything loads, so no screen can quietly show the wrong site's numbers.

  • Recorded, not remembered

    Every job card carries a system activity trail — process moves, assignments and changes, each with who made it and when. It is written by the application and never edited by hand.

Factora does not currently hold third-party security certifications, and none are claimed on this page. If a formal assessment is part of your procurement, ask us and we will tell you exactly where things stand.

Every device

The same workspace, wherever the work is.

Factora is built mobile-first and installs as a progressive web app. Screens are recomposed for the device rather than shrunk onto it.

  • Desktop

    Sidebar navigation, multi-column layouts, dense tables.

  • Tablet

    A compact rail, wider touch targets, the same screens.

  • Mobile

    Bottom navigation, cards instead of rows, sheets instead of dialogs.

  • Installed

    A full-screen launcher on a shared floor device, no browser chrome.

Survives a bad connection
The interface shell is cached, so a dropped signal shows empty chrome and an offline notice rather than a dead tab. Factory data is never cached.
Zoom is not locked
Pinch-zoom stays enabled and text scales with the device setting, because someone reading a part number in poor light needs it to.

Who it is for

Built for modern factory operations.

Factora suits operations where work is raised as a job, routed through defined processes and ends as counted, catalogued stock.

  • Manufacturing

    Make-to-order and batch production routed through a defined sequence of processes.

  • Metal & fabrication

    Cutting, forming and finishing work where a job passes between machines and hands before it ships.

  • Components & hardware

    Catalogues that live or die on variants — the same part in four sizes and two finishes.

  • Industrial products

    New production and repair work managed side by side, each with its own completion path.

  • Multi-site operations

    Organisations running more than one factory that need them separated in the data and joined in the administration.

These are the operations Factora is designed for, not a customer list.

Why Factora

Five reasons this is a platform, not another tool.

Each of these is a design decision that was made early and is hard to retrofit, which is why it is worth asking about before you buy anything.

  1. One platform

    Job cards, products, variants, finished goods, the store and the people doing the work, in a single workspace instead of four tools and a spreadsheet.

  2. Built around operations

    The screens follow how a job actually moves — raised, routed, worked, completed, counted — rather than an accounting model with production bolted on.

  3. Multi-factory by design

    Tenancy sits in the foundations, not on top. A second factory is a record in the same system, not a second copy of the application.

  4. Clear data relationships

    A variant on a job card is the same variant in stock and in the store. Records link to each other, so nothing has to be reconciled by name later.

  5. Ready to scale

    Shared architecture, per-factory configuration and role-based access, so growth adds factories and people rather than complexity.

Resources

Common questions.

Short, specific answers about what Factora does today — including where it is still being built.

What does Factora cover today?

Job cards and process routing, workers and machines, products and their variants, finished-goods stock, the factory store, factory and user administration, and an operational dashboard. Dedicated reporting is in development; operational figures and trends are on the dashboard today.

How are multiple factories kept apart?

Every operational record belongs to a factory, and every request is scoped to the factory the user is working in. A user who belongs to more than one chooses before any data loads, and master data such as categories and processes is defined per factory rather than shared.

Who can see what?

A Factory Admin runs a single factory, including the people in it and the roles they hold. Other users see the modules their role is entitled to. Navigation reflects that, and the API enforces it independently — hiding a link is a courtesy, not the control.

Does it work on the shop floor?

It is built mobile-first and installs as a progressive web app, so a phone or a shared tablet gets a full-screen launcher with the same workspace as a desktop browser. Text stays zoomable and controls stay touch-sized.

Can a factory turn modules off?

Yes. Each factory carries its own configuration, and modules switched off for it disappear from that factory's navigation. Anything not explicitly disabled is on.

What languages does the interface support?

English and Hindi, switchable from inside the application.

Ready to bring your factory operations together?

See how Factora can help your teams operate with greater visibility, consistency and control — across one factory or all of them.

Request a DemoLet’s Talk on WhatsApp

Or write tosales@pixnil.comWhatsApp+91 76002 61025