Operator guides · reviewed 23 September 2026

Put the workflow to work, then verify the record.

Each guide starts with the operating problem, follows the safe setup path and ends with the evidence a manager can check. Availability depends on your account, permissions and configuration.

IGFirstERP on Android

The owner still has to call staff to know what happened.

  1. Install the official IGFirstERP app from the linked Google Play listing.
  2. Sign in with an authorised business account and select the permitted business and location.
  3. Open the stock, sales, receiving or review task assigned to your role.
  4. Check the saved record and any unresolved exception before treating the task as complete.

What to verify

Confirm the action, user, location and resulting record in the business workspace.

Current boundary

Available tasks vary by role, enabled module, connection and app version.

See the buyer and product explanation

IGFirst POS on Android

Counter speed should not erase stock or payment responsibility.

  1. Install the official IGFirst POS app from its Google Play listing.
  2. Sign in as an authorised cashier and confirm the selling location.
  3. Search or scan a product, choose its permitted unit and review the visible price and quantity.
  4. Complete the sale using the supported payment path; verify its receipt and stock result.

What to verify

Review the final sale and payment state in IGFirstERP.

Current boundary

Offline eligibility and direct printing require the correct setup and supported hardware.

See the buyer and product explanation

Current iPhone access

An iPhone user needs a truthful access route while the native app is prepared.

  1. Use the approved web sign-in path provided to your business.
  2. Confirm the workflow is supported in the mobile browser and your role is authorised.
  3. Keep your team informed that native iOS availability will be announced separately.

What to verify

The web workflow saved its record and can be reviewed from the same business account.

Current boundary

The native IGFirstERP iOS app is upcoming with no announced release date.

See the buyer and product explanation

Publish a product with an owned route

Product photos and prices scattered across accounts leave the owner unsure what was posted.

  1. Choose the exact product, variation, media and stock location.
  2. Review the destination-specific caption, price, order link and media preview.
  3. Choose a connected Telegram destination or another route that shows ready in your workspace; use manual share when that is the available path.
  4. For scheduled routes, review the time and approval state; after sending, inspect each destination result and retry or repair failures.

What to verify

Inspect the route status and provider result; a prepared manual share is not a delivered post.

Current boundary

Instagram and TikTok direct publishing depend on provider approval and eligible accounts. TikTok direct publishing is immediate only. Official WhatsApp Groups publishing is pilot-gated.

See the buyer and product explanation

Prepare and publish Website Studio changes

A product can look ready online while its location, price or checkout path is not.

  1. Choose the website location and review connected products and prices.
  2. Edit the page or product presentation and save the draft.
  3. Preview the exact saved revision, then review domain, payment and shipping readiness.
  4. Publish that revision and verify the live product and checkout path.

What to verify

The published revision, location and visible product match the approved preview.

Current boundary

A saved draft is not a public website change; domain and provider checks may still be required.

See the buyer and product explanation

Take a paid order through fulfilment

Payment confirmation can be mistaken for completed picking or delivery.

  1. Open the paid order and confirm whether it is held, ready to prepare or awaiting a different action.
  2. Assign the package identity and record picking and packing work.
  3. Record dispatch, pickup or transport-park handoff with the responsible user and any exception.
  4. Confirm customer collection or delivery only when the configured evidence supports it.

What to verify

The package trail and customer-facing status show the same actual stage.

Current boundary

Sending to a transport park is an opt-in service and does not prove customer collection.

See the buyer and product explanation

Investigate a WooCommerce mismatch

A failed link can leave shop and website availability out of step.

  1. Confirm the WooCommerce store identity and the product or variation mapping.
  2. Check which stock location has authority and inspect the affected order or inventory event.
  3. Review the reconciliation or hold reason and use the authorised retry path.
  4. Verify the resulting website quantity or order state after recovery.

What to verify

The mapped product, location, order and retry result agree after reconciliation.

Current boundary

External webhooks and queues can delay work; a retry should not be described as successful until the result is checked.

See the buyer and product explanation

Review a Cortex-assisted Telegram task

A channel task should not begin with the wrong destination or content.

  1. Connect a permitted Telegram channel or group through the scoped setup path.
  2. Review the connection identity, permission state, proposed caption and media sample.
  3. Approve the exact task configuration or save it for later.
  4. Start the reviewed workflow and inspect its delivery state.

What to verify

The started task uses the same destination and content configuration that was approved.

Current boundary

Connection checks do not send a public post; provider and channel permissions still govern delivery.

See the buyer and product explanation

Use staff reports for owner review

Staff explanations arrive late and do not match the system figures.

  1. Have each authorised staff member submit the report for the correct period.
  2. Keep explanations and correction notes separate from the locked system figures.
  3. Review exceptions, assign named follow-up and close only the work that is resolved.

What to verify

The owner can see who submitted, the system figures and the unresolved next action.

Current boundary

A report strengthens review; it does not replace physical counts or management judgment.

See the buyer and product explanation