Frequently asked questions

Read completion, lines, productivity, on-time rate and exceptions for the warehouse.

Task viewing permission is required. Check the warehouse and business-day range first.

Select one warehouse or all warehouses and check the update time. Read KPIs alongside their denominators, due range and batch progress. Open tasks or operations and printing to investigate warnings.

Compare task records only after matching warehouse and date ranges.

Completion, on-time rate and lines per hour have different denominators.

Live overview differs from historical snapshots; changing warehouses changes the figures.

If figures stop updating, check connectivity and timestamps, then worker health. Do not rebuild batches to repair charts.

Follow order cards, deadlines and risks to locate work needing attention.

Check the warehouse and tasks visible to your account.

Choose status and search filters to find order cards. Compare completed lines, total lines, deadlines and risk indicators. Open task details to inspect actual quantities and release status.

After task completion, verify whether release status confirms shipment.

App completion, successful synchronization and DG release are separate stages.

The board tracks work; it does not perform shipment release.

For missing orders, clear filters, check warehouse access and verify the task exists.

See workers' batches, progress and floor activity.

Task viewing permission is required. A worker account and a phone device are different things.

Select a warehouse and inspect each worker's current work. Compare assignments, progress and recent activity; connectivity alone does not prove completion. Use dispatch to review and change the responsible worker when needed.

The worker card and task details should agree on ownership and progress.

A worker may use different devices; assignments target workers.

This page does not create an App subscription or prove work has been downloaded.

If a worker is missing, check role, warehouse scope and assignments, then the device's last-seen time.

Review waiting and active work and reassign it when necessary.

Viewing requires task access; reassignment also needs task change permission.

Select a warehouse and verify batch, current worker and progress. Select an eligible worker and use Reassign. Ask the new worker to pull the new assignment in the App and the previous worker to stop using the old one.

Check the new assignment in DG and the new work and quantities in the App.

Real reassignment creates a new assignment ID and increments generation; old reports are rejected.

Reassignment is not a progress reset. The old App can still display old work until rejection is received.

Missing controls may indicate permissions or state restrictions. For rejected reports check for an old assignment before rebuilding anything.

Review historical snapshots, compare warehouses and export CSV.

Report access is required. Match dates, granularity and warehouse before comparisons.

Choose a date range and hour, day, week or month granularity, then apply. Read trends, details and warehouse comparisons with their displayed scope. Recalculate if needed and download the CSV.

Check the recalculation result and ensure CSV fields match the selected report.

Snapshots are recalculated about every 10 minutes; live overview can temporarily differ.

Missing history does not mean zero activity. Retention and warehouse permissions apply.

Check dates and warehouse before worker schedules. Refresh the query; do not repeat floor operations to fill a chart.

Rotate overview, orders, workers and dispatch on a floor display.

Sign in with a suitable read-only account and warehouse scope.

Open the wall and verify the warehouse and displayed panel. Use pause, previous/next and fullscreen controls; automatic rotation runs every 30 seconds. Exit the wall before opening help or other operations.

Verify that data updates and floating controls do not cover it.

The question-mark button is hidden during playback; this guide remains available after exit.

The wall cannot release shipments or administer users. Account permissions still apply.

For a frozen screen, check pause, network and sign-in state, then system health.

Preview standard or marketplace files and create DG orders from valid rows.

Prepare .xlsx, .csv, .txt or .tsv, not legacy .xls. Choose an available warehouse and matching format.

Download the sample CSV for headers; select file, format and warehouse, adding an opening password when needed. Use Preview. Check valid, failed, skipped and order counts. Correct errors in the original file and preview again. Review the duplicate warning before import. Check results and history, then create a batch in DG orders.

Compare imported orders/lines and failed rows. Preview alone creates no orders, and failed rows are excluded.

Required fields: request_date, customer_name, product_name, original_qty. Quantities must be positive with at most 5 decimals. Orders group by order number, date and customer.

Limits: 20 MB, 50,000 rows and 300 columns. Use supported text encoding. Importing the same file again creates duplicate orders.

Use row errors to check dates, numbers and headers; check the format for sheet errors. Remove Excel protection if unsupported rather than repeatedly forcing imports.

Maintain native orders and create batches from orders awaiting batching.

An available warehouse is required. Account permissions and order state govern editing and batching.

Use Add order, enter order, customer, date, warehouse and lines, then Save order. Each line needs a product name and positive quantity. Check code, specification, unit and short name; edit only unbatched orders. Select pending orders, set batch name, mode and due time, then Create batch; continue to batches and allocation.

