Ordering & transfers

Daily ordering in Mihwar is a two-lane flow. Branches request stock from your warehouse (a transfer), and the warehouse orders from suppliers (a purchase order). The AI suggests the quantities on both lanes.

Lane 1 — A branch's day: request, then receive

1. 1

   Open the replenishment workspace

   From the branch, open Inventory → Replenish a branch. It is a three-step flow: confirm your order cycle, review quantities, send.
2. 2

   Review the AI-suggested quantities

   Each line shows the suggested amount in your branch's everyday units. Tap “Why this number?” to see the reasoning in plain language. You can change any quantity — raising it far above the suggestion asks for a short reason, which also teaches the forecast.
3. 3

   Send the request

   Press Send request. It goes straight to your warehouse's incoming queue — no email, no spreadsheet. Items marked as supplier-direct in the catalog split automatically into a separate direct order.
4. 4

   Track it in Transfers

   Watch progress under Inventory → Transfers: requested → picking → packed → in transit (with the ETA and driver the warehouse sets).
5. 5

   Receive and flag problems

   When the delivery arrives, open it and confirm line by line. Anything short, over, damaged, or substituted — flag it on the spot. Flagged lines go to the warehouse's discrepancy queue and open a follow-up (CAPA) automatically, so problems never rely on a phone call.

Lane 1, other side — the warehouse's day

1. 1

   Work the incoming queue

   Open Warehouse → Incoming. For each branch request: allocate quantities, then Approve & send to pickers — or reject it, which converts the demand into a draft supplier order instead.
2. 2

   Pick and pack

   The pick list batches lines for the floor — scan barcodes, record short picks honestly, and Finish & mark packed. It works offline and syncs when the connection returns.
3. 3

   Dispatch with an ETA

   Mark the transfer dispatched and set the ETA and driver. The branch sees it instantly and gets notified if the ETA changes.
4. 4

   Close out discrepancies

   Anything a branch flagged at receive lands in Warehouse → Discrepancies. Acknowledge each one and resolve its linked follow-up — that record is what keeps suppliers and pickers honest.

Lane 2 — warehouse to supplier (purchase orders)

1. 1

   See aggregated demand

   Warehouse → Replenishment totals what all branches are asking for, per supplier, with AI-recommended buy quantities.
2. 2

   Raise and approve the PO

   Create the supplier order, and approve it under Supplier orders if your setup requires approval. Recurring rules and rejected branch requests also create draft POs here.
3. 3

   Send it to the supplier

   From the order detail, export the purchase order as PDF or CSV (Arabic-ready) — or dispatch via the channel configured per supplier.
4. 4

   Receive against the PO

   Record what actually arrived. Shortfalls here are flagged the same way branch receipts are — and every fulfilled line becomes order history that sharpens the forecast.

Where the learning happens

Every request, fulfillment, and receipt feeds the demand model — see AI predictions for how to read accuracy and coverage. Stockouts your closing checklist reports (see how the apps work together) count as extra demand the forecast would otherwise miss.