What works today.

A count shows the difference; a small difference corrects itself within the tolerance you set and a larger one waits for a named person

A print job shows whether it printed, failed or is unknown, nothing is resent on a guess, and a reprint is an explicit action from the print queue

When the link returns, each offline scan is checked against what changed; a moved bin or held stock goes to the supervisor with the reason; a revoke is the cut-off, nothing is lost silently

Inventory is one book per client: on hand, available, reserved and on hold, kept separately for each client

Stock can be put on hold and released with a name; a temperature excursion in a zone puts that zone's stock on hold

Ownership transfers and write-offs of stock are recorded against both ledgers and wait for approval of the exact quantity

Two clients can use the same barcode without their stock mixing

Stock by location: the warehouse map, each pallet and where it is, and every move between locations

Opening a load, scanning containers on and closing it hands the stock to the carrier and completes the order, and the client is told what shipped

A task sends the operator to a location and the scan confirms it; confirming a task step posts the stock move into its new place

Each pallet is scanned and checked against its notice; the board shows matched, short, over and damaged; received stock that has not cleared cannot be picked; a count over tolerance is recorded and shown, not turned away at the door

Customer-furnished material is kept apart from your own and shown only to the customer it belongs to, with stock by lot and location on one screen

A part is held until a named person releases it; the first article package stays in your quality system; every hold and release carries a name and a time

A kit is picked by scan and the person who pulled each line is on it; a short, damaged reel or wrong part goes to a named person

A receipt stays on inspection until a named person releases it, and the release is tied to exactly what they looked at

The handheld runs receive, put away, pick, replenish, count, pack, load and move jobs (and fetch from a robot)

Each person gets the next job on a handheld (where to go, what to scan, how many) and a scan finishes it and brings the next one

The scan is the confirmation, so nobody types a quantity into a rack

The task board shows every operator, their current job and anything waiting; a supervisor can reassign a job without leaving the board

Items are tracked by lot and serial number kept against the item, every pallet and carton by LPN, products scanned by GTIN

Cartons, carrier labels and tracking are saved to the order; a scale at the pack station confirms weight, a dimensioner confirms size and a print-and-apply labeler labels the carton

Pick by scan: item, location and quantity on the handheld; scan to confirm; flag a short without leaving the screen

Order lines queue, are released to the floor, and trigger a replenishment when a pick face runs low

The carrier books a door and a window against the order, and a missed window shows on the board

The client sees the receipt as it is made, with any short or damage, and approves what touches its stock

A receiving day from notice to client view runs as seven steps across dock board, handheld and client view

Advance notices arrive by screen or API and sit on the dock board as expected; retailers' and clients' own formats arrive through Client Link

A shortage flags, drafts a request to close the line short for exactly one pallet, a person approves it, and it runs once

Two clients' pallets can arrive on one truck and each is received against its own client's notice; a receipt is seen only by its client and your team

DigiWarehouse takes a pallet from advance notice to carrier handoff: receive, store and count, pick, pack and ship

Charges for receiving, storage, handling and value-added work are captured from each client's work as it happens

Clients get owner-scoped statements with drill-down to the work behind each charge

Statements and charges export to your accounting system

A 3PL sets rate cards per client

When the Wi-Fi drops, handhelds keep taking scans, which wait on the device and show as waiting

CSV files: Items, locations, stock and open orders in from any file with columns.

Extensiv 3PL Warehouse Manager: Items, locations, stock and open orders in from the system you run today, to run beside it.

ShipHero: Products, stock and open orders in from the system you run today, to run beside it.

A charge is raised against the order it came from and points at the receipt, putaway and other work that earned it, so a client asking what a line is gets the work behind it

A 3PL onboards a client in four steps: add the client and its users, load its items and locations, connect its orders, and run beside current process until both agree

Your current warehouse system keeps running beside DigiOS; DigiOS takes in items, locations and open orders for the client or site you start with and lists every difference

DigiOS exchanges orders, charges, invoices and customers with your ERP, accounting system and storefronts and marketplaces, and tracking and stock back

Defense traceability: a C of C attached to every receipt, lot and serial traced from receipt to the job, IUID item identification and DataMatrix marks read at receiving and in the stockroom

Parcel and DTC shipping: storefront orders come in, and rates, labels and tracking go out through your own carrier accounts. DigiOS is built for pallet and case 3PLs with many clients and retailer EDI.

Carrier and parcel-shipping systems exchange labels, rates and tracking with DigiOS

Kitting by scan, light assembly at a station and value-added services (labelling, bundling, rework) run against the work order

A finished product is traced back to its lots and operators and forward to the orders that received it

An assistant drafts a screen from a request and an engineer approves it before it goes live

Operator screens have a phone list view and a wall display

A screen builder places widgets bound to readings, and a published screen changes only through approval

Standard operator screens (overview, area, equipment, faceplates, trends, alarm summary) are generated from your equipment list

One model of sites, areas, lines and equipment following ISA-95

Each reading is tied to its order, lot, operator and location

The model and its readings are published to a unified namespace over MQTT on the ISA-95 path, with Sparkplug B at the device edge

An automation or an AI assistant can draft a change but cannot approve it; a person with the right access does, both names are kept, and it never has more access than the person it acts for

A lookup that touches another client's pallet is refused without saying whose it is

A write-off, cancelled order or ownership transfer waits in an inbox for the person who owns the decision; clients approve what touches their own stock

Each client's items, orders, stock and activity belong to that client; another client's pallet, scan or price never appears on its screens

A write-off, ownership transfer or cancelled order waits for a named person to approve the exact change

Every scan, change and approval shows who did it, on whose behalf and when; nothing is overwritten and a correction is a new entry that points at the one it fixes

Give each client a sign-in and they see their own stock, orders, receipts and activity as they stand now, and nothing of anyone else's

API and webhooks: DigiOS has a REST API that speaks JSON, and webhooks that tell your systems when something happens on the floor. A REST API with JSON, OAuth client credentials with a token for each client, repeat-safe writes, signed webhooks with retries, and a sandbox for early-access customers.

Clients' and owners' own systems call DigiOS over a REST API in JSON, and DigiOS calls theirs with webhooks when something happens

GS1 identifiers (GTIN for products, SSCC for pallets and cartons, GS1-128 barcodes, GLN for locations and partners) are supported

One live view of every site, client and shift: doors, tasks, orders and exceptions, current to the time shown

What a client sees is the same live view the team works from, limited to its own goods

A short pick, a damaged pallet, a mismatched count or an unclaimed task each lands in one queue with the reason and the person who can act

A live board shows every dock door, task, order and exception as it happens, by site, client or task type, and updates as scans come in

Open any order and see each step it went through (received, put away, picked, packed, loaded), who did it and when

A hold, a release or a scrap waits for a named person, with the exact change shown, in one inbox

Access is held per person and per client with an end date, and nobody has more access than they were given

Planners, supervisors, operators, clients and partners use the same system on the web, each signing in to a screen for their job; no separate portals

An AI assistant (agent) works inside DigiOS: it can prepare changes for a person to approve and answer from the data

Operations managers, shift leads, inventory controllers, client service and quality each land on the screen for their job

Multi-factor authentication is supported at sign-in

SCIM adds and removes users from the customer's directory automatically

Sign-in through the customer's own identity provider using SAML or OIDC single sign-on, for staff and cargo-owner users

Google Workspace: People sign in with their Google Workspace account. Provisioning where Google offers it.

DigiOS runs on iPhone and iPad in the browser; there is no native app

Microsoft Entra ID: People sign in with Microsoft Entra ID. Provisioning adds and removes users and groups.

Okta: People sign in with Okta. Users and groups are added and removed from your directory.

Every board shows the time it is current to

A current browser on a desktop or tablet, and an Android handheld on the floor, with sign-in through your SSO (SAML or OIDC) and MFA

Staff, clients and partners sign in on invitation; you choose who sees which site and which client, and until when

You add your own screens, workflows and reports inside DigiOS (a kitting step for one client, a dock board with the three things your supervisor asks about); additions sit beside what ships and keep working when DigiOS is updated

The same work runs at a desk, on a tablet and on a floor device; a bigger screen shows more

Android handhelds are enrolled through the customer's device management (Microsoft Intune, SOTI MobiControl, Workspace ONE), with DigiOS as a managed app or a kiosk browser

The full privacy notice and terms of use are published

The site runs no analytics and sets no tracking cookies

A working session is 45 minutes on a video call with someone who builds DigiOS, with the screens set up for your floor; a person reads every request and replies by email

The server logs hold a request's id and the topic the visitor chose, never the name, email, company or note

A request typed into the form is not sent to an advertising or analytics service

The working-session request form asks for name, work email, company, role, number of facilities, what runs the operation today, what the visitor wants to ask about and optional notes, and stores the request so a person can reply

IT gets a named list of what connects, what moves and in which direction

You can start with one client, one line or one site beside your current system and stop whenever you choose; nothing in your operation depends on DigiOS until you decide

The 3PL edition includes client billing, raised from the recorded work.

Core covers one owner's goods receiving to shipping; 3PL adds many clients on one floor, with a sign-in for each client and client billing; Network adds Client Link, connections to other companies on DigiOS and connections to robots, lines and machines; each edition is sized by orders and clients, and Client Link can be added to 3PL.

Screens, workflows and connections you add inside DigiOS are part of your deployment, not an extra line; DigiOS is kept current for you

DigiOS is priced per facility by edition (Core, 3PL, Network) and size band, one monthly price per building, and the price follows the facility, not the number of people who sign in.

Client users are free: a 3PL's clients are not charged for their logins

We connect your PLCs and robots with your controls engineer, one line at a time, and reply to the make and model of your equipment with what it would take

DigiFactory is shaped with the first plants that use it: describe one line and we say what it would take

We set up each connection with you and map each client's format once; no developer is needed on your side, and a connection does not change how the floor works

Every session has a named owner on each side, terms are agreed in writing before any data is shared, your data is used only for the agreed scope and returned or deleted when we stop, and we do not use your name without your say

Early access runs in four steps (scope, run beside, pilot, decide) with a written scope, your engineers on your floor, an exit at each step and a full export whenever you ask

Onboarding is a fixed scope, written down first: your items and locations, your client feeds, and one run beside your current process

The price is set with each early-access partner starting from one facility, early-access terms hold for a term, and each partner is told its next-term price in advance

For defense suppliers DigiOS states in writing where it touches DFARS 252.204-7012/-7019/-7020, NIST SP 800-171, SPRS, CMMC, ITAR/EAR, AS9100, AS9102, IUID, lot and serial traceability and C of C, without claiming to satisfy any

A person answers the customer's security questionnaire in writing against how DigiOS is run; clause numbers are answered in writing with which parts of DigiOS touch each

DigiWarehouse is built for pallet and case handling for several clients; if most volume is parcel e-commerce, we will say whether to wait