Check the saved message; successful batching returns a batch reference and order count.

Orders used by tasks can be cancelled instead of deleted to retain history. Read the actual result.

Batched or shipped orders cannot be edited as unassigned data. Odoo orders are maintained in Odoo.

For no warehouses ask an administrator to check scope. Batching failures require checking state, existing tasks, permissions and source.

Maintain shorter names for App display and speech.

Check product code, name, specification and unit. Only administrators can change the site-wide threshold.

Choose a pending product or add a short name; verify specification and unit before saving. Lookup prefers matching code/name with exact specification/unit, then whole-product entries; renamed products can fall back to the same code. Check affected unbatched lines and confirm the short name in newly downloaded App work.

The success message reports how many unbatched order lines were updated.

The length threshold controls the pending list, not automatic truncation. Saved aliases take precedence over format-generated short names.

Batched orders retain their existing names. Deleting an alias does not clear existing order values.

Check code, name, specification and unit when unmatched. Existing downloaded batches are not rebuilt to update names; preserve work progress.

Allocate native DG orders from available supply, then dispatch; Odoo quantities remain controlled by reservations.

Native allocation needs an undispatched batch and change permission. Odoo reservation quantities cannot be reallocated here.

Select a batch, enter product supply and use Allocate proportionally for largest-remainder proportional allocation. Check each customer's allocation, adjust and save individual lines if needed; Restore ordered quantities is available before dispatch. Choose a worker and dispatch after reviewing quantities; the App downloads through My work.

Check success, worker and locking messages. Zero-allocation lines are marked as not dispatched.

Ordered 40, allocated 30, actual 25: each quantity is kept separately. Floor workers may report a short pick.

After dispatch DG and the App cannot reallocate or add local orders. Supply entry is not an Odoo inventory transaction.

Read the lock reason: already dispatched, Odoo source or empty batch. Missing workers require account/permission checks, not repeated dispatch.

Review line reports, assignments, short picks, posting and printing before releasing shipment.

Actions depend on state and permissions. Verify references, current assignment and actual quantities first.

Select a task and read order, lines, reports and release status; choose a new worker for reassignment. After floor completion review shortages and required checks. Odoo supports BACKORDER/DROP; native DG orders do not create Odoo backorders. Release, inspect posting commands and release results, then separately check print jobs.

SHIPPED confirms shipment in DG. COMPLETED only confirms floor work is complete.

Reassignment creates a new ID. After the old report is rejected, pull the new work rather than reallocating the old batch.

Cancellation applies to unfinished tasks. Pending or unknown posting results must be checked before any further release attempt.

Use Check now in task command details for UNKNOWN/RETRY_WAIT. For CONFLICT compare source changes and contact an administrator.

Track posting commands, print jobs and Odoo reservation reconciliation separately.

Keep the task and command/job references. Viewing and changing require the appropriate permissions.

Filter posting by open, conflict, failed or all and read reasons and attempt counts. For UNKNOWN inspect task details first. For RETRY_WAIT check source connection and permissions before Check now. Inspect remote print results. For partial or unknown SortingGo results, review physical output before deciding in manual review.

Confirm posting and printing independently. Reprints have a new record and reason and do not change shipment results.

Timeout can mean a lost response rather than no action. Reprints are distinct from retrying an original request.

Never blindly resend unknown results. A completed service response does not prove physical paper output.

Check service, printer, remote job and per-record results; prevent duplicate labels and share only non-secret diagnostics with administrators.

Find mobile devices, last activity and token state, and revoke access when needed.

The device must reach DG over the LAN. Device viewing/revocation permissions are required.

Search by user, name or UID and check platform, version and last seen. Obtain pairing QR/address from configuration, set the App connection and sign in with a worker account. For lost or retired devices verify the target and revoke tokens; sign in again when reuse is intended.

The App can access the worker's assigned work and the last-seen time updates.

A phone's own 127.0.0.1 is not the server. Use a reachable LAN address and numeric port.

TOTP-enabled accounts cannot use device login. App DG access requires Std or above; DG itself does not check subscriptions.

Check network, server address, port, firewall and account first. For missing work check its worker assignment; never include passwords in reports.

Create, disable and reset accounts and assign roles and warehouse scope.

Role management permission is required. Give floor and read-only accounts only the access they need.

