Confirm delivery, receive and close

After dispatch, a delivery needs three more acts, by two different parties:

1. The origin party confirms that the boxes were handed over, or reports a delivery problem.
2. The destination party checks every box and accepts or disputes it.
3. The destination party closes the order.

For who counts as each party, see Origin party and destination party.

​

Confirm the delivery

​

Who can do it

• Permission delivery.confirm (Confirm delivery).
• The source location in your Location access (the order’s location when the source is a central warehouse or the order named no source).
• To see the delivered boxes by code you also need fulfillment.read. Without it, the screen lists the ordered supplies instead.

Without delivery.confirm the screen says “You cannot confirm deliveries. Ask your clinic’s administrator for the permission.”

​

Where

• In Deliveries, open To deliver and select the order number. The section lists orders in Dispatched (dispatched).
• Right after dispatching, the Confirm the delivery link on the pick screen.
• From the custody detail, Confirm the delivery.
• Direct path: console.muveya.com/fulfillment/:orderId/delivery.

The screen is titled Delivery of order #1042. Under What is being delivered it shows either the boxes (Box code, Supply, Quantity) or, without fulfillment.read, the ordered supplies (Supply as “name · SKU”, Quantity as “10 × unit”).

​

Confirm a clean delivery

​

Report a delivery problem

Use this when the boxes could not be handed over properly. The answer is “The problem was recorded. The order is now a delivery problem.” The order moves to Delivery problem (exception).

​

What the system records

• A delivery record with who confirmed, when, which boxes were handed over and, for a problem, the reason code and details. It is written once and cannot be changed: confirming again only says “This delivery was already recorded.”
• No stock movement. The boxes stay In transit until the destination receives them.
• The order status (delivered or exception) and the audit record fulfillment.delivered or fulfillment.delivery_exception.

​

When a delivery problem is reported

A delivery problem stops the order:

• Its boxes stay In transit. They count in neither the source nor the destination warehouse.
• The order cannot be received or closed. The custody detail says “Resolution is pending with the clinic’s owner. Nothing more can be done here for now.”
• It is listed under Delivery problems for members with fulfillment.read.

There is no screen to resolve a delivery problem on the console today, and a reported problem cannot be withdrawn. The workspace owner should write to team@muveya.com with the order number and what happened.

​

Receive the order

​

Who can do it

• Permission receipt.confirm (Confirm receipt) and permission fulfillment.read (View fulfillment).
• The destination location in your Location access (the order’s location when the destination is a central warehouse).
• If the source and destination warehouses belong to two different locations, your Location access must not include the origin location, unless you have All locations in this account.

The screen explains what is missing: “You cannot receive orders. Ask your clinic’s administrator for the permission.” or “To receive box by box you also need permission to view deliveries. Ask your clinic’s administrator.”

​

Where

• In Deliveries, open To receive and select the order number. The section lists orders in Delivered (delivered).
• From the custody detail, Receive the order.
• Direct path: console.muveya.com/fulfillment/:orderId/receipt.

The screen is titled Receive order #1042. It lists one card per delivered box, with its code, supply and “Quantity: 10”. If the order is not in Delivered, it says “This order has not been delivered, so there is nothing to receive yet.”

​

Steps

Fields of a disputed box:

​

What happens to each box

A disputed box is recorded back in the warehouse it came from, so send it back physically. The original Dispatched movement stays in the ledger: the return is a new, compensating movement, never an edit. To inspect a quarantined box later, see Boxes and Lot recall; no action releases a box from quarantine. The order moves to Received (received) when every box was accepted, or Partially received (partially_fulfilled) when at least one box was disputed. The audit record is fulfillment.received or fulfillment.received.disputed.

​

Partial quantities

Reception is whole-box: each box is accepted or disputed as a unit, and there is no field for a received quantity. If a box arrived with fewer units than expected, choose one of these:

• Dispute the box (for example with Missing or Other) and describe the difference in the evidence. The whole box is recorded back at the source, where the count can be corrected.
• Accept the box and then correct its quantity at the destination with a stock correction.

​

Rules and limits

• Only an order in Delivered can be received.
• The reception must cover exactly the delivered boxes, each one once. The console builds this for you; if the delivery changed while the page was open, reload it.
• One reception can include up to 200 accepted and 200 disputed boxes.
• The first reception stands. Confirming again only says “This reception was already recorded.”
• The evidence text is stored with the reception but is not shown on the custody detail or returned by the API today. Per-box notes are returned by the API, not shown on the console.

​

Close the order

Closing is the last, administrative step. It moves no stock: every box was already received at the destination or returned to the origin.

​

Who can do it

• Permission fulfillment.close (Close fulfillment) and permission fulfillment.read (View fulfillment), because the button is on the custody detail.
• The same location rules as receiving: the destination party closes.

​

Steps

What the system records: a closure record with who closed and when, the order status closed, and the audit record fulfillment.closed.

​

Rules

• Only orders in Received or Partially received can be closed. An order with a Delivery problem cannot be closed.
• A box still in transit blocks closing. After a reception, muveya moves each box into the destination or back to the origin. If one of those stock steps did not finish, the box is still In transit and closing answers “This order cannot be closed yet.” muveya retries the pending step in the background; check the Boxes table on the custody detail and try again later. If a box stays In transit, write to team@muveya.com.

​

What can go wrong

​

Related pages