Product Variables

Manual: Product Variables via Bulk Action (OMS/WMS)

With this bulk action, you can configure which product variables are required per SKU at once within afosto.app (OMS/WMS).

Product Variables determine which data must be registered during:

Goods receipt
Stock movements
Picking and shipping
Warehouse scanning

Use this bulk action when working with batch products, serial numbers, expiration dates, RFID, or additional logistics requirements.

What does this bulk action do?

You define per SKU which registrations are mandatory.

Examples:

Must a batch number always be entered?
Is a serial number required per item?
Must an expiration date be recorded?

After processing, these requirements become active immediately in warehouse processes.

Step 1 Go to the bulk action

Log in to afosto.app. Go to Processes. Open Bulk actions. Choose Product Variables. You will now see a spreadsheet input screen.

Step 2 Unique name

Give your bulk action a unique reference.
Click Next to continue.

Step 3 Paste your data into the spreadsheet

You can copy and paste your data directly from Excel or Google Sheets. The following columns can be used (* = required):

[object Object]

What is required?

SKU (required)*

The existing product code in Afosto. Must match exactly. All settings are linked based on this SKU.

All “Required” fields (required)*

For this bulk action, all variable fields must be filled in because you must explicitly state whether something is:

Yes (required) or
No (not required)

So per SKU you define which registrations are mandatory in your warehouse process.

Explanation per variable

**Batch Number Required **Use this for batch-managed products. Examples:

Food
Cosmetics
Products with production runs

At receipt, a batch number must always be entered.

**Serial Number Required **Use this for unique products. Examples:

Electronics
Devices
Machines

Each individual unit receives a unique serial number.

**RFID Required **Use this if you work with RFID tracking. During stock movements, an RFID tag must be recorded.

**Best Before Required **Use this for products with an expiration date. A date must be entered during receipt.

**Dimensions Required **Use this when length/width/height must be recorded. For example for:

Shipping optimization
Storage calculations

**Weight Required **Use this when weight must be registered. Important for:

Shipping methods
Carriers
Customs documentation

Step 4 Check your input

Always verify:

Do all SKUs exist?
Did you correctly enter Yes/No for each field?
Do the settings match your warehouse process?

**Note: **If you make something required, a user cannot continue without entering that data.

Step 5 Execute the bulk action

Click Execute.

The system validates the rows.
If successful, the settings become active immediately.

From that moment:

Selected fields are enforced in the warehouse.
Missing data is blocked.
Changes apply instantly in OMS/WMS.

Practical example

[object Object]

In this example:

CANDLE-RED requires a batch number.
LAPTOP-15 requires a serial number and weight.

Important notes

All Required fields must be filled in.
Settings directly impact warehouse processes.
Making a field required blocks actions when data is missing.
Changes apply immediately in real time in OMS/WMS.