Create a user and set a password of at least 8 characters. Assign roles and warehouses, save and ask the user to verify accessible functions. Verify the target before disabling or resetting; clear two-step authentication only when appropriate.

Test permitted and forbidden functions as the target user, not just with your administrator account.

Default admin/distributiongo credentials produce a reminder rather than a forced change. Change them before production use.

Five failed attempts lock access for 15 minutes. Disabled status, password reset and TOTP are separate settings.

Missing menus require role and warehouse checks. Lost TOTP access requires the administrator's existing reset procedure.

Get pairing details, configure new batch references and maintain print-template versions.

Permissions vary by setting. Check the active version and preview before saving.

Verify the QR's LAN address, server and organization for App pairing. Set batch prefix, date, separator and sequence digits; preview before saving. Add a print-template version, verify its purpose/revision, then activate or retire it.

Confirm the saved result, batch preview and active template revision.

Preview does not create a batch. Existing print jobs retain their templateRevision.

Template version records do not replace the Print Service label designer. Existing batch references are not rewritten.

For pairing failures check the LAN address. Verify corresponding Print Service configuration before activating a template; do not create a fictitious revision.

Inspect order sources, core health, worker heartbeats and background job probes.

System viewing permission is required. Native DG is built in; Odoo is optional.

Check each source individually; unconfigured Odoo does not imply native DG failure. Read core version, warnings, key expiry, open command counts and oldest pending time. Inspect heartbeats and use the background job probe when necessary, then check its response.

Health, worker and probe results should agree. Record non-secret reason codes for failures.

Odoo key rotation requires operations staff to update configuration and restart. A warning is not completed rotation.

Unreachable Odoo, denied access and unsupported version/route require different fixes, not just retries.

Check services and network, then bot rights, add-on and key. Observe UNKNOWN commands before rebuilding data.

Sign in with a DG account, separately from Odoo accounts.

Verify the DG server address and prepare DG credentials and your authenticator if two-step login is enabled.

Enter username and password. Default credential hints appear only while those credentials remain active. When requested, enter the authenticator's six-digit code. Check your user and available warehouses after sign-in; sign out of shared computers.

Verify your account and authorized DG pages rather than the Odoo website.

Passwords need at least 8 characters. Five failed attempts lock access for 15 minutes.

Help cannot reset passwords or bypass locks. Mobile App connection uses a different entry point.

Ask an administrator for credential issues and check device time for code issues. For connection errors check the server and keep passwords out of reports.

Change your password and manage optional TOTP authentication.

Sign in first. Have your current password and authenticator ready and check whether the account is also used by the App.

Open password settings from the sidebar, enter current/new/confirmation values and save. In two-step settings scan the QR and confirm with the six-digit code as instructed. Check the success message and sign out when finished on a shared computer.

Use the new password next time; enabled TOTP adds a verification step.

TOTP-enabled accounts cannot use device login; avoid accidentally blocking floor workers.

Lost authenticators require an administrator reset. Never report QR codes, secrets or verification codes.

Check the 8-character minimum and matching passwords. Correct device time for TOTP failures, then ask an administrator if needed.

Read page guides, search FAQs, configure the floating button and prepare reports.

Guides follow your account permissions and enabled sources. Basic content requires no external internet.

Use the question mark for guide or FAQ. Drag to dock; arrow keys fine-tune position. Search and filter, or choose a feature card and related guides. Restore/reset the button or check content updates in settings. Preview a report before copying or opening an email draft.

Read the content version and source. A copied notification does not mean an email was sent.

Restore the hidden button from the sidebar Help Center. Language follows the DG interface.

Built-in help works without external internet; updates and external documents require connectivity. No AI assistant is included.

Reopen if loading fails. Incompatible updates preserve existing content. Copy the report manually if no email app is available.

Read ready Odoo deliveries and create DG work batches.

Enable the Odoo Provider, install the matching add-on and grant bot access. Only one-step delivery is supported.

Complete product, order, inventory and reservation work in Odoo. Search the pool, check due dates, select ready deliveries and create a batch with the appropriate mode. Dispatch from batches, work and sync in the App, then release in DG so Odoo processes shipment.

Verify both the DG source reference and the Odoo shipment result; App completion is insufficient.

Odoo reservations determine quantities. DG does not reallocate them locally; short-pick remainder policy is handled at release.

Odoo Online is unsupported. Two- and three-step routes are not listed as ready work.

For an empty pool check Odoo readiness, route and reservations, then system health, add-on and API key permissions.