Menu
Help centre

Choose the right mobile access for your task

The mobile browser, home-screen shortcut and native companion are different ways to reach TerminalERP. Start with the access currently available to your workspace.

Before you start

Check your account, enabled modules and role. Native app release and distribution must be confirmed separately from browser access. Use the real workspace address and normal sign-in; complete required account verification and security setup through the available browser process.

Follow these steps

  1. Open your workspace in a supported phone browser and sign in.
  2. Choose the permitted business task and open the full record before making a change.
  3. If you want a home-screen shortcut, use the signed-in installation guide and the options your browser provides. A missing install button does not mean the workspace cannot be used in the browser.
  4. If your organisation has confirmed native access, obtain the app through its verified distribution route. Do not use an invented or unofficial download link.
  5. In the native companion, use the tasks available to your role. Follow a browser handoff for setup, bulk changes or detailed administration that is not completed natively.
  6. After submission, inspect the result. If the response was interrupted, use the available recovery guidance or check the record before retrying.

Check the result

The task should be reflected in the same workspace under the applicable permissions and business rules. A successful screen transition alone is not proof that a financial, stock or external payment action completed.

Connection and device notes

Workspace records and mutations require connectivity. Do not assume offline record access or queued financial and stock actions. Camera, notification and download behaviour depends on the app, device and enabled workflow. Confirm native delivery and physical-device acceptance separately.

If you get stuck

Record the task, approximate time, device, browser or app version and the message shown. Preserve unsaved work. Never send a password, API key or private customer document in an ordinary support screenshot.

Keep going