OLT AI: the ERP assistant that acts only with your approval.
OLT AI is OLT Solutions' permission-scoped ERP assistant. It answers questions across your connected business data and can prepare draft invoices and inventory moves for your review. OLT AI does not create, edit, or delete ERP records until you explicitly confirm the proposed action. OLT AI uses local Ollama by default. Only the default local Ollama configuration has zero data egress to an external model provider and no metered provider cost. If an operator explicitly configures an external OLT AI or agent endpoint, that provider processes prompts and relevant ERP context externally, and its use may incur provider charges.
Choose the right setup path
Platform access is by invitation. Contact OLT to discuss the right setup for your business.
Platform access is invitation only. Contact OLT to discuss your project.
- Local Ollama by default OLT AI uses local Ollama by default.
- Local privacy and provider cost Only the default local Ollama configuration has zero data egress to an external model provider and no metered provider cost.
- External endpoint disclosure If an operator explicitly configures an external OLT AI or agent endpoint, that provider processes prompts and relevant ERP context externally, and its use may incur provider charges.
How OLT AI works
Ask OLT AI a question, review the live ERP context it returns, and approve or discard any proposed action before data changes.
- Ask across supported modules One question reads the shipments, stock, invoices, POs, suppliers, CRM, and pricing your enabled access allows — no jumping between screens.
- Drafts real work It prepares a draft invoice or an inventory move from live data, ready for your review.
- Confirm-before-write OLT AI does not create, edit, or delete ERP records until you explicitly confirm the proposed action.
- Respects your permissions It can only see and touch what your role allows. Server-side RBAC applies to the AI the same as to you.
- Best-effort audit logging OLT AI attempts to record tool activity and confirmed changes in its audit log, but logging is best-effort; a logging failure does not block an otherwise successful action.
- Works across 10 of the 12 modules Supplier Portal, WMS, Accounting, and TMS are verified examples of supported connected modules it operates on, subject to enabled access. Marketing and Google Reviews are outside its module scope today.
Explore the workflows behind OLT AI
Open the connected product pages behind common OLT AI questions. Inside the ERP, every answer and proposed action still follows your role's access.
- Inventory Tracking See the stock, warehouse, replenishment, and lot records that give OLT AI its inventory context.
- Accounting, Invoices & Quotes See the quotes, invoices, payments, and receivables OLT AI can read when your role allows.
- Transportation Management See the loads, routes, vehicles, stops, and delivery records OLT AI can use for transport questions.
Where does OLT AI send model requests?
OLT AI uses local Ollama by default. Only the default local Ollama configuration has zero data egress to an external model provider and no metered provider cost. If an operator explicitly configures an external OLT AI or agent endpoint, that provider processes prompts and relevant ERP context externally, and its use may incur provider charges.
Can it change my data?
OLT AI does not create, edit, or delete ERP records until you explicitly confirm the proposed action. OLT AI attempts to record tool activity and confirmed changes in its audit log, but logging is best-effort; a logging failure does not block an otherwise successful action.
Will it see data it shouldn't?
No. The same server-side role-based permissions that govern your account govern the AI. It can only read and act on what your role allows.
Which modules does it work with?
The supported connected modules — 10 of the 12, including Supplier Portal, WMS, Accounting, and TMS — and, within those, only the ones your enabled access allows. Marketing and Google Reviews are outside OLT AI's module scope today. Inside that scope, it reads the one live data model the rest of OLT runs on.
Put OLT AI to work with your approval.
Only an active tier's catalog feature list and module allowance define whether that plan includes OLT AI; plan access and terms are agreed directly with each client. OLT AI uses local Ollama by default. Only the default local Ollama configuration has zero data egress to an external model provider and no metered provider cost. If an operator explicitly configures an external OLT AI or agent endpoint, that provider processes prompts and relevant ERP context externally, and its use may incur provider charges.
Choose the right setup path
Platform access is by invitation. Contact OLT to discuss the right setup for your business.
Platform access is invitation only. Contact OLT to discuss your project.