GWMS PDA Client — Warehouse On-Site Operations

Last updated: 2026-05-21

1. Scenario

The GWMS PDA Client is an Android barcode scanning application used for on-site warehouse operations including receiving, stock counting, stock transfer, outbound shipping, returns processing, and label printing.

Warehouse staff can scan and process tasks directly at receiving docks, shelves, sorting areas, and returns stations without having to return to a desktop computer to enter data.

Applicable scenarios:

• On-site operations requiring rapid scanning by location, SKU, box, wave, or return label.
• Verifying inventory, picking progress, or return status while scanning on the PDA.
• Sending shipping labels directly to Bluetooth or WiFi label printers.

Not applicable scenarios:

• Back-office operations such as inbound order review, customer data maintenance, quotation configuration, and batch import/export must still be done on desktop.
• Customer-side actions such as order creation, reconciliation, and business quotation review are not on-site warehouse tasks and are not suitable for the PDA.

2. Instructions

Prerequisites

Please confirm the following before starting:

1. Device requirements: Android 7.0 or above scanning PDA, connected to the network, capable of reading 1D/2D barcodes.
2. Account requirements: Must have a GWMS Code, username, and password; the account must be bound to an available warehouse.
3. Installation: Use the current installation package provided by your administrator or implementation team.
4. Printing requirements: If on-site label printing is needed, prepare a Brother, Zebra, or GPrinter label printer in advance. Bluetooth printers must be paired with the PDA first; WiFi printers must be on the same network as the PDA.

2.1 Install the App and Check Version Updates

Entry point: PDA Home Screen -> GWMS app

1. Install the APK provided by your administrator or implementation team on the Android PDA.
2. On first launch, the app displays a splash screen and checks for available updates.
3. If an Update dialog appears, tap Update Now to download; tap Later to continue to the login flow.
4. This documentation is based on client version 1.0.2. If button names or page layouts differ after future upgrades, refer to what is actually displayed in the app.

For hardware reference, the following image shows a typical Android barcode scanning PDA device:

2.2 First-Time PDA Login

Entry path: GWMS PDA — Login

1. After opening the app, enter the GWMS Code provided by your administrator.
2. After successful resolution, the system prompts Connected to: [system name] and enables the username, password, and captcha fields.
3. To switch the interface language, use the language dropdown on the login page: English, 中文, Español, Français.
4. Enter your Username, Password, and Captcha, then tap Login. The password field has an eye icon on the right — tap to toggle between masked and plain text display for verifying long passwords.
5. To have the PDA remember your credentials, check Remember username and password below the captcha before logging in. On the next login, after the GWMS Code resolves, the username and password will be auto-filled and the cursor will land directly on the captcha field. Unchecking the box and logging in will clear previously saved credentials for this GWMS Code. When multiple people share a PDA, follow your site's policy on whether to enable this feature.
6. To reset your password, tap Forgot Password. The system will prompt you to contact your administrator or supervisor.

System feedback:

• Invalid GWMS Code -> Invalid GWMS Code or Domain not resolved, please check GWMS Code.
• Captcha not loaded or expired -> Please reload the captcha.
• Empty username, password, or captcha -> field-by-field prompts to fill in.

2.3 Main Interface and Bottom Menu

Entry path: GWMS PDA — Home

1. After successful login, the app defaults to the Receive page.
2. The + button in the bottom-right corner expands or collapses the bottom menu.
3. There are 6 fixed modules at the bottom: Receive, Count, Move, Ship, Return, Me.
4. The currently active module is highlighted. Tap other modules to switch pages.

2.4 Receiving — Inbound, Putaway, and Inventory Initialization

Entry path: GWMS PDA — Bottom Menu — Receive

1. Enter an inbound order number in the top input field and tap Query to look up the receiving order.
2. The list displays the current status of each inbound order, e.g., To Receive, Partially Received, To Putaway, Partially Putaway, Putaway Complete.
3. Tap a status button. The system presents available operations based on the order's current status and receiving mode. Options may include Receive By SKU, Receive By Box, Putaway By SKU, Putaway By Box, or Verify SKU Properties. Modes that are not applicable to the current order are automatically hidden.
4. If an order is still in Draft or To Audit status, the PDA will not allow receiving and will prompt Please complete inbound order review first.
5. Scanning a location label directly on the Receive page enters the inventory initialization page. If the scanned location does not belong to the current warehouse, the system prompts Please scan a warehouse location label.

After entering a specific operation, continue processing according to the mode provided by the system:

