Skip to content

Traceability

Traceability shows stock movements. It is the page used when you need to understand what happened to a product: who moved it, when, in which location, with what quantity, and in which flow.

The stock report answers “how much do we have?”. Traceability answers “how did we get here?”.

To open the page, go to Inventory -> Traceability.

The page appears only for users who have the traceability reports permission. If the user does not have this permission, the route is blocked by the application.

Traceability uses the warehouses available to the user. If the user has access to multiple warehouses, the list can contain movements from all accessible warehouses, and the Warehouse filter narrows the results to the selected warehouse.

If no date range is selected, WMS loads movements from the last 30 days by default.

For an older investigation, manually set the Start date and End date filters.

Movement date filters include time and seconds. This helps when multiple operations happened on the same day.

The page can be filtered by:

  • movement date and time;
  • warehouse;
  • user;
  • action type;
  • inventory identifier;
  • product name;
  • SKU;
  • scanned barcode;
  • location;
  • quantity before;
  • quantity changed;
  • quantity after;
  • lot;
  • expiration date;
  • serial number;
  • order (ID);
  • adjustment (ID).

The user can also choose the displayed columns to keep the table easier to read.

The filter panel can be expanded or collapsed. The panel state is saved in the browser, so the page opens later in the same mode.

Filters are applied when values change. To return to the initial list, use Reset.

The table can display:

ColumnWhat it means
Date & TimeThe moment when the movement was recorded.
WarehouseThe warehouse where the movement happened.
UserThe user associated with the operation, if available.
Action TypeThe operational event type.
Product NameThe product affected by the movement.
Product SKUThe product SKU.
Scanned BarcodeThe code scanned during the operation, if saved.
LocationThe involved location. For transfers it can show source -> destination.
Qty. BeforeThe quantity before the movement.
Qty. ChangedThe quantity added or removed.
Qty. AfterThe quantity after the movement.
LotThe product lot, when the product is lot-tracked.
ExpirationThe lot expiration date, if available.
SerialThe product serial number, when the product is serialized.
OrderThe order number linked to the movement, if available.
Adjustment (ID)The adjustment linked to the movement, if available.
Inventory (ID)The inventory linked to the movement, if available.

Column selection is useful when investigating a specific case and keeping only the relevant fields visible.

The Table Size selector changes row density: Small, Normal, or Large.

The list is paginated. By default, 15 rows are displayed per page. You can change how many rows are displayed per page, for example 10, 15, 25, or 50. The choice is saved in the browser.

On desktop, results are displayed in a table. On mobile, the same movements are displayed as compact cards with the action, date, product, location, quantity, and available identifiers.

Traceability includes real WMS actions, for example:

  • receiving;
  • receiving correction;
  • putaway;
  • transfer between locations;
  • transfer out;
  • transfer in;
  • putaway HU transfer out;
  • putaway HU transfer in;
  • adjustment;
  • empty location;
  • remove from location;
  • picking;
  • missing product during picking;
  • move to cart;
  • remove from cart during packing;
  • return to stock;
  • logistic return to stock;
  • traceability entry for a missing logistic return product;
  • missing product adjustment for logistic return;
  • inventory differences: missing, surplus, recount restore, misplacement, parking, reconciliation, and final adjustments.

The action list displayed in the Action Type filter is based on movements that exist in the accessible warehouses. If an action type does not exist in the accessible warehouses, it may not appear in the selector.

A row usually shows:

  • action date;
  • user;
  • action type;
  • product and SKU;
  • scanned barcode;
  • location;
  • quantity before;
  • quantity changed;
  • quantity after;
  • lot and serial number;
  • link to an order, adjustment, or inventory, if available.

For transfers, the location can show source and destination.

Qty. Before is the value that existed before the operation.

Qty. Changed shows the operation impact. A positive value means an inbound or added quantity, and a negative value means an outbound or removed quantity.

Qty. After is the result after the movement is applied.

  • before an important adjustment;
  • when a product is physically missing;
  • when the stock report does not match reality;
  • when an order route must be checked;
  • when investigating logistic returns or inventory differences.

Filter by product, SKU, or barcode and check the latest movements. Compare quantity before, quantity changed, and quantity after.

Filter by Lot and, if relevant, by Expiration. For perishable products, the lot is essential in the investigation.

Filter by Serial. The serial number should narrow the result to the route of the individual product.

Filter by Order (ID) or check the order number in the Order column. Then compare picking, packing, return, or stock error lines.

Filter by Adjustment (ID) and check which quantity was removed or added.

Filter by Inventory (ID) and check missing, surplus, misplacement, reconciliation, or adjustment actions.

Traceability does not modify stock. The page is only for analysis and audit.

Traceability does not replace operational pages such as Inventory adjustments, Missing items, or Surplus items. After the cause is found, the correction is done in the right operational flow.

  • Do not draw conclusions only from current stock. Check movements too.
  • For lot-tracked or serialized products, filter by lot or serial number as well.
  • For inventory differences, compare with Missing items and Surplus items pages.
  • For audit, keep the period as exact as possible and include the warehouse, product, and relevant operational identifier.