Create a Targeted Location-wise Stock Take Using Bulk Upload in Anchanto WMS – Anchanto

Overview

The Location-wise Stock Take bulk upload needs a Location Code on every row. You can also add a SKU, Batch and Expiry to limit the Stock Take to the exact inventory you want to audit. The more detail a row has, the narrower the count. This lets you audit specific SKUs, batches or expiry dates without counting the whole location or removing unrelated lines afterwards. Counters see only the inventory in scope, which helps reduce counting errors.

Prerequisites for Success:

Requirement	Detail
Template	Use the latest bulk upload template, which includes the SKU, Batch and Expiry columns.
Location Code	Every row needs a valid Location Code that has eligible inventory.
Stock availability	The location or stock you request must not already be held by another Stock Take or operation.

How the Upload Scopes Your Stock Take

Fields provided in the row	Inventory included in the Stock Take
Location	All eligible inventory in the location
Location + SKU	Only the specified SKU in that location
Location + SKU + Batch	Only the specified SKU and Batch in that location
Location + SKU + Batch + Expiry	Only the exact matching inventory combination

Example

Location LOC-A01 holds this inventory (example values):

SKU	Batch	Expiry	Qty
SKU-100	B1	2026-12-31	40
SKU-100	B2	2027-03-31	25
SKU-200	B7	2027-01-15	60
SKU-300	–	–	15

What each upload row adds to the Stock Take:

Upload row	Inventory added to the Stock Take
LOC-A01	All four lines (SKU-100 B1, SKU-100 B2, SKU-200, SKU-300)
LOC-A01 + SKU-100	SKU-100 B1 and SKU-100 B2 only
LOC-A01 + SKU-100 + B2	SKU-100 B2 only
LOC-A01 + SKU-100 + B1 + 2026-12-31	SKU-100 B1 expiring 2026-12-31 only

Field Rules and Validations

Location Code is the only mandatory field. SKU, Batch and Expiry are optional, but you must fill them in order: a Batch needs a SKU, and an Expiry needs both a SKU and a Batch. This is because a SKU tracked by expiry always has batches.

Field	Required	Depends on	Validation
Location Code	Yes	–	Must be a valid location with eligible inventory
SKU	No	Location Code	Must have inventory in the specified location
Batch	No	SKU	Must match a batch of that SKU in the location
Expiry	No	SKU + Batch	Must match the expiry of that SKU and batch in the location

Valid and Invalid Column Combinations

Location	SKU	Batch	Expiry	Result
✓				✅ Valid
✓	✓			✅ Valid
✓	✓	✓		✅ Valid
✓	✓	✓	✓	✅ Valid
✓		✓		❌ Invalid – Batch without SKU
✓			✓	❌ Invalid – Expiry without SKU
✓	✓		✓	❌ Invalid – Expiry without Batch

Step-by-Step Instructions

Prepare the Upload File

Step	Action	Expected Result
1	Go to Stock Take → Choose to create a Location-wise Stock Take through bulk upload	The bulk upload option for Location-wise Stock Take opens.
2	Go to the bulk upload option → Click to download the latest bulk upload template	The template downloads with Location Code, SKU, Batch and Expiry columns.
3	Go to the downloaded template → Enter a Location Code on every row	Each row has its mandatory Location Code.
4	Go to any row you want to narrow → Add a SKU, then a Batch if needed, then an Expiry if needed (only together with a Batch)	That row now covers only the inventory that matches the fields you filled in.
5	Go to the full file → Check that no location appears in overlapping rows	The file is ready to upload.

Upload and Review the Result

Step	Action	Expected Result
6	Go to the bulk upload option → Click to upload your file	The system checks every row in the file.
7	If the upload succeeds: Go to the upload result → Download the Success file	The Stock Take is created. The Success file lists the inventory added for each row, including SKU-level rows.
8	If the upload fails: Go to the upload result → Download the Error file → Fix every listed row → Re-upload the full file	The Error file lists every failing row and the reason, so you can fix everything in one go.

Important Notes & Limitations

Topic	What to know
All-or-nothing upload	If any row has an error, the whole upload fails. No rows are processed and no Stock Take is created. Fix every row listed in the Error file and re-upload the full file.
Location-only files	Files with only Location Codes work as before: every eligible item in each location is added. Leave the SKU, Batch and Expiry columns empty on rows you don’t want to narrow.
Mixed rows	One file can mix rows with different levels of detail, such as a location-only row for LOC-A01 and a Location + SKU + Batch row for LOC-B02. Each row is scoped by the fields it contains.
Overlapping rows	The same location must not appear in overlapping rows, such as once on its own and again with a SKU. This counts as an error and fails the whole file.
Sample template	The sample template shows how to add a SKU-level row next to location-only rows.

Troubleshooting & Common Errors

Any one of these errors fails the entire file. The Error file lists every affected row.

If the Error file reports this	Follow these steps to fix it
Batch or Expiry provided without a SKU	Add the SKU to that row, or remove the Batch or Expiry.
Expiry provided without a Batch	Add the matching Batch to that row, or remove the Expiry.
Invalid or unknown Location Code	Correct the Location Code so it matches a valid location in WMS.
SKU has no inventory in the uploaded location	Check that the SKU is stocked in that location, or remove the SKU from that row.
Batch or Expiry doesn’t match the SKU’s inventory in the location	Correct the Batch or Expiry to match what’s stocked for that SKU in that location.
Overlapping rows (for example, the same location uploaded once on its own and again with a SKU)	Keep one row per location scope and remove the overlapping row.
Location or stock already held by another Stock Take or operation	Wait for the other Stock Take or operation to finish, or remove that row.
Zero stock or restricted stock in the requested scope	Remove that row, or change its scope to inventory that is available to count.