• Receive By SKU: Confirm actual received quantity per SKU.
• Receive By Box: Scan by box number and confirm actual received quantity in each box.
• Putaway By Box or Putaway By SKU: Assign putaway locations for received boxes or SKUs.
• Inventory Initialization: Scan location first, then scan SKU/GSKU, enter quantity, and submit.

Receive By SKU — Key operations:

• Scan a SKU code: the scanned SKU row is highlighted (a green checkmark appears after the code and the row turns green), the list auto-scrolls to that row, and focus automatically lands on that row's "Current Receive" input field — in most cases, just adjust the quantity and tap Submit.
• When the "Current Receive" input field is focused, the number is fully selected, so new input replaces the old value for quick overwrite of the default quantity.
• Tap the "Unreceived" column (either number or label) on a row to reset "Current Receive" to the remaining receivable quantity (Expected − Received).
• If a SKU is confirmed as not received in this submission, enter 0 in "Current Receive" and submit. Do not enter a negative quantity. When the actual quantity differs from the expected quantity, submit the counted quantity first, then review the exception quantity and reason later in the desktop inbound order details or receiving records.
• Tap the SKU code (green GSKU text): Clears that row's "Current Receive" quantity in one tap. In rare cases where PDA system settings unexpectedly inject scanned content as keyboard input into the quantity field (you may see strange values like "911", "908", "22" matching the tail digits of the scanned SKU code appear in "Current Receive"), simply tap the green SKU code to instantly clear it and re-enter — no need to manually delete characters. The scan state (green checkmark) is preserved; no re-scan is needed.
• Each successful scan emits a crisp "beep" as feedback, making it easy to confirm the action was received in noisy warehouse environments.

Putaway By SKU — Key operations:

• Each location input field (top Current Location, each SKU row's location, and locations added via +Location) supports three input methods — tap for keyboard input (typing one character brings up a fuzzy-match dropdown with substring matching, prefix matches ranked first); long-press for a location picker dialog grouped by zone; scan via barcode scanner, which writes the scanned location code into the currently focused location input field, or into the top Current Location if no field is focused.
• When the scanned location code differs from the field's existing value, the system shows a confirmation dialog to prevent accidental overwrites. If the entered or scanned location code is not in the current warehouse's location list, a prompt appears both when leaving the field and when tapping Submit, requiring correction before submission.
• When top Current Location is filled, scan a SKU code: the scanned SKU row is highlighted (only the most recently scanned row has a pink border), a green checkmark appears after the code and the row turns green, the list auto-scrolls to that row, and focus moves to that row's location field — convenient for then scanning an actual location to overwrite the default.
• When top Current Location is empty, scan a SKU code: the scanned SKU row is similarly highlighted and the list auto-scrolls. Additionally, the system shows a location distribution dialog for that SKU's existing inventory in this warehouse (each row displays location, total quantity, total volume), helping the operator decide where to place this batch. After closing the dialog, focus lands on that row's location field, ready for scanning an actual location. If a scan occurs before the dialog is closed (whether SKU or location), the system judges based on the scanned content — scanning a SKU jumps to the next SKU row, scanning a location writes to the location field — SKU codes will never be mistakenly written into the location field.
• When top Current Location is filled, tap a row's GSKU/code area to fill that row with the top location. If filled incorrectly, tap the same row again for one-tap undo (no dialog, only applies to the most recently click-filled row). To clear a location filled earlier (via scan, long-press picker, or previous click), tapping that row again shows a confirmation dialog before clearing.
• SKU rows that have been fully put away are no longer editable (quantity, location, and +Location button are all grayed out). Before submission, the system validates per SKU that the total putaway quantity entered does not exceed the remaining putaway-able quantity (multiple rows for the same SKU created via +Location are summed). Any excess or location error is immediately flagged and submission is paused.
• Each successful scan emits a crisp "beep" as feedback.

Putaway By Box — Key operations:

• The top Current Location and each row's location field support three input methods (tap for keyboard with fuzzy match, long-press for location picker, scan via barcode), consistent with Putaway By SKU. Scanning to overwrite an existing location also triggers a confirmation dialog.
• Scan a box label: the box is selected with a pink border (only the most recently scanned box at any time), and the list auto-scrolls to that box. If top Current Location is filled, the scan writes the top location to this box and marks it with a green checkmark. If top Current Location is empty, the box is merely selected — scan a location next to write to it.
• Highlighted box priority: As long as there is a pink-bordered box on screen, the next scanned location code will be written directly to that box (even if no field is focused — it won't be written to top Current Location). Overwriting a non-empty old value still triggers a confirmation dialog.
• Explicitly cancel selection: If you genuinely want to scan a new value for top Current Location (rather than writing to the currently selected box), tap the top Current Location field — the pink border is immediately removed and the next scan goes to the top field. Tapping another box's location field also cancels the current pink border.
• Tapping a box's box number (GSKU/code area, not the whole row) has four outcomes, depending on current state:
  • Box is already put away: rejected with a "completed" message.
  • Box's location was just filled by tapping the box number (most recent): one-tap undo, no dialog.
  • Box already has a location (filled via scan, long-press picker, or previous click): confirmation dialog shown, clears location on confirm.
  • Box location is empty and top Current Location is also empty: pink-border selects this box (ready for the next location scan).
  • Box location is empty and top Current Location is filled: fills the top location into this box, recorded as the most recent click-fill (one more tap for one-tap undo).
• Putaway-completed boxes remain visible in the list but with grayed-out, non-editable location fields — scanning or tapping will not modify them.
• On submission, all boxes with filled locations that have not yet been put away are reported as putaway data for this batch. The system first validates all location codes are legal, otherwise prompts and pauses submission.

2.5 Count

Entry path: GWMS PDA — Bottom Menu — Count

The Count module supports three typical workflows: direct scan to check inventory, initiating a new stock count from the inventory query page, and continuing to process existing count sheet details.

2.5.1 Inventory Query

On the Count page, without entering any count sheet number in the top Query area, scan directly with the barcode scanner to query inventory:

1. Scan a location label: opens the inventory query page showing current inventory at that location, summarized by SKU.
2. Scan a SKU or GSKU: queries inventory by item, results summarized by location. If the same barcode matches multiple SKUs, a product selection list appears first for you to confirm which one.
3. On the inventory query page, pull down and release to refresh the current query results.

2.5.2 Start a New Stock Count

After completing the inventory query in 2.5.1, you can generate a new count sheet based on the query results:

1. On the inventory query page, tap Start Count.
2. The system shows Confirm to start a new count? to prevent accidental taps.
3. After confirming, the system generates a new count sheet and directly enters the count page for that sheet (continue with steps in 2.5.3).

2.5.3 Counting

Verify actual quantities item by item against an existing count sheet:

1. On the Count page, enter a count sheet number in the top field and tap Query to look up the existing count sheet.
2. The list displays statuses: Unchecked, Checking, Checked.
3. Tapping a count sheet status navigates to different pages based on status:
   • Unchecked or Checking: enters the count page to continue processing.
   • Checked: enters the inventory sync page.
   • Cancelled count sheets only show a status message and do not navigate further.
4. On the count page, the list shows all SKUs in the count sheet with their locations and expected quantities. Each row can be processed as follows:
   • Scan that row's SKU code or single-tap the row: opens a count dialog pre-filled with the row's expected quantity as the default suggested value. You can directly tap Submit (actual = expected), or tap the field to auto-select-all and overwrite with the actual counted quantity, add remarks, then Submit.
   • Double-tap the row: skips the dialog and directly submits with "actual quantity = expected quantity". Suitable for the common case where expected matches actual and no remarks are needed.
5. After a row is submitted, the count sheet's remaining uncounted items refresh in real time.
6. Before the count sheet is explicitly finalized (i.e., before tapping "Complete this count"), any detail row can be re-counted repeatedly — scan or tap the row again, the dialog shows the last submitted actual quantity, which can be modified and re-submitted. The most recent submission prevails. Only after completing the count are the details truly finalized.
7. After the last detail is counted, the system shows a Finalize this count? confirmation dialog: tap Confirm to finalize the count sheet — status becomes Checked, details are locked, and no further modifications are allowed. Tap Cancel to continue modifying any detail (still in the re-countable state from point 6), and trigger finalization again when ready.

2.6 Move — On-Site Stock Transfer

Entry path: GWMS PDA — Bottom Menu — Move

1. Enter a transfer order number in the top field and tap Query to look up an existing transfer order.
2. In the list, Unmoved, Processing, and Moved statuses can all be entered to continue transfer details. Cancelled transfer orders show a Transfer order has been cancelled message.
3. If you scan a location label directly on the Move page, the system shows a confirmation dialog, e.g., Start a new move from location A1-01-06?.
4. Tap Confirm to create a new on-site transfer flow. If the scanned content is not a location code, the system prompts Scan a location to start a stock move.
5. During the transfer process, both successful and failed details remain on the page. Failed items display a failure reason for on-site review.

2.7 Ship — Wave or Order-Based Outbound

Entry path: GWMS PDA — Bottom Menu — Ship

1. The top input field label is Wave / Order / Tracking #. Based on the format of the scanned or entered content, the system automatically determines the operation type: a wave number starting with W filters the wave list by wave number; a customer code + date + sequence outbound order number opens an order detail dialog; other content is treated as a tracking number and navigates to the order review page (see 2.8).
2. With the top field empty, tap Query to load the default wave list. Tap a wave to enter the wave orders page.
3. On the wave orders page, tap Pick List to enter different pages based on the current wave's picking type. Order-based picking opens the order-based picking page; SKU-based picking opens the SKU-based picking page and prompts you to scan the source location first before continuing.
4. When tapping a single order on the wave orders page, you can also manually confirm Confirm [order number] has been shipped?.
5. If the site switches to order-based outbound mode, the ship page changes to an order list, supporting lookup by invoice number or Store Code-Invoice Number.
6. During order-based picking, after the current order is completely picked and a printer is configured, the system sends labels to the connected printer.

2.8 Ship — Order Review by Tracking Number

Entry path: GWMS PDA — Bottom Menu — Ship — Scan tracking number in top field

The final checkpoint before outbound: scan a tracking number to enter the order review page, scan each SKU as listed by the system to confirm the physical items, and finally submit a Pass or Fail (with reason) conclusion.

1. Scan a tracking number in the Ship top input field — as long as the scanned content is neither a wave number nor an outbound order number, the system automatically navigates to the Order Review page and loads the corresponding order. After entering the page, the soft keyboard is not automatically invoked to avoid interfering with scanning. If you genuinely need to manually type a tracking number, tap the Tracking # field.
2. The upper half of the page shows basic order information: Tracking #, Order #, Wave #, Status, Created, Outbound. Outbound only shows a timestamp if the order has already been marked as shipped — this field is empty for normal unshipped orders. If an order was marked shipped and then returned, or system records don't match physical items, this timestamp is a key reference for troubleshooting.
3. If this order has been reviewed before, a reminder banner appears below the order info: a previously passed review shows a green banner with the previous reviewer and time, and automatically disables the Pass/Fail buttons with the message This order has passed review, preventing duplicate reviews. A previously failed review shows a pink banner — first line is the previously entered failure reason (bold), second line is the reviewer, third line is the time (right-aligned). The buttons remain enabled, and this submission will overwrite the previous failure result.
4. After the order loads, all SKU rows for that order appear below. Each row shows SKU code, GSKU, product name, and current cumulative scanned count / required total (e.g., 0/3). Each time the SKU code is scanned, the first matching incomplete row increments by one. When the required count is reached, a green checkmark appears after the SKU code and the code itself turns green. In rare special cases, double-tap a row's SKU code to manually mark that row as complete. Single-tap does nothing, preventing accidental operations.
5. A progress line at the bottom — X/Y skus reviewed (Chinese: X/Y 个 SKU 已复核) — updates in real time with each scan. On the right is an Auto Pass checkbox.
6. Once all SKUs are confirmed, tap the bottom button to submit your conclusion: Pass — the review passes (if any SKU rows are not yet fully scanned, the system first shows a confirmation dialog; passes on confirm). Fail — the review fails, a dialog appears requiring you to fill in a failure reason (required, e.g., "damaged packaging", "missing items", "wrong label attached"). After submission, the system records the failure status and reason. The interface then automatically closes and returns to the Ship home page.
7. If Auto Pass is checked: when all SKUs for an order are fully scanned, the system automatically records a Pass and immediately clears the current order, ready for the next tracking number. The reviewer just needs to keep scanning — scan tracking number, scan all SKUs for that order, auto-pass, scan the next tracking number, scan its SKUs, in a continuous loop without ever tapping any buttons. The Auto Pass checkbox state persists across consecutive order reviews. If a particular order needs to be failed, uncheck Auto Pass first, process that single order via the Fail flow, then re-check it.

2.9 Returns — Counting, Task Execution, and Return Order Viewing

Entry path: GWMS PDA — Bottom Menu — Return

The Returns module has 3 tabs: Count, Execute, Return Orders, covering the complete flow from receiving a package to processing completion.

2.9.1 Count — Photo Capture, AI Recognition, and SKU Entry

Entry path: GWMS PDA — Bottom Menu — Return — Count

1. Enter the Count tab. The system automatically opens the camera preview. Aim at the package label and manually tap the capture button.
2. The system invokes AI to recognize the label, extracting tracking number, customer, dimensions, weight, etc.
3. The system uses the tracking number to automatically check for an existing return order:
   • Existing in-progress return order: directly enters the count details page to continue entering SKUs.
   • Existing closed or voided return order: enters read-only view mode with an informational message.
   • No return order: enters create mode. The system pre-fills recognition results. Confirm or supplement:
     • Tracking No. (required, can be pre-filled from recognition, editable).
     • Package Location (required, can be scanned).
     • Customer (optional, selectable via picker).
     • Photo documentation (the captured label photo is automatically included; additional photos can be taken, up to 6 total).
     • Dimensions and weight (supports CM/KG and IN/LB bidirectional conversion).
4. After creation, on the lower half of the same page, scan SKUs one by one for counting:
   • Scan a SKU barcode. The system queries backend SKU information.
   • 1 result found: fills directly. Multiple results: picker dialog. 0 results: can choose Add to Remarks (code written to header and detail remarks).
   • Enter the counted quantity.
   • Add more SKU details as needed.
5. If the tracking number matches an outbound order, the system automatically loads the outbound order's SKU list, which can be directly imported as counting details.
6. After counting is complete, tap Submit. The system saves in order: create/update header -> upload photos -> submit details.

Header and details during creation are saved in the frontend draft first. They are only committed to the backend in one batch when the final submit button is tapped. Unsaved drafts are discarded when leaving the page.

2.9.2 Execute — Complete Tasks

Entry path: GWMS PDA — Bottom Menu — Return — Execute

1. Enter the Execute tab. By default, it shows all tasks with Pending status under the current warehouse.
2. The top supports quick filtering by tracking number: scan or enter a tracking number and tap query.
3. Tap More Filters to expand: Current Location, SKU, GSKU, Task Type (Restock/Destroy), Customer.
4. Each task card shows: Task Type (Restock/Destroy), Tracking No., SKU, GSKU, Current Location, Pending Quantity.
5. Tap a task card to enter the execution interface:
   • Restock Task: Confirm SKU and quantity -> scan or enter restock location -> enter execution quantity (defaults to pending quantity; reduce for partial completion) -> tap Restock Complete.
   • Destroy Task: Confirm SKU and quantity -> enter execution quantity -> tap Destroy Complete.
6. For partial completion, the system automatically splits the remaining quantity into a new pending task.
7. Cancelling tasks is supported: tap a task card to open the dialog, then tap Cancel Task.

2.9.3 Return Orders — View and Finalize

Entry path: GWMS PDA — Bottom Menu — Return — Return Orders

1. Enter the Return Orders tab. It displays the return order list, filterable by main status (In Progress/Closed/Voided) and execution status.
2. Each list item shows: Return Order No., Tracking No., Main Status, Customer, Package Location.
3. Tap a return order card to enter the detail page, where you can view:
   • Header summary: Main Status, Claim Status, Count Status, Decision Status, Execution Status, and quantity summaries for each stage.
   • Counting detail list: Counted quantity, decision quantity (Restock/Destroy), executed quantity (Restock/Destroy), decision status, and execution status for each SKU.
   • Associated task list: Pending and completed tasks under this return order.
   • Package photos: Up to 6 header photos.
4. In-progress return orders allow adding or editing counting details from the detail page.
5. In-progress return orders support swipe-left actions: Edit (modify carrier, dimensions, weight, customer, etc.) and Complete (confirm processing is finished).
6. Box consolidation and forwarding function entry points are retained in the return order detail page.

2.10 Me — Account Info and Printer Configuration

Entry path: GWMS PDA — Bottom Menu — Me

1. Enter the Me page to view current login account details: Username, User ID, Warehouse, Warehouse ID, Department, Tenant ID, Client ID.
2. Tap Log Out to return to the login page.
3. Under App Settings, you can check Order-Based Outbound Mode. After changing, the system prompts you to restart the app. After restart, the Ship page switches to order-based mode.
4. Under Label Printer Settings, you can select Brother, Zebra, or GPrinter.
5. After connecting a printer, the page shows the current brand, model, connection method, and address or Bluetooth MAC. Tap Test to send a test label; tap Forget to disconnect the current printer.

Result: After completing the above setup, warehouse staff can log into the PDA, switch between main modules, process on-site scanning operations, and connect to a label printer as needed.

3. Supplementary Notes

3.1 Which Warehouse Does the PDA Use After Login?

The PDA does not show a separate warehouse selection page after login. The system enters the app using the account's current default warehouse and loads zone and location data for that warehouse.

If an account is associated with multiple warehouses, first verify in the back office that the account's default warehouse is correctly configured, then have the warehouse staff log into the PDA.

3.2 Receiving and Review Are Two Separate Entry Points

The PDA handles on-site receiving, putaway, and inventory initialization — not inbound order review.

If an inbound order is still in Draft or To Audit status, the PDA will only prompt Please complete inbound order review first. These operations must first be completed on desktop, then return to the PDA to continue receiving.

3.3 Why Does the Ship Page Have Two Display Modes?

The Ship module has two working modes:

• Wave mode: Displays a wave list, suitable for organizing picking and shipping by wave.
• Order-based mode: Displays an order list, suitable for on-site processing directly by order.

Switch via GWMS PDA — Me — App Settings — Order-Based Outbound Mode. The app must be restarted for the change to take effect.

3.4 Two Things to Confirm Before Connecting a Printer

• Bluetooth printer: First complete Bluetooth pairing at the PDA system level, then return to GWMS PDA — Me — Label Printer Settings to select the device.
• WiFi printer: The printer and PDA must be on the same network, otherwise the app cannot discover the device.

If a test print fails, first check that the printer is powered on, the network is available, and the current page shows the correct brand, model, and connection address.

3.5 List Pull-to-Refresh and Scroll-to-Load

The four primary modules — Receive, Count, Move, Ship — are all paginated lists with consistent behavior:

• Pull down from the top of the list and release to refresh back to the first page. A brief message appears after loading showing how many records were fetched.
• Scrolling to the bottom of the list automatically loads the next page. A brief count message similarly appears when done.
• If the current page is the last page, scrolling to the bottom shows a No more (Chinese: 没了) message indicating there is no more data. This message appears only once per last-page session to avoid repeated prompts. After the next pull-to-refresh, scrolling to the last page can trigger the message again.

4. FAQ

Q1: Why can't I enter my username and password on the login page?

A1: Usually the GWMS Code hasn't been resolved yet. First enter a valid GWMS Code and wait for the page to show Connected to: [system name] and display the captcha, then enter username and password. If it still says Domain not resolved, please check GWMS Code, contact your administrator to verify the code is correct.

Q2: Why can't I open an inbound order for receiving on the PDA?

A2: First check the inbound order's current status. If it is Draft or To Audit, the PDA will directly prompt Please complete inbound order review first. This means the order hasn't reached a receivable state yet and must first be reviewed on desktop.

Q3: Why did my Ship page turn into an order list instead of showing waves?

A3: This means Order-Based Outbound Mode has been enabled. Go to GWMS PDA — Me — App Settings and uncheck Order-Based Outbound Mode. Restart the app as prompted, and the Ship page will revert to the wave list.

Q4: Why can't the printer be found?

A4: First distinguish the connection method. Bluetooth printers must be paired in the PDA system settings first. WiFi printers must be on the same network as the PDA. Then return to GWMS PDA — Me — Label Printer Settings and re-scan for devices. Once the page shows the brand, model, and connection address, tap Test to confirm it can print normally.

Q5: Why did I log into a different warehouse than the one I wanted?

A5: The PDA loads data based on the account's current default warehouse and does not provide a manual warehouse switching option. If the warehouse is wrong after login, have your administrator check the default warehouse bound to this account, then re-log into the PDA.

Q6: Why did scanning in Ship take me directly to the Order Review page instead of querying waves?

A6: The Ship top input field automatically determines the action based on scanned content format — content starting with W is a wave number, customer code + date + sequence is an outbound order number, everything else is treated as a tracking number. When a tracking number is scanned, the system assumes you want to review that order and automatically navigates to the Order Review page. To query waves or outbound orders, scan the corresponding format. Do not scan tracking numbers if you don't intend to review.

Q7: What do the three tabs in the Returns module do?

A7: Count is for photo capture, AI label recognition, and SKU counting — the first step after receiving a package. Execute is for viewing and executing restock or destroy tasks, which are automatically generated after the customer issues decisions on desktop. Return Orders is for viewing all return orders and their processing progress, and for finalizing completed return orders. The three tabs correspond to the three stages: Receive -> Process -> Manage.