Quick answer

Use statuses as signals for ownership, not as a reason to guess. An order or product status tells you where to investigate next: CS, warehouse, receiving, inventory, product data, integration, or support.

Common use cases

CS: Explain order state without promising a next step too early.
Warehouse lead: Decide whether the next action belongs to fulfillment, receiving, route work, or exception review.
Admin: Investigate product, inventory, sync, archived, or receiving-related statuses.

When to use this

An order or product has a status the team does not understand.
A customer asks what a status means.
A teammate needs to know who owns the next action.

Before you start

Confirm the workspace and warehouse, and dashboard you are reviewing.
Use the visible status together with order/product details, not by itself.
If a status is not listed or the next action is unclear, contact support with the exact label and screenshot.

Steps

Pending: the order is ready for the first operational task: starting a picking activity for an outbound order, starting a receiving, starting a return activity.
In progress: the first operational activity (picking, return, receive) has been started but not completed.
Packed: DTC Order has a completed packing activity
Waiting for pickup: manifest has been closed and the order is waiting for the carrier's pickup
Shipped: carrier has scanned the order that was ready for pickup and it is on the way to the shopper/end customer.
Completed: order has been completed or fully delivered.
On-hold or blocked order statuses: mean the order should not be pushed forward until the hold or blocker owner is understood.
Backordered: the order contains one or more SKU with no inventory available in Logentic
Canceled: order is canceled and won't appear in fulfillment views
Archived, missing, sync-error, receiving, preparing, or replenishment-related product statuses: need product data, inventory, receiving, or support review before they are treated as available for fulfillment.
Exception or failed-sync statuses: point to exception, product-sync, order-sync, delivery, or integration review.

Screenshots

Orders dashboard showing quick search, date range, filters, and Add filter controls.

Screenshot: Use Orders dashboard status filters to narrow an order list before deciding who owns the next action.

Products dashboard showing search, date filters, Filters, and Add filter controls.

Screenshot: Use Products dashboard search and filters to review product status, SKU, and sync context.

What good looks like

The team uses status labels to choose the right next owner and avoids releasing holds, promising fulfillment, changing inventory, or retrying sync work without enough context.

Common issues and next actions

If this happens	What to do next
The status label is unfamiliar.	Capture the exact label, dashboard, order or product ID, and screenshot before escalating.
A status conflicts with what happened physically.	Check receiving, inventory, scan, route, and product-sync context before changing records.
A customer asks what happens next.	Identify the owner first, then reply with what is confirmed rather than guessing.

Contact us when

Contact support when the status is unfamiliar, the next owner is unclear, the status conflicts with physical warehouse work, or a customer-facing promise depends on interpretation.