Ordovee
Tech

Inventory work gets complicated.
The record does not need to be.

Counts disagree. Spreadsheets go stale. Marketplaces lag behind the shelf. Items get misplaced. Updates fail without warning.

Ordovee is built around a simple technical rule: when those things happen, the operational record stays understandable. That means one authoritative record, history preserved behind the current state, outside systems kept at the edges, and evidence when people or automation change something.

This is the engineering underneath the workflow — and under the item records and permanent inventory ledger that inventory management keeps.

Accountability

One system to keep your inventory records consistent.

eBay and Shopify are important parts of the operation. They are not the inventory system of record.

Inventory movements, reservations, compatibility records, locations, and workflow state live in Ordovee. Connected marketplaces receive quantities from that operational record.

If a channel begins showing a different quantity than Ordovee expects, that disagreement is treated as drift to investigate — not permission for the outside number to silently become your warehouse count.

The direction matters:

Work happens → Ordovee records it → connected systems are updated from that record.

Not the other way around.

How channel sync works
The Apps dashboard in Ordovee — eBay and Shopify connections, sync health, listing coverage, push-queue counts, and a recent-activity log.
History

See what’s in stock and how it got there.

A warehouse needs the answer to “how many do we have?” immediately.

It also needs an answer to “how did we get that number?” when something looks wrong.

Ordovee keeps both.

The inventory ledger records each add, remove, transfer, and adjustment as its own movement. A current-state snapshot sits alongside it so everyday quantity lookups stay fast.

The snapshot answers:

What do we have now?

The ledger answers:

What happened to get us here?

Corrections become new movements instead of rewriting the old ones. The history that existed before the correction remains part of the record.

How ledger-based inventory works
The Ordovee inventory activity ledger — a history table with the date, the action (add or adjust), SKU, location, quantity and user on every row.
Traceability

Every change recorded, indexed, and retrievable.

Not every change enters the system the same way.

Someone edits a SKU. A CSV import adds hundreds of records. A marketplace sync runs. An inventory movement happens during picking.

Ordovee keeps those paths distinguishable.

Record changes have history. Inventory movements have the ledger. Imports and automated work leave activity records.

So when something looks wrong, the question is not just:

What does the record say now?

You can also ask:

Who or what changed it, when did that happen, and what happened around it?

That history is recorded while the operation runs — before you know you are going to need it.

See how the audit trail works
Three layers of history in Ordovee — Who (the change log: user, timestamp and fields changed), What (the inventory ledger of every stock movement) and Why (activity records of what the system did) — beside the live Inventory Activity screen.
Parts Intelligence

Organize source assemblies and recovered parts in one system.

Parts Intelligence connects recovered parts to their source assemblies and the other makes and models they fit. Those parts use the same inventory records, quantities, locations, and permanent inventory ledger as any other item in Ordovee.

Together, these capabilities support Structured Disassembly Management — the discipline of recovering, cataloging, and selling parts from complete assemblies.

See how Ordovee supports parts recovery
The Ordovee Models Hub open on the 2019 Mac Pro (model A1991), a source assembly with 53 attached parts — an SSD module pair, a CPU and case parts among those listed.
Bad input

Check first. Commit second.

A system of record should be difficult to damage accidentally.

CSV imports in Ordovee use a preview step before anything commits. The file is parsed, problems are surfaced, and you decide whether to fix the data before running the import.

The same philosophy runs through the product: important changes should be explicit and inspectable rather than hidden side effects.

Bad data will eventually show up in every real operation.

The system should give you somewhere to catch it before it becomes your new normal.

See the import workflow
The Ordovee CSV import screen (Items, Create, CSV file tab) — supported columns, a downloadable template, a drag-and-drop upload area, and Preview and Run import buttons.
Flexibility

Use familiar tools. Keep your data portable.

Ordovee runs in a browser.

A phone can scan. A rugged handheld is better suited to repeated, high-volume scanning. Labels are ordinary PDFs that print through the device’s normal print system. Catalog data can be exported as CSV.

The goal is deliberate: use structured software without making the rest of your operation dependent on a proprietary scanner, printer language, desktop application, or closed data format.

Use the hardware that fits the job.

Keep the data you created.

See hardware compatibility
A Zebra TC-series handheld in a warehouse aisle showing Ordovee’s Location Inventory screen for location F-2-05 with seven items, beside the scanned F-2-05 QR label on the shelf beam.
Security

Your data. Your team. Your control.

Each business’s data is kept private to its own account.

Traffic is encrypted in transit. Stored database data is encrypted at rest. Access inside the account is controlled by role so people can be given the parts of the system their work requires.

The audit history provides another layer: when records change, the system retains attribution instead of leaving a shared account with no explanation for who did what.

Security is not a separate workflow for the operator. It is part of the boundaries the application is built around.

Security and account questions
AI

People involved at every step.

We use AI heavily in development: tracing code paths, finding edge cases, drafting tests, and helping us review a system with a lot of connected parts.

Humans still make the product decisions and review what ships.

The development tools we use do not have access to customer inventory, orders, or account data.

AI does not make operational decisions inside Ordovee. Where we use AI in development, humans review what ships and customer operational data remains outside those development tools.

We have written down the full approach because “we use AI” is not enough information to evaluate a system your operation depends on.

How we use AI
System behavior

The checks and records behind everyday operations.

Ordovee uses inventory history, synchronization checks, import previews and activity records to make changes traceable and problems easier to investigate.

The physical count disagrees with the screen.

Walk the inventory history and find where the unexplained part begins.

A marketplace shows a different quantity.

Treat it as channel drift, not a new warehouse fact.

A CSV contains bad data.

Preview it before the records commit.

An automated action does not appear to have happened.

Check the activity history instead of guessing whether it ran.

Someone changed a record unexpectedly.

Follow the change history back to its source and attribution.

You want your catalog outside Ordovee.

Export it in an open format.

Those are not edge cases around the product.

They are part of designing software for a real operation.

Built to explain itself.

Ordovee records inventory movements, record changes, and system activity as the work happens.

When something needs a closer look, the history is already there. You can see what happened instead of trying to piece it together afterward.

  • One authoritative operational record.
  • History preserved behind the current state.
  • Outside systems do not redefine the operational record.
  • Changes traceable.
  • Data portable.

These principles run throughout Ordovee, keeping inventory records consistent and changes understandable across the operation.

See Ordovee in operation Talk to us