Use the YiTaiCOS Mobile App camera

Open the mobile scanner, let the camera read a QR code or barcode, and continue with the action allowed for the selected workflow.

Before you start

Sign in to the correct workspace in the native YiTaiCOS Mobile App on a supported phone or tablet. Your account must have permission for the scanner workflow you need. In an ordinary browser, use Manual input or a keyboard scanner when a native camera is unavailable. Allow camera access when the device asks.

Privacy and App filing

In Android website version 0.5.0 (12) and recent iPhone builds, read the first-start privacy notice before continuing. Not now keeps your account and existing data; business sign-in, workspace loading, diagnostics and camera/photo permission requests remain inactive until you agree. Permissions are requested when you use the corresponding feature.

The notice, Login and Settings → Legal & privacy open the full Privacy Policy and Terms of Use. They also show App ICP filing 浙ICP备2025205212号-2A with the official MIIT verification link. This is the App filing, distinct from the website filing.

Android website build 12 keeps you signed in when you read these documents.

For Android updates, use the app's update notice and confirm Download, then Install. Keep the existing Scanner App installed; uninstalling or clearing its storage can remove local settings and sign-in data.

Steps

  1. Open a scanner workflow

    Open the YiTaiCOS Mobile App. On Home, choose Shipping scan for a package or waybill, or choose Product inbound, Product outbound, or Loss outbound for warehouse work.

  2. Wait for the camera

    In the native app, the scanner opens with the Camera / typed input profile. If the device asks for camera access, allow it. Wait for Native camera active before presenting a code. An ordinary browser may require Manual input or a keyboard scanner instead.

  3. Scan the code

    Keep the QR code or barcode inside the camera frame. The app reads QR codes and common 1D/2D barcodes and shows the resolved result in the scanner card.

  4. Complete the allowed action

    Follow the result card. Inventory work may require an exact variant, a warehouse, a quantity, and Confirm. Shipping work may require the packed order and Confirm packing. A dispatch product scan can use the active order when the configured stage and your permission allow it.

Enter inventory quantities

In Android website build 13 and iPhone TestFlight build 56, tap the quantity between − and + to type a whole number from 1 to 999. You can still use the two buttons. This works for a single product, selected variants and the product collection review. Choose a warehouse and check each quantity before confirming. Typing a number does not book stock; permissions and available stock are still checked when you confirm.

Configure your team's scanning rules

An administrator decides which checks the company requires; operators should not disable checks to bypass an error.

  1. Select the correct workspace in the web dashboard. Open Orders → Settings → Stage blueprint and edit the stage before the intended destination, not just the destination stage.
  2. Under Picking and packing, configure Scan items to count every ordered unit. Disable it only if your intended process is label-only confirmation. Allow manual item entry permits item/quantity selection instead of item scans; it is not permission to skip all checks.
  3. Scan package label again requires the same package label to be checked again, after picking when enabled. Confirm packing requires confirmation to complete the scanning workflow. Allow manual stage moves lets permitted users move orders to the next stage without scanning. Existing strict configurations keep it off. The switch is unavailable when all three scanning/packing options are off. An explicit manual exception never bypasses scanner or automatic checks and does not count items or fabricate confirmation.
  4. In Product scanning and packing confirmation, inspect the label confirmation trigger and its After scanning behavior. A configured transition and the current stage's prerequisites still apply; a label is not a universal bypass.
  5. Save, reload the settings to verify persistence, then reopen the Order in the app. Test one disposable Order before using the rules for live work. Required fields, shipment locks and user permissions remain effective.

Allow finish button is a separate, default-off setting in the same Blueprint menu. To use it, first turn off Scan package label again, enable Allow finish button, save and reload, then reopen the Order in the app. Required item scans still apply. Enabling label re-scan again disables the button. The app shows success only after server confirmation; this setting does not change manual Web stage moves.

Confirm packing does not itself enable that button. In the confirmation-only single-scan flow, the deliberate label scan itself confirms packing. Turning all checks off does not promise automatic shipment; use the permitted regular Orders action. Moving an Order's stage is not proof that the carrier physically received it.

