Staff and timing
Identify who counted and when.
Name the counter, shift, facility, and time. Record a second counter separately for recounts.
- Employee name or ID and department.
- Count date, time, and shift.
- Supervisor or assigned reviewer.
Describe your counting process. Makeform turns it into an inventory adjustment form that records the item, system quantity, physical count, reason, evidence, and reviewer decision.
Route adjustment records to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a starting point, edit it, or send the prompt into the Makeform builder. The fields are an example.
Audience
Warehouse associates counting assigned bins
Format
Mobile count form with variance workflow
Prompt size
292 chars
Example form structure
Mobile count form with variance workflow
Counter, date, zone, and bin
SKU, item, and lot or serial number
System quantity and physical count
Why is an adjustment needed?
Count evidence
Suggested routing tags
Pending review
Approved adjustments
Recount needed
Capture both the quantity before adjustment and the verified physical count. The difference alone cannot show whether the source numbers were entered correctly.
Step 1
Identify
item, location, lot, and current quantity
Step 2
Count
verified physical quantity and variance
Step 3
Explain
reason, notes, and supporting evidence
Step 4
Review
approve, reject, or request a recount
Why structured adjustments matter
A spreadsheet overwrite hides the original quantity and reason. A structured request keeps the before count, verified count, cause, and reviewer together.
Separate fields preserve the system quantity and physical count while showing the proposed variance.
Show damage photos, lot details, receiving documents, or recount notes only when the selected reason requires them.
Send exceptions to a reviewer to approve, reject, or return for another count.
Common adjustment events
Branch from common situations to the evidence each needs, giving staff a short form and reviewers a consistent record.
Record bin, SKU, book quantity, first count, recount, and proposed quantity.
Capture lot, quantity, condition, photos, quarantine location, and proposed disposition.
Connect expected, posted, and physically received quantities to the supplier, purchase order, receipt, and packing slip.
Give associates a phone-friendly route for shelf, backroom, return, theft, and data-entry discrepancies.
Adjustment workflow
Turn inventory rules into required questions and routing, then share one intake path with counting staff.
Specify bins, shelves, lots, serialized assets, or receiving lines and their required identifiers.
Add reason choices and evidence fields, then decide which differences require recount or review.
Preview routine, damage, receiving-error, and missing-stock branches before publishing.
Publish for staff and route records to an inbox, spreadsheet, Slack, or connected workflow.
Adjustment record options
Inventory software holds the balance; the request explains the count and decision.
Field guide
Use these six groups to keep submissions concise and reviewable.
Staff and timing
Name the counter, shift, facility, and time. Record a second counter separately for recounts.
Item and location
Use structured identifiers. Warehouses may need zone and bin; perishable stock may also need lot and expiry.
Quantity comparison
Ask for the system quantity and physical count. Keep units explicit when cases and individual pieces coexist.
Reason and cause
Use a controlled reason list plus notes. Branch to different facts for damage, receiving, returns, or data-entry corrections.
Evidence
Request photos or source documents only when the selected reason needs them.
Review decision
Offer clear outcomes and notes. Distinguish the requested correction from the quantity approved for entry.
Related tools
Connect adjustments with audits, warehouse checks, asset movement, maintenance, and notifications.
Structure broader inventory audits across products, locations, and count teams.
Open toolInspect storage areas, labeling, housekeeping, and operating conditions.
Open toolTrack assigned equipment and ownership changes outside saleable stock.
Open toolRecord assets moving between people, departments, or physical locations.
Open toolCapture service needs when a count reveals damaged operational equipment.
Open toolCollect customer interest when corrected availability reaches zero.
Open toolFAQ
Answers for managers creating a consistent stock-correction process.
It records a physical count or stock event that differs from the inventory system. It identifies the item and location, preserves both quantities, explains the reason, attaches evidence when needed, and records a review decision.
Include counter, date, facility, bin, SKU or barcode, item, lot or serial ID when relevant, unit, system quantity, physical count, variance, reason, notes, and reviewer. Request photos or receiving documents conditionally.
Collect system quantity and verified physical count. The source values help reviewers catch a reversed sign, wrong unit, or typing mistake. Display a calculated difference when suitable while retaining both entries.
Yes. Use choices such as count variance, damage, expiry, theft or loss, receiving error, return, transfer, and data-entry error. Conditional logic can show photos, packing-slip references, lot details, or recount fields as needed.
Route the submission to a reviewer with approve, reject, or request-recount outcomes. Keep comments, approved quantity, and review date with the request for staff updating the inventory system.
Yes. Add facility and location selectors with site-specific zones, bins, or reviewers. For long lists, create separate versions so staff see relevant choices and managers receive their site's records.
Yes. Makeform supports unlimited free forms and responses, so you can generate, edit, publish, and collect adjustment submissions without a response cap. The paid tier removes the Makeform badge.
No. The form captures the observation, reason, evidence, and review around a proposed adjustment. Your inventory or point-of-sale system remains the source of record. Route approved data to it through your existing workflow.
Turn every count correction into a reviewable record.