iyibir WMS
FeaturesAI ModeIntegrationPricingResourcesGet started
Manager panel

Stop collecting reports; see what is broken and fix it

A warehouse manager's day often goes into gathering information: which shipment is late, which count found a variance, who is on what, will the team cover tomorrow. The information exists, but it is scattered and arrives late. The iyibir WMS web panel is not a reporting screen; it is an exception centre: it shows what is broken and puts the fix next to every row.

Today
  • 2Late shipmentsResolve
  • 5Open work left from yesterdayResolve
  • 1Count variances awaiting a decisionResolve
  • 3Open replenishment suggestionsResolve

Illustration. Rows at zero do not appear on the card.

The manager's question, the panel's answer

The panel's menu follows the flow of work: cockpit, tasks, warehouse, inbound, outbound, counting, analysis. Below is which screen answers which question.

  • What should I look at first today?

    The morning briefing opens at the top of the cockpit: late and due-today shipments, open work left from yesterday, count variances awaiting a decision, open replenishment suggestions, shipments whose e-despatch has not been sent, and the change in the data health score. Each row's "Resolve" link opens the page where the work is waiting, already filtered.

  • What is broken, and what do I do?

    The exception centre counts short picks, repeated mis-scans, overdue tasks, expired reservations, count variances awaiting a decision or recount, tasks waiting for their Logo record, and a lost Logo connection in one list. The suggested fix sits next to each row: reassign, recount, approve the variance, open the task. The list refreshes on its own.

  • Can I just type the question instead of moving between screens?

    The Assistant in the top bar opens a side panel from any page and knows the page you are on; there is also a full-page view with conversation history. Questions such as "Who is free?", "Why did this count variance happen?" or "What does today's workload look like hour by hour?" are answered from cockpit, exception, workload, task, team, recommendation, pick-face, count-variance and sales-order data. The assistant drafts task assignments, applied recommendations and pick-face minimum/maximum changes; values come from the system's own calculation. Team status shows each person's zone and shelf ("Who is free in zone A?"); clicking a row in a table opens that task, count variance or order. A draft is applied only after "Approve" and a confirmation dialog; the assistant never writes to Logo.

    AI Mode
  • Will the team cover today's work, and what about tomorrow?

    The planning screen compares workload with capacity for today and tomorrow, shows load per person and per zone, and marks overload in red. You assign pooled work to people from here.

    Task management
  • Who gets how much done, and are we measuring it fairly?

    The performance screen offers team, person, workload and warehouse health views. Labour standards are calculated from your own warehouse's past tasks; each task's expected time comes from that standard. People are listed by name and no ranking table is built; an operator sees only their own data.

  • Is our shelf layout right?

    The warehouse map opens with occupancy, movement velocity, ABC class, task density and task route layers. The map can be seen as a plan or in 3D; in 3D shelves stand on their own levels in the same colours. The recommendations screen suggests slotting moves based on velocity, risk-based cycle counts and pick-face replenishment. Before applying a slotting move, "What if?" walks the picks of recent weeks again with the new layout and shows the weekly walking difference; it is only a calculation and nothing moves. An applied recommendation becomes a task.

  • Is our Logo data ready for warehouse management?

    The Data Health Scan runs seven checks on your Logo data: negative stock, stock not assigned to a shelf, count variances, items without a barcode, expiry dates, slow-moving stock and items without dimensions. The result is a score from 0 to 100; for each check it says what was found, why it matters and how to fix it. The report can be printed.

  • If a batch is recalled, who received it?

    On the traceability screen you search a lot or serial number; where the goods came from, where they are now, what happened to them and which customer received them appear on one page. The recall view lists affected customers with quantities.

    Lot and serial tracking
  • Who wrote this document, and when?

    The movements screen lists every record sent from the floor to Logo with the person who wrote it, the time and the Logo document number. A record whose answer stayed uncertain, that was written in part or whose read-back differs stays at the top of the attention list; after checking Logo and doing what is needed, the manager closes it with a reason. Closing sends nothing to Logo, and an uncertain record is never sent again. A record that never reached Logo, or that Logo plainly refused, the manager sends once more with the same content after the cause is fixed; if Logo already holds the document, nothing is sent.

  • Who approves a request opened on a phone?

    A request opened on the floor stays in Logo as an unapproved proposal and does not reach fulfilment. The manager approves it on the request's page, or cancels its lines that have not been fulfilled yet. It is one of the two things the panel writes to Logo (the other is sending a failed record again), and it runs like mobile: preview, approval and read-back from Logo.

  • When something goes wrong on the floor, how does it reach me?

    The operator taps "Report to manager" on the phone: a damaged item, a wrong item, an unreachable shelf or another reason, with a note. Reported from a task, the task, shelf and item are added by themselves. The report lands in the exception centre and the morning briefing; you take it, write the resolution, and the answer shows on the operator's phone.

  • Does knowledge from the floor stay in one person's head?

    An operator leaves a note on a product, a shelf or a supplier, typed or spoken: "This supplier's carton holds 10, not 12." The next person who touches it sees the note as a card on their phone. If the manager approves it on the Warehouse notes screen it becomes permanent; if rejected, it is removed.

  • Where do I change the warehouse rules?

    Settings under Management are gathered in one place: depot point, shifts, ABC classes, golden zone and heavy item rules, replenishment and put-away suggestion limits, cycle counting and new count plan defaults, the rule that picks the next job, health weights, packing and users. Every change is saved after a confirmation that shows the old and the new value.

How the panel works

The web plans, the floor executes

Task, wave and count plans are set up on the web. Transactions that write to Logo are previewed and approved on the floor, in the mobile app; the exceptions are the manager's request approval and the resending of a failed record, both through the same preview and approval.

Every number drills down to a list

Clicking an indicator opens the row list with the same filter. A number is never left on its own; the records behind it are visible.

Access comes from the role

Management, planning and analysis screens are for the warehouse manager. An operator sees their own work and their own performance.

Open the cockpit for your own warehouse

Open your iyibir Cloud account, start with 5,000 free credits and begin by running your Logo data through the Data Health Scan.