A delivery can be partial. The record should be clear.

A purchase order describes what is expected. Receiving should record what actually arrived and was accepted. We’re designing Merchavelo Inventory around that distinction.

One order, several moments

Imagine a merchant orders twelve units of an item. Eight arrive on Monday, and the remaining four are expected later. This is an illustrative workflow, not a customer case study.

Marking the entire order as received would hide the outstanding quantity. Leaving it entirely open would hide the delivery that already happened. Partial receiving gives the first delivery its own record while preserving the rest of the order.

When the other four units arrive, that should be another receiving event. The merchant should be able to understand the order’s progress without treating a single status label as the whole history.

Corrections belong in the workflow

Counts can be wrong. A product can be selected incorrectly. A receiving action can need correction after someone checks the delivery again.

Our development work includes receiving corrections because these cases need a clear path through the product. The aim is to make the reason for a change understandable alongside the quantities involved. A correction should help explain the record rather than erase the context of the original action.

The location matters too

A quantity needs a destination. Receiving stock into one location is different from moving it between two locations, even if the product and the number of units are the same.

Merchavelo Inventory’s development scope includes purchase-order receiving, location-aware work, and inter-location transfers. We treat these as related workflows with different meanings, so the interface can make the intended action clear.

What we’re checking

Repeated actions and interrupted requests are part of the testing work. A user may click again because a response was slow. A connection may stop after an action begins. We need to consider what a person sees next and how the record can be reviewed.

These are development priorities, not a claim that every real-world scenario has been validated. The app remains in private development and testing. If receiving is part of your daily work, share the steps you need the software to handle.