When "Receiving Verification for Physical Attributes" is enabled, Logiwa IO will check products for missing Dimensions, Weight, or Volume. Depending on your client's setup, you will encounter either a Warn or Prevent flow.
Mobile App Receiving
When scanning a product on the mobile app, the system checks for missing attributes before taking you to the quantity entry screen.
The Warn Flow
If the client is configured to "Warn User Only", a popup titled "Information" will appear.
Skip & Continue: Tap the "Continue Receiving Anyway" button to skip entering attributes and proceed directly to quantity entry.
Update Data: Tap "Enter Physical Attributes" to open the data entry screen. Inputs are optional in this mode, meaning you do not have to fill out every field to proceed.
Suppress Warnings (One-by-One Receiving only): You can check the "Don’t show this again until a different product code is scanned in this receiving flow" box. This mutes the warning if you scan the same item again consecutively. (Note: Scanning a different product resets this suppression ).
This functionality is available for One-by-One Receiving only, cannot be utilized for the standard receiving flow.
Users without "Edit Product Physical Attributes during Receiving Verification" access will be warned with the below popup.
The Prevent Flow
If the client is configured to "Prevent Receiving", a popup titled "Attention" will appear.
No Skipping: You cannot skip this step. The "Continue Receiving Anyway" button is hidden.
Entering Data: You must tap "Enter Physical Attributes" to proceed.
Note: If you do not have the necessary permissions to edit attributes, the "Enter Physical Attributes" button will be hidden, and you will be forced to cancel the receiving operation for that item.
In this scenario, receiving of that item can be resumed only after required physical attributes are entered through the product pack type master data (or through mobile by any other user with access).
Users without "Edit Product Physical Attributes during Receiving Verification" access will be warned with the below popup.
Using the Enter Physical Attributes Bottom Sheet
When you select "Enter Physical Attributes," a bottom sheet slides up to allow you to input the missing data directly from the scan screen.
Navigation and Layout
Dynamic Titles: The top of the sheet displays the specific pack type you are currently editing (e.g., "UOM" or "Scanned Pack Type").
If multiple pack types require verification, it is asked user for which pack type they would like to start with the editing.
Dynamic Layout: Bottomsheet only shows the physical attributes that are selected under client settings as to be verified and ones that are missing.
E.g: If dimensions & weight is tracked, and only weight value is missing for an item, this bottomsheet only shows the weight entry sheet. Dimension sheet is not shown since it has no missing value, volume sheet is not shown since it is not selected to be verified.
Pagination: If your client's settings require verifying multiple pack types (e.g., both the Scanned Pack Type and the UOM) or multiple physical attributes the sheet will display a counter like "1/3" or "2/3". Use the "Next" and "Previous" buttons to page through them.
State Caching: Don't worry about losing data while navigating; the system caches your entries. If you enter data on page 1, move to page 2, and then return to page 1, your entries will remain intact.
Exiting: You can close the bottom sheet without saving by tapping the Cancel button (available on the first page) or by swiping down (quick exit). This returns you to the initial warning popup.
Entering Values and Units
Numeric Keypad: Tapping into a field opens the device's numeric keyboard. There is no auto-focus, meaning you must manually tap each field you wish to edit.
Mandatory vs. Optional Fields:
In the Warn Flow, no fields have asterisks, and you can leave fields blank or as "0" to save partial data.
In the Prevent Flow, all required attribute fields are marked with an asterisk (*). The "Save/Next" button triggers an error, if any required field is left blank or as "0".
Unit Selection: The default units are Inch, Cubic Inch, and Pound (unless priorly defined). You can use the dropdowns to select different units (e.g., ounce, Kg, cm) if needed.
Saving and Proceeding
Partial Update: When you tap "Save", the system performs a partial update, modifying only the physical attributes for the specific pack types you edited. It will not alter the product's description, barcode, or unedited pack types.
Immediate Resumption: Upon a successful save, you will instantly return to your receiving flow.
In Standard Receiving, you will navigate directly to the Quantity Entry screen with a success message.
In One-by-One Receiving, the success toast appears automatically, the quantity counter increments, and the scanner is instantly ready for the next item
Subsequent Scans: Once you have provided the missing attributes, the system permanently updates the product. Subsequent scans of that item will not trigger the bottom sheet again.
Web UI Receiving
If a client is set to Prevent Receiving, attempting to receive incomplete products via the Web UI will be blocked.
If the client is set to "Warn", the Web UI will allow the transaction.
Receive PO Screen: If you attempt to receive a PO, and even one line contains a product with missing attributes, the entire action will fail. The system will not receive any lines and will display an error message listing the specific SKUs missing data You must update the product master data before proceeding.
Add Inventory Screen: The system will block manual inventory additions and display an error indicating which attributes are missing for the SKU.
Excel Imports & Open API
If a client is set to Prevent Receiving:
Excel Import (Add Inventory): If you attempt to bulk import inventory via Excel, rows containing products with missing attributes will fail. Valid rows in the file will still be processed successfully (partial failure). Check the Import Log for the specific failure reason.
Open API: API endpoints for PO Receiving (/v3.1/PurchaseOrder/receive) and Inventory Creation (/3.1/inventory/create) will return a 400 Bad Request if attributes are missing. The response body will detail the SKU and the missing attributes.
Couldn’t Find What You Were Looking For?
Visit our Help Center to search for more documents!