Miridia
Portal
Guides

Transfer orders

Move stock between your own locations. Use one order type for a warehouse rebalance and for a branch request.

A transfer order moves stock from one of your locations to another of your locations. Ownership does not change, and no money changes hands. The stock moves at cost.

Three order types, one rule

Miridia has three order types. The rule that selects the type is simple.

Order typeDirectionDoes ownership change?Financial effect
Sales orderYou to a customerYesRevenue
Purchase orderA supplier to youYesSpend
Transfer orderYou to youNoStock moves at cost
A franchisee who buys stock from the head office is a customer. Ownership changes, and money changes hands. Record this as a sales order, not as a transfer order. If you record it as a transfer, the head office reports no revenue and the franchisee reports no cost.

The lifecycle

StatusMeaning
DraftA transfer that you prepare, for example a rebalance between two warehouses.
RequestedA location asked for stock. The supplying location must decide.
ApprovedThe supplying location accepted the transfer.
InTransitThe stock left the origin.
PartiallyReceivedSome of the stock arrived. The remainder is still in transit.
ReceivedAll of the stock arrived.
RejectedThe supplying location refused the request.
CancelledThe transfer stopped.

Miridia guards each status change. For example, you cannot dispatch a transfer that is not approved.

A branch request

This is the most common use in a multi-branch business.

The branch requests stock

The branch manager creates a transfer order with the status Requested. The origin is the warehouse and the destination is the branch.

The warehouse decides

The warehouse approves the request, or it rejects it. If the warehouse does not have enough stock, it raises a purchase order with a link to the request. It can also approve part and buy the rest.

The warehouse dispatches

The warehouse dispatches the approved transfer. Miridia writes a TransferOut movement at the origin. The quantity shows as in transit at the destination.

The branch receives

The branch records the quantities that arrived. Miridia writes a TransferIn movement at the destination and reduces the in-transit quantity.

Two-phase movement

Dispatch and receipt are two separate actions. Between them, the stock is in transit.

  • The stock leaves the origin at once when you dispatch.
  • The stock is not available at the destination until you receive it.
  • The stock never disappears from the business total.

Thus stock on a truck is never available at both ends, and it is never lost from the count.

A partial receipt is normal. The remainder stays in transit until the next receipt. Each receipt accepts an effectiveDate.

Shortfalls and purchase orders

When the warehouse is short, it raises a purchase order with sourceTransferOrderId set to the transfer order. The branch can then see when the rest of the stock will arrive. The buyer can see the demand that caused the purchase.

The automatic step from a branch request to a transfer or a purchase is planned. The link between the documents exists today. Today a person raises the purchase order.

A quick move

For a simple move that needs no approval and no transit time, use the one-step inventory transfer. Read Inventory.

Notifications and workflows

Miridia tells the business when a transfer is received and when a transfer is rejected. Workflows can start on OnTransferOrderCreated, OnTransferOrderStatusChanged, OnTransferOrderDispatched, and OnTransferOrderReceived.

API reference