Get started with Kaduno Warehouse EN

Choose the correct warehouse mode and follow receiving, picking, packing, printing and stock-count workflows.

This guide follows the Norwegian Warehouse guide. It describes configured workflows, not tested hardware, stock accuracy or delivery performance for your installation. /admin/ paths are in your store's administration. Agree a test warehouse and permitted effects before recording movements, approving counts, booking freight or printing labels.

Choose ownership and mode first

Confirm which system owns stock. An administrator chooses the mode under Settings → Warehouse management (/admin/settings/warehouse):

ModeMeaning
Built-in WMSKaduno warehouse workflows with reservations, picking and fulfilment
External WMSStock is managed elsewhere; automatic reservation is disabled and Kaduno's own terminal workflow is not the external warehouse's interface
OffWarehouse management/reservations are off and storefront stock status is not shown

Basic inventory and advanced WMS have their own switches. Advanced features include Scanner / mobile terminal, Pick and pack, Stock counts, Internal transfers and Work statistics. Mode, feature activation, licence and role control availability. Do not make internal stock movements as a substitute for an external WMS's own workflow.

Warehouses, locations and quantities

Warehouse management (/admin/warehouse-management) has a warehouse selector and Overview, Receiving, Counts and Locations surfaces. Inventory is at /admin/inventory; movements and transfers have their own area. Use scannable location codes such as A-03-S2-B7 and the appropriate type: pick, bulk, receiving, returns, quarantine or general, where enabled.

Physical, reserved and available stock are different quantities. Negative-stock and out-of-stock policies are configurable: WMS is not a universal promise that all sales below zero are blocked. Transfers between the store's warehouses can be initiated from a product, with source and destination locations checked first.

Receive against a purchase order

  1. Open PO receiving on the terminal (/admin/warehouse/receive-po) or choose From purchase order in Receiving.
  2. Confirm the purchase order, receiving warehouse and expected lines.
  3. Scan the item, enter the quantity actually received and a location where needed.
  4. Confirm only the authorised receipt, then check the result and outstanding quantity.
  5. Record discrepancies through the purchase-order discrepancy workflow. Never mark missing goods as received to make a partial receipt look complete.

Goods without a purchase order use the separate receipt path. A partial receipt is not an error that should be repaired by recording the balance as received. For purchasing context, see the Norwegian guide.

Pick, pack and dispatch are separate stages

With Pick and pack enabled, Pack & ship (/admin/pack-and-ship) follows orders through picking, packing, dispatch and sent stages. On the terminal, select a pick task at /admin/warehouse/pick, scan location and item, and complete picking only when the work is correct. At /admin/warehouse/pack, scan items into parcels and complete packing.

A packed order is not a dispatched shipment. A shipping connection is needed for carrier labels and tracking; Book freight & dispatch can book real freight and trigger downstream effects. Confirm the order's shipment status and permitted payment/invoice effects before using it in a test.

Supported terminal scans can be queued locally during connectivity loss. Inspect the offline/synchronization indicator and any failed items before assuming the server received a scan. Local storage is not proof of successful synchronization; do not scan or receive the same goods again merely because the server view is late.

Labels and printing

Label printing (/admin/printing) has Printers, Templates, Rules and Queue. Printing requires its own licensed module; automatic printing is a separate switch, off until enabled. Configure only the printers and triggers required by the workflow.

For a printer on your local network, a printing agent polls Kaduno, prints locally and reports the outcome. This model does not require opening an inbound network port to the internet. It still requires an approved machine, connectivity and a supported printer setup. Use a dedicated key limited to printing:agent; keep it out of screenshots and shared instructions. Installing/configuring an agent is separate from this walkthrough.

Inspect Queue and agent/printer status before choosing Print again. Reprinting can produce a second physical label. A queued or sent job alone does not prove a correct, readable physical label was attached to the right parcel.

Counts, adjustments and related work

Create a full, cycle or partial count from Counts. Review discrepancies before approving/posting them. Manual adjustments at /admin/inventory/adjust need a meaningful reason so the movement can be traced. Counting or adjusting stock can affect availability and downstream systems; agree the scope before testing.

Where production is enabled, see production and bills of materials (Norwegian). Work performed at a customer's site uses service orders under /admin/work-orders, where the relevant service-order view is enabled; it is not the same as a stock count.

Troubleshooting

  • Item not found: check barcode/SKU, store and catalogue identity.
  • Wrong quantity: check unit and whether the receipt/movement was already recorded.
  • Terminal missing: check WMS mode, licence, feature settings and role.
  • Freight label fails: inspect parcel, address, carrier setup and existing booking before retrying; an uncertain response may already have created a booking.
  • No physical print: check active printer, agent connection, queue and printer output.
  • Offline scan pending: resolve synchronization before repeating the operation.

A useful acceptance record separates receiving, stock movement, pick/pack, carrier booking, physical printing and return-status verification. Test those stages with controlled fixtures; a successful screen or label is not full order-to-delivery acceptance.