More, Sync and Offline Work in the Yardor Yard App

Everything under More in the Yardor Yard App — sync and conflicts, language settings, your device, switching warehouse, signing out — and how the app keeps your work safe offline: the outbox, stale snapshots, and which actions need a connection.

The day-to-day tabs — Queue, Scan, Moves, Yard checks — carry the work itself. The fifth tab, More, is the hub for everything less frequent: pending verification, walk-in registration, sync and conflicts, settings, update checks, your device, switching warehouse, and signing out. This article walks the More page first, then explains the sync engine underneath it, because that engine is what makes the whole app safe to use in a yard with patchy signal.

The More page, entry by entry#

• Current warehouse: shows the warehouse you are working in. Tap it to switch if your account belongs to more than one.
• Pending verification and Register a walk-in: the two gate back-office entries, covered in the gate article.
• Sync and conflicts: the state of everything waiting to reach the server. When there are conflicts, this entry carries a badge with the real conflict count — no badge means no conflicts.
• Settings: the app’s language (see below).
• Check for updates: runs the same update check the app does on its own at startup; the install article explains how updates, progress, and must-update versions work.
• My device: this phone’s identity (see below).
• Sign out: asks you to confirm first. Signing out never deletes the offline queue — work still waiting to sync stays on the phone and goes out after the next sign-in.

How offline work is kept: the outbox#

When you record work — a check-in, a photo, a move step, a check item — the app writes it into a local outbox on the phone first, bound to your account. When a connection is available, the app replays the outbox to the server in order, retrying with growing pauses when the network keeps failing. The sync pill at the top of the app shows this state at a glance: all synced, items waiting, or items that need your attention.

Reads work the other way: queue, placement, and check screens keep a snapshot of the last data they loaded. A snapshot older than 15 minutes is marked stale on screen, with the time it is from — use it to keep moving, but let it refresh before you treat it as the final word.

Actions that need a connection#

Some actions cannot be queued, because they only mean something if the server answers right away. The app never queues these; offline, it says a connection is needed and stops:

• Sending and entering the gate one-time phone code.
• Claiming a move from the pool.
• Rejecting a pending verification, and supervisor approvals that resubmit an entry or a departure.
• Creating a new yard check (its item list is built from who is on site at that moment).
• Fetching the arrival credential to show a driver.

Sync and conflicts, up close#

Open More → Sync and conflicts to see the outbox itself. Entries still waiting show what they are and how many times they have been tried; entries locked because a teammate is handling the same item are counted, not shown as yours to fix. Pull down, or tap the sync button, to force a full sync round right now.

Most waiting entries resolve on their own once the connection holds. A conflict is different: the server answered, and the answer is no — for example, the move was already claimed by someone else, or the visit changed while you were offline. Conflicts stay put until a person decides, and each one states its reason in plain words. For each conflict you can:

• Retry — send it again as-is (right when the conflict was a timing overlap that has since cleared).
• Hand over — pass the entry to the team so someone with the full picture can resolve it; the entry is marked handed over on your phone.
• Discard — delete the queued entry. The app asks you to confirm, because discarding means the work in that entry will not reach the server at all; use it only when the entry is genuinely wrong or already done another way.

Settings: language#

More → Settings holds the app’s language. Pick English, 中文, or Español and the whole app switches immediately — your choice is saved on the phone and stays until you change it. Nothing else about the app is configured here; warehouse rules and policies live in the web console, not on the phone.

My device#

More → My device shows this phone as the warehouse knows it: the model, the system version, the app version, and the device identifier. It is read-only — there is nothing to edit here. It matters on the day something goes wrong: support and your admin identify a phone by these details. If your admin revokes this device on the web (from the team settings, where member devices are listed), the app returns to the sign-in screen and tells you why; sign-in stays blocked for that device until an admin allows it again.

Choosing a warehouse — including the empty state#

Right after sign-in, the app settles your warehouse. With several warehouses, you pick the one you are working at — and can switch later from More. With exactly one, it is selected for you. With none, the app shows an empty state instead of a broken home screen: your account is not part of any warehouse yet. Ask your warehouse admin to add your account to the warehouse; once they have, sign in again and the warehouse appears. There is nothing to fix on the phone for this state.

Yardor features used in this article#

• Yard App bottom bar → More (warehouse switch, sign out with the queue kept)
• More → Sync and conflicts (outbox, force sync, conflict retry / hand over / discard)
• More → Settings (language) and More → My device