ParcelPilot
Help

Why Can't I Use This Location?

Use this guide when ParcelPilot blocks a receiving, assembly, inbound, or repacking workflow because the current location or warehouse selection is not currently usable.

What this guide covers

This guide explains the current deterministic blockers that ParcelPilot can already prove from the saved record context:

  • location mixing conflicts
  • location capacity exceeded
  • missing destination location
  • saved location outside the selected warehouse
  • warehouse not assigned to the client
  • no eligible warehouses configured for the client

This guidance is about current operational blockers only.

It does not choose the best location for you, move stock automatically, or bypass live validation when you try the workflow again.

How to read the blocker

ParcelPilot uses existing domain rules as the truth owner.

  • Location rules come from the current location, item, and saved workflow state.
  • Warehouse eligibility comes from the client's active warehouse assignments.
  • Final workflow actions still rerun live validation when you save, complete, or continue.

That means an AI answer or warning notification explains the current saved blocker, but the real workflow check still runs again at the point of action.

Common blocker types

1. Location mixing conflict

Meaning:

The selected location does not allow mixed items or SKUs, and it already contains stock for a different SKU.

Typical operator action:

  • choose another destination location that can accept the SKU
  • if operationally appropriate, use a location configured to allow mixed items or SKUs
  • try the workflow again after changing the location

Typical examples:

  • receiving into a location like A404 that already contains a different SKU
  • completing an assembly into a finished-goods location that already contains another item
  • completing a repacking workflow into a destination location that is reserved for a different SKU

2. Location capacity exceeded

Meaning:

The selected location has a configured capacity and the projected total would exceed it once the current workflow quantity is applied.

Typical operator action:

  • choose a location with enough remaining capacity
  • review whether current stock or pending receivings should be redirected elsewhere
  • try the workflow again after updating the destination

Important:

The capacity check uses current stock plus the queued quantity from the current saved workflow state.

3. Missing destination location

Meaning:

The workflow needs a destination location, but none is currently selected.

Typical operator action:

  • select the receiving or destination location
  • save or complete the workflow again

4. Saved location outside the selected warehouse

Meaning:

The location saved on the workflow no longer belongs to the same warehouse as the current record.

Typical operator action:

  • choose a valid location inside the selected warehouse
  • save or complete the workflow again

This usually appears after a warehouse change or when older saved values no longer match the current record scope.

5. Warehouse not assigned to the client

Meaning:

The selected warehouse is not currently an active warehouse assignment for the client.

Typical operator action:

  • choose a warehouse that is assigned to the client
  • if this warehouse should still be available, update the client's warehouse assignments first

See also:

6. No eligible warehouses configured

Meaning:

The client currently has no active warehouse assignments available for the workflow.

Typical operator action:

  • add at least one active warehouse assignment for the client
  • then retry the workflow

See also:

Workflows this currently applies to

The current bounded diagnostic and operator guidance are intended for current-record contexts in:

  • Receipts
  • Inventory Inbounds
  • Inventory Assembly
  • Inventory Repacking

These flows reuse existing warehouse eligibility and location rules.

What this guide does not mean

  • It does not guarantee the next save or completion will succeed.
  • It does not replace live domain validation.
  • It does not cover create-page questions that do not yet have a current saved record context.
  • It does not diagnose warehouse optimisation, picking strategy, or broader stock-placement planning.

If you still need to verify the cause

Check the current record for:

  • the selected warehouse
  • the selected location
  • whether the location already contains another SKU
  • whether the location allows mixed items or SKUs
  • whether the location belongs to the same warehouse
  • whether the client has an active assignment for the chosen warehouse

If the workflow is a receipt or inbound receiving flow, also confirm whether the quantity would exceed the destination location's configured capacity.