Choose the correct context
Check the location and product variant before entering a quantity. Similar product names or options can otherwise make a correction affect the wrong record.
INVENTORY / ACCURACY
Every correction needs a reason.
Use stock records to explain the difference between expected and physical quantity. The Agora stock-issue workspace brings the location, item, quantity and issue information into one task.
BUILT AROUND THE WORK
What this means
for your business.
Record what happened
Distinguish damage, a count discrepancy and another operational issue. A useful note explains the event in terms another team member can investigate.
Inspect the result
Confirm the resulting quantity and any related records in your deployment. A correction should close a documented difference, not hide an unexplained one.
THE DETAIL IN BUSINESS CONTEXT
Follow the item, not just the headline total.
A variant at a warehouse and the same variant at a shop have distinct location records. Movement, reservation and correction explain why available quantity changes.
The record identity
Variant, location, quantity and reason are part of an inspectable stock event.
The exception
A short receipt, damaged item or concurrent update requires a decision trail and a responsible person.
INSPECT THE RECORDS AND DECISIONS
A correction needs a reason as well as a number.
A damaged item, a count correction and a normal sale are different stock events. Make the correction intelligible to the next person who reads the record.
Operating concepts to inspect in your setup; this is not a wire-format schema. Exact API fields belong in the source-derived reference.
- Variant ID
- Identifies the option being adjusted.
- Location ID
- Identifies where the quantity changes.
- Quantity
- The requested stock adjustment, following the actual contract’s convention.
- Reason
- Explains the business event behind a correction.
- Version check
- The supplied adjustment contract exposes an expected-version input; review its deployed conflict behaviour.
- Result inspection
- Confirm the resulting quantity and any failure before repeating the request.
When a concurrent update occurs
Read the current record and resolve the conflict deliberately. Repeating an adjustment blindly can create another unintended change.
When physical and system counts disagree
Record the count, reason and responsible role. Keep the correction separate from the transaction that originally revealed the discrepancy.
Inspect the supplied workspace.
Supplied Agora inventory workspace. This capture provides interface context; the operating scenarios on this page use separately labelled sample data.
FOLLOW THE PROCESS
From the first step
to the next decision.
01
Investigate the difference
Compare physical stock and the relevant order or movement records.
Investigate the difference→Enter the issue→Review the updated record
02
Enter the issue
Select the location, item, reason and quantity through the supported workspace.
Investigate the difference→Enter the issue→Review the updated record
03
Review the updated record
Check the result and retain the explanation for follow-up.
Investigate the difference→Enter the issue→Review the updated record
Operating walkthrough · Review the exact configuration for your business.
A CLEARER PICTURE
Good questions.
Useful answers.
Who should make adjustments?
Limit correction rights to the appropriate staff and agree approval rules.
Should an integration overwrite the quantity?
Prefer a defined stock-change workflow and reconciliation process. Review the actual API contract before implementing.
BUILD WITH AGORA
Your next chapter starts here.
Bring your business, your ambition and the questions that matter. Let’s explore what you can build with Agora.