Deliveries (mobile)

Lines of an inventory: the item, the expected (system balance) and the counted (physical). The difference becomes an adjustment on applying. — this is the role of the "Counted items" screen within the platform.

Expected is the balance the system had for the item at the time of the count; Counted is what the team physically found. The difference between the two is what becomes a stock adjustment when the inventory is applied — up or down, with the calculation trail open. Use the row's Note to record why a big difference happened (damage, item in transit, unit error): it's what saves the argument when the adjustment is applied.

The grid has free search and column filters, with saved views per user; the choice and order of columns are also saved for you. A removed row goes to the grid's recycle bin and can be restored. You can select several rows and change a field at once (batch edit) and export the grid as a tabular PDF. And every addition, edit or removal of a row goes into the inventory's timeline, field by field (from → to) — the count becomes auditable.

Here you see and fix loose child records, one by one. In day-to-day work, however, the right thing is to create and edit them inside the parent record's form: that is where the business rules run (recalculated totals, validations, numbering, history). Editing directly here is useful for auditing and for correcting a specific case — but it can leave the parent record with an outdated total, and that raises no error on screen.

Each row shows the system quantity and the counted one, and the difference between them. It's this difference that becomes the stock adjustment when the inventory is closed — which is why checking before closing is cheaper than correcting afterwards.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

"Where do I see counted items?" — whenever that question comes up, this is the screen that answers it.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".