PER FACILITY, PER MONTH.
The unit is the facility you run, not the people who work in it.
One monthly price per facility, by edition. We publish the model here, not the numbers.
/MODEL
Per facility, per month, in editions. Cargo owners sign in free. Onboarding is a fixed scope with a stated list of what is in it. Digimesh is unpriced for now.
The unit is the facility you run, not the people who work in it.
An edition is a bundle of capability: the floor, the client views, the network.
A 3PL's clients are its customers, not its seats. Their logins are not counted.
A written scope, agreed before work starts, with a list of what is in it.
Exchange across companies is a planned edition and is not priced in the first sessions.
Design-partner terms are written down before any data is shared.
/EDITIONS
What each includes, described by what it does, without a price. The edition names are not final, so we do not print them.
| EDITION | WHAT IT INCLUDES | STATE |
|---|---|---|
| FIRST: THE FLOOR | The first edition covers one operator's floor, from receiving to shipping. | DESIGNED |
| SECOND: CLIENT VIEWS | The second edition adds client views and the billing hand-off to the first. | DESIGNED |
| THIRD: ACROSS COMPANIES | A third edition covers cross-organization exchange through Digimesh. It is not priced in the first sessions. | PLANNED |
/WHO IS NOT COUNTED
Client logins do not count toward the price. What you pay for is the facility.
In that example the facilities are the unit. The client logins are free, and each is scoped to its own client's records.
DESIGNED/ONBOARDING
Onboarding is a fixed-scope fee, agreed before work starts.
Which facility the work covers, and which are out.
Which clients are loaded first, and what each one's feed looks like today.
The items, orders and exports that will be loaded, and who on each side owns them.
Who owns receiving, inventory and finance on each side, and who decides.
Anything not named is not in the fee, so a change is a conversation before it is work.
/COMPARE
Published 3PL price lists tend to share a few shapes. This is where DigiOS stands against each one, in words, without a number.
| SHAPE | HOW IT BEHAVES | DIGIOS |
|---|---|---|
| PER NAMED USER | Hard to predict when floor labor is seasonal and shifts turn over. | The facility is the unit, not the person on the floor.DESIGNED |
| PER ORDER OR DOCUMENT | A toll that grows with your clients' volume. | Digimesh is not priced in the first sessions.PLANNED |
| CLIENT LOGINS | Free in most 3PL plans, and capped by tier in some. | Free, and scoped to each client's own records.DESIGNED |
| QUOTE ONLY | Enterprise plans are priced after a sales process. | We publish the model, not numbers.— NOT CLAIMED |
/FAQ
A price discovered at renewal is a price you could not plan around. A model you can read before you sign gives your own finance team something to forecast. Published is the difference between a cost you can plan and a cost you find out.
No operation pays for DigiOS yet, so a published price would be a guess. The model is real: per facility per month, in editions, with cargo-owner sign-ins free and onboarding at a fixed scope. Design-partner terms are on request.
No. Cargo-owner users are free and scoped to their own records. You pay for the facility, not for each person your clients invite.
Not in the first sessions. Exchange across companies is a planned edition, and it is not priced until it exists.
That is set in design-partner terms, written down before any data is shared. Ask for them in a session.
Tell us the facilities, the clients and what runs your warehouse today. We reply with the terms and the scope, in writing, before anything starts.