Support

Get the count moving again.

Find the right route for setup, operating questions, or account access. Include the exact count, warehouse, or variance reference when one exists.

Choose the closest route

Product, implementation, or application help.

Sending the right context first makes a warehouse issue easier to diagnose without exposing unnecessary inventory data.

Route 01 · Understand

Product questions

Review the operating model, eight connected areas, roles, and controlled workflows.

Read product overview →
Route 02 · Configure

Implementation help

Prepare warehouses, bins, items, opening balances, count policy, and assigned responsibility.

See implementation →
Route 03 · Resolve

Application support

For access or operating issues inside ERP.ai, include the affected reference and what you expected to happen.

Email support@erp.ai →

Useful context

Identify the controlled object, not a screen position.

A durable reference lets support follow the same relationship chain the inventory process uses.

Warehouse or locationProvide the warehouse code and, where relevant, the exact zone or bin code.
Item or balanceProvide the SKU, unit, and location. Do not send secrets or account credentials.
Count workProvide the count plan, sheet, or count-line reference and its current state.
Variance decisionProvide the variance reference, disposition, status, and the operation that did not behave as expected.
Website navigation

Information lives here

  • Product explanation
  • Cycle-count process
  • Implementation and start guidance
Separate surfaces
ERP.ai support context

Application work lives there

  • Account and access state
  • Live records and workflow
  • Saved process references

Include the reference. Keep the trail intact.

For application help, tell us the exact controlled object and expected next state.

Email support
Made with Proto