Orders - Ops Mode

Ops Mode tells you how the Orders list should treat an order.

Think of it as one question: should this order be part of the live warehouse queue at all?

Quick mental model:

• Operational = belongs in the live queue if nothing else blocks it
• Monitoring only = keep the order visible but do not work it
• All = show both

Operational is not the same as “actionable right now”. A live order can still be blocked by local hold, history mode, upstream status, stock state, or shipment evidence. See Orders — Understanding Order State.

Where you see it

Users see Ops Mode on the Orders list as:

• an Ops Mode filter
• an optional Ops Mode column

The Orders list defaults this filter to Operational.

Not the same as

Operations Diagnostics

Operations Diagnostics is a troubleshooting tool for operational problems such as missing shipment evidence, missing pricing, or reporting gaps.

It is not the same as Ops Mode.

• Ops Mode is an Orders filter about whether the warehouse should actively work the order.
• Operations Diagnostics is a separate diagnostic page for explaining problems.

Monthly Operations

Monthly Operations is a month-end billing and review workflow.

It is not the same as Ops Mode.

• Ops Mode helps you control and understand the Orders view.
• Monthly Operations helps you review billable activity for a client and month.

Other operational tools

Ops Mode is not the Morning Board, not operational diagnostics, and not general month-end reporting.

For help search and AI Help:

• questions about Operational, Monitoring only, or All on the Orders list should land here
• questions about troubleshooting operational issues should usually land in Operations Diagnostics
• questions about billing review should usually land in Monthly Operations

Which option should I use?

Operational

Choose Operational when you want the normal working queue.

Use it for tasks like:

• finding orders that belong in today's live warehouse queue
• working through today's warehouse queue
• checking orders that should still be eligible for live execution

Example:

• a picker wants to find the next orders that should move through normal fulfilment
• a dispatcher wants to see orders that should be ready for shipment work

Warehouse users will normally spend most of their time in Operational.

Monitoring only

Choose Monitoring only when you need to see orders that are still visible in ParcelPilot, but are not meant for normal warehouse execution.

Monitoring only exists so ParcelPilot can continue importing and displaying orders without allowing normal warehouse activity.

Use it for tasks like:

• supporting a client that has been suspended but still needs visibility
• checking imported orders that should be monitored rather than worked
• reconciling what arrived from an integration without mixing it into the live queue

Example:

• a client has been paused operationally, but support still needs to see the imported orders
• an admin wants to confirm which orders stayed visible after a client moved to monitoring-only mode

This view is usually more useful for support, operations managers, and administrators than for day-to-day warehouse execution.

All

Choose All when you need the full picture.

It shows both:

• operational orders
• monitoring-only orders

All does not bypass unrelated visibility rules.

All is mainly an investigation and support view rather than the normal warehouse queue.

Use All when you are:

• investigating a missing order
• supporting a suspended client and need to compare active versus monitoring-only records
• reconciling imports against what operators can see in the live queue
• checking historical operational activity without assuming the order is actionable

It still respects other active constraints such as:

• tenant and client scope
• archived-client hiding unless separately revealed
• any other active Orders filters
• closed, suppressed, archived, anonymised, or accounting-specific reveal rules on the Orders page
• separate History Mode or pre-go-live history rules

Why Orders defaults to Operational

Orders defaults to Operational because that is the safest and most useful starting point for day-to-day warehouse execution.

Without that default, the main list would mix live actionable work with records that are intentionally not part of normal warehouse processing.

How an order becomes monitoring-only

Ops Mode is related to the client's operating mode.

Current client operating modes include:

• Active
• Suspended - monitoring only
• Archived

When a client is Suspended - monitoring only, ParcelPilot can keep imports and visibility running without treating those orders as live warehouse work.

For operator use, the important point is simple:

• the order stays visible
• the warehouse should not work it normally
• Ops Mode helps you spot that quickly on the Orders list

See Clients - Create, Edit & Delete for the client operating-mode explanation.

How Monitoring only changes warehouse behaviour

Monitoring-only is not just a view setting.

It affects real warehouse behavior.

Monitoring-only orders can be excluded from or blocked from workflows such as:

• active warehouse operational queues
• shipment creation
• picking and other warehouse execution
• linked shipment actions that depend on the order being operational
• picked-awaiting-dispatch style workload views

If the question is "Why can't I pick or ship this order?", Ops Mode may be one reason, but it is not the full blocker model. Also see Orders — Understanding Order State and Why Can't I Create a Shipment?.

Ops Mode and client operating mode

Ops Mode on the order is downstream from client operating mode, but they are not the same field.

• Client operating mode is the client-level account setting such as Active or Suspended - monitoring only.
• Ops Mode is the Orders-level filter and badge that shows whether a specific order is currently treated as operational or monitoring-only.

In plain English:

• client operating mode is the source business rule
• Ops Mode is how that rule shows up on orders

Ops Mode versus History Mode

Ops Mode is different from History Mode.

• Ops Mode answers whether the order belongs to live warehouse work or monitoring-only visibility.
• History Mode answers whether the order is pre-go-live history kept as older imported record history.

Pre-go-live history is a separate non-operational concept. An order can be non-operational because it is historical, because it is monitoring-only, or because of another workflow blocker.

Troubleshooting

I can't find my order

First, switch Ops Mode from Operational to All.

That is the fastest check when an order seems missing from the live queue.

If the order appears under Monitoring only, the issue may be that the order is still visible but not part of active warehouse work.

If it still does not appear, remember that Ops Mode does not override:

• tenant or client scope
• archived-client hiding
• other active Orders filters
• separate History Mode or other list reveal rules

Why can't I create a shipment?

If the order is Monitoring only, that can explain why shipment creation is blocked or why the order is visible but not actionable.

Ops Mode is not the only possible blocker, so use Orders — Understanding Order State for the full state model and Why Can't I Create a Shipment? for the shipment troubleshooting path.

Why is this order visible but not actionable?

That is exactly the kind of case Ops Mode helps explain.

If the order is visible under Monitoring only, ParcelPilot is intentionally keeping it on screen without treating it as normal warehouse work.

An order can be operational and still blocked

Ops Mode is not a full summary of every warehouse blocker.

An order in the Operational queue can still be blocked for reasons such as:

• pre-go-live history
• outstanding payment under the client's policy
• cancelled or refunded state
• external fulfilment or non-warehouse fulfilment
• upstream or warehouse on-hold state
• ParcelPilot local fulfilment hold
• already fulfilled or otherwise no longer actionable state
• stock, serial, warehouse, or pickability blockers

So if an order is not progressing, do not assume Ops Mode is the only explanation.

Related guides

• Orders Table Columns
• Why Can't I Create a Shipment?
• Orders — Reimporting an Order
• Orders - eCommerce Workflow, Suppression, Archive, GDPR & Accounting
• Clients - Create, Edit & Delete
• Operations Diagnostics
• Monthly Operations

Selective natural-language aliases

• ops mode
• what is ops mode
• what does ops mode mean
• what does monitoring only mean
• why is this order monitoring only
• why cant i pick this order
• why cant i ship this order
• what does all mean in ops mode
• ops mode vs history mode
• operational vs monitoring only
• where is my order
• missing order
• order not showing
• why cant i see this order
• suspended client
• monitoring only order
• why is my order greyed out
• why cant i action this order
• order wont ship
• warehouse queue