Single shipping-label scan

  1. Open the main camera and present the complete saved carrier label or tracking barcode/QR. Do not use a product SKU to confirm a package.
  2. If one Order matches, the app reads that Order's current workflow. Multiple matches require deliberate selection; do not choose by guesswork.
  3. If picking is required, scan the matching item once for each required unit and read the remaining quantities. Where manual picking is allowed, select the item and quantity explicitly. Merely finding an Order does not count its contents.
  4. Complete the required label check and confirmation for that stage. In the confirmation-only flow, the label scan can perform the confirmation immediately; do not expect an additional button. An error is not a successful booking.
  5. Read the green success receipt and Order reference before continuing. If uncertain, verify the Order in the web dashboard rather than repeatedly submitting it.

Collect several labels with multiscan

  1. Start at the main camera before scanning the first label. Use the bottom-centre mode icon between the flashlight and ABC to switch to multiscan.
  2. Scan labels one after another. The first accepted result fixes the collection type: Products, Orders or Shipping labels. Different resource types cannot be mixed in that collection.
  3. Check the collected shipping numbers. Repeated codes or aliases for the same Order must not create duplicate rows or extra quantities. Remove a mistaken entry from the temporary list; this does not delete the Order or reverse an existing booking.
  4. Select eligible shipping labels and use the available packing-confirmation action. Only eligible selected rows are submitted. Successful rows leave the list; failed rows remain for review. Do not treat selection or removal as shipment confirmation.
  5. Products with several variants require an explicit variant choice; do not assume the main SKU adds every variant. Product and Order collection is not a general bulk stock/shipping command. Inventory movements still require their normal explicit warehouse, quantity and confirmation steps.

An active picking/packing Order or detail view can hide the mode switch. Return to the main camera before starting multiscan. In version 0.5.0 the single-label success receipt returns to the main camera automatically; older builds can require Back. A missing switch inside an active Order does not by itself prove an outdated app. Check the installed version in TestFlight/app information when reporting a problem.

Camera tools and recovery

  • Flashlight controls illumination; ABC opens manual code entry. Enter the complete code, not a cropped tracking number. Manual entry uses the same permissions and matching rules.
  • To intentionally scan the same physical code again, remove it fully from view before presenting it again. A continuously held code is not another item.
  • If the code is recognized but the result is slow, distinguish camera recognition from server lookup and booking. Wait for the outcome; do not keep tapping confirmation while a request is pending.
  • If a previously shipped Order is reset to pending shipment, verify its actual stage and rules first. Older app builds can retain a completed-Order marker and reject the same label within that session. Report this with the installed build; a source correction is not proof that your installed app contains it.
  • If manual movement on the web is blocked, ask the administrator to inspect the current stage requirements, permissions and separate manual-stage setting. Save and reload any deliberately authorized Blueprint change. Manual picking does not bypass packing/label requirements; scanners still require every enabled check.

Report a scanning problem

In Android website 0.5.0 and iPhone TestFlight 0.5.0 (55), direct confirmation-only label scans stay in one result/loading view through the server confirmation. There is no intermediate packing camera. A successful command shows the green receipt, then returns to the main camera after three seconds. Errors stay errors; the app must not report success before the server accepts the action. The server still validates current stage, checks and permissions during the command. Multiscan keeps its collection and explicit selected-label confirmation.

Provide the app version/build, iOS or Android version, workspace, Order reference, approximate time and timezone, single/multiscan mode, the code type (product or shipping label), and the visible error code. Use approved support channels; do not publish customer labels, addresses or credentials. Include whether the green receipt appeared and whether the Order changed stage in the dashboard.

Expected result

The scanner shows the matched product, order, tracking value, label, or warehouse/location context. The available action and any resulting stock or fulfilment change depend on the selected workflow, your workspace permissions, and its workflow settings.

If something goes wrong

  • The native camera does not start: check the device camera permission and that you are using the native app on a supported device. In an ordinary browser, open Manual input and use typed or hardware input instead.
  • The code is not recognised: keep the complete code in the frame, try again with the correct label, and check that you opened the matching Shipping or warehouse workflow.
  • A result is blocked: read the message on the result card. Inventory scans need an exact variant and warehouse; fulfilment scans can be blocked by the order stage, packing state, or permission.