Tracking Returns Against Deliveries

The most useful thing about a return in wallmarkets is not a label. It is the link back to the original delivery.

That link is what lets you answer the questions that matter in real work:

• what shipment the return came from
• how much product was originally delivered
• how much has already been returned
• which supermarket and branch are involved
• whether the same delivery has turned into multiple return records

This article explains how to read that history cleanly.

Start from the returns list

Open Returns from the sidebar.

This is your fastest overview of return history. Use it to spot:

• recent returns
• repeat supermarkets
• unusually large return values
• clusters of activity tied to one delivery period

The list is good for scanning. The detail page is where you confirm the facts.

What to look for on the return detail page

Each return detail page gives you the record that matters:

• return date
• original delivery date
• supermarket
• branch
• returned products
• quantities
• unit prices
• total return value
• a direct link back to the original delivery

That delivery link is not a convenience feature. It is the backbone of traceability.

How quantity tracking stays honest

wallmarkets validates returns against the original delivery and any earlier returns already linked to it.

In practice, that means you cannot keep returning the same delivered quantity over and over. The system reduces the remaining available quantity as returns accumulate.

This is one of the most important safeguards in the workflow because it prevents sloppy reconciliation later.

Use delivery and return pages together

When a return looks odd, do not stare at the return page alone.

Open both records:

• the original delivery
• the linked return

That side-by-side view usually answers the practical questions quickly:

• was the right product shipped
• how much was sent
• how much has come back
• whether multiple returns are tied to the same delivery
• whether the financial impact matches what operations remembers

Exports and reporting

Tracking gets more useful when you zoom out periodically.

Use the returns list and Delivery Reports and Analytics to review:

• which supermarkets generate the most return value
• which deliveries produce repeated follow-up work
• whether returned value is concentrated in a small number of shipments

The detailed record tells you what happened. Reporting tells you whether it keeps happening.

Common mistakes

Looking at return value without the original delivery

That hides the context that explains the record.

Treating each return as isolated

Patterns usually show up across linked records, not within one record alone.

Ignoring repeated small returns

The expensive pattern is often not one huge return. It is the same manageable problem appearing every week.

Related guides

• Processing a return
• Return analytics
• Optimizing your return process