1255 W 15th St,
Suite 810,
Plano, Texas, 75075
Bista AI Assistant for Odoo
Bista AI Assistant helps your teams get work done inside Odoo using the processes your company already follows. Sales, purchasing, manufacturing, inventory, finance and project teams each have an assistant with playbooks for their work. Those playbooks can be adapted to your rules, documents and approval requirements.
An assistant can pull together information from Odoo, email, shared drives and other systems you choose to connect. It can research a question, identify what needs attention, prepare a response or take an approved action. It works within the access rights of the person using it, and you decide which actions require a person to sign off.
See What Happens When A Supplier Is Late
Say a supplier tells your purchasing team that a shipment of aluminum housings will arrive three weeks late. The immediate question is bigger than the purchase order: Which production runs will be affected? Which customer orders are at risk? What can the team do about it?
In the example shown here, the Purchasing Assistant checks the supplier email and two purchase orders covering 2,600 units. It finds that the expected delivery has moved from September 29 to October 20. It then traces the parts through Odoo to three blocked manufacturing orders and five customer orders worth $418,600. One customer order carries a $1,500-per-day late delivery clause beginning October 13.
The assistant presents three options: expedite part of the shipment, move 60% of the volume to another supplier or change the production sequence. It also shows a weekly supply and demand chart so the team can see how each option affects the shortage. The figures and company names in this example are demo data.
The assistant traces a supplier delay from email and purchase orders through production and customer commitments, then compares possible responses.
The assistant helps the team get to an informed decision faster. Your people still review important results before acting on them.
Actions Go Through The Approvals You Set
You can allow an assistant to gather information and draft work while requiring approval before it sends an email, submits a purchase order or changes an Odoo record. Approval rules are set by role and playbook, so the right person reviews the right action.
The Approvals screen shows what the assistant wants to do, who requested it, which playbook and tool it would use, who must approve it and the amount involved when relevant. The approver can accept or reject the action. Requests and actions are logged for review.
In the demo shown here, pending items include customer shipment emails, a shipping label purchase, changes to manufacturing orders and a $38,376 purchase order. None goes through until its designated approver takes action.
Pending approvals show the proposed action, the responsible approver and any associated amount.
Your Processes, Built Into Playbooks
A playbook describes how your company handles a specific task. It brings together the steps, business rules, documents, data sources, tools and approval points needed to complete the work.
Each assistant comes with playbooks informed by Bista’s ERP project experience. We adapt them with you to reflect the way your company works. Your team can maintain them, add new ones and see a history of past runs. Playbooks can run when someone starts them or on a schedule.
For example, a sales team could use a Tender Go / No-Go playbook. Given a tender reference, the assistant can review the opportunity against the company’s capabilities, previous work and available capacity, then prepare a recommendation with the conditions for pursuing the bid. The playbook defines which sources it can use and which steps need approval.
Playbooks belong to your company. As your team refines them, its processes stay documented and available to the people who need them.
The Playbooks view groups work by assistant and shows required connections, schedules and run history. Each playbook shows its purpose, inputs and approval settings.
Assistants for The Teams That Use Odoo
| Assistant | What it helps with | Starting playbooks |
| Sales | Account research, pipeline review, bids and follow-up | Prospecting; Bid & RFP Response; Pipeline Review; Quote Follow-up |
| Purchasing | Supplier sourcing, quote comparison and late purchase orders | Vendor Sourcing; RFQ Comparison; PO Follow-up; Supplier Risk |
| Manufacturing | Scheduling, material shortages and work order readiness | Manufacturing Scheduling; Material Shortage; Work Order Readiness; Quality Follow-up |
| Inventory | Stock counts, replenishment and discrepancy analysis | Cycle Count; Replenishment; Stock Discrepancy; Excess & Slow-moving Stock |
| Finance | Month-end close, receivables, payables and cash visibility | Month-End Close; Collections & AR Follow-up; AP & Three-way Match; Cash Position |
| Project Management | Project kickoff, status reporting, risks and changes | Project Kickoff; Status Reporting; Risk & Issue; Change Order |
The starting playbooks are adapted to your business, and you can add your own. Assistants for other teams, including field service, customer service, quality and HR, are available on request.
Answers That Draw On More Than One System
The details needed to answer a business question often sit in different places. An order may be in Odoo, a delivery promise in email and the terms in a contract on a shared drive. Bista AI Assistant can bring those sources together, cross-check what it finds and show where its answer came from.
You choose which systems, folders and mailboxes to connect, and whether each connection is read-only or can support approved actions. Available sources include:
- Odoo and other business systems: orders, inventory, production, invoices, projects and customer records.
- Corporate email: commitments, changes and escalations captured in conversations.
- Shared drives and folders: contracts, specifications, procedures, proposals and past work.
- The web: information relevant to suppliers, customers, markets and regulations.
- Specialized data platforms: tender databases, industry tools, sales intelligence and internal applications.
Odoo access runs through Bista Odoo MCP, with controls over which models the assistant can reach and an audit trail of its activity. The demo screens also show connections to Microsoft 365, Apollo, SPS Commerce, a shared drive, web research, an industry pricing platform and a tender database.
Security and hosting
Bista hosts the assistant in a secure, compliant environment included with your plan. Your team does not need to build or operate the AI infrastructure.
The language models used by Bista AI Assistant are configured so your prompts, documents and business data are not used for model training. Assistants operate within the user’s access rights and can reach only the systems and data you allow. You can require approval before they send information, submit transactions or change records. Requests and actions are logged.
If your organization already has an agreement with a language model provider, you can use your own key. The assistant continues to use the same playbooks, hosting and controls. Contact us about bring your own key pricing.
Bista Solutions is an Odoo Gold Partner and an 8x Odoo Best Partner across North America. Bista is also ISO 9001 and ISO/IEC 27001 certified and has worked with regulated manufacturers since 2007.
Pricing
Plans have a fixed monthly price, with hosting and AI usage included up to the plan’s monthly token limit. Usage is pooled across the users on your plan.
AI Assistant Pricing
| Plan | Users | Monthly price | Monthly tokens | Plan details |
| Team 5 | Up to 5 | $250 | 1 billion | All six role assistants, starting playbooks and hosting |
| Team 10 | Up to 10 | $450 | 2 billion | More roles running in parallel, playbook customization support and approval workflows by role |
| Team 25 | Up to 25 | $1,000 | 4 billion | Multiple departments, playbook governance across teams and priority support |
| Enterprise | More than 25 | Contact us | Sized to your needs | A plan based on your departments and expected usage |
| Bring your own key | Based on scope | Contact us | Billed through your provider | Use your own model provider account with Bista's hosting, playbooks and controls |
Every standard plan includes the six role assistants, a starting playbook library, a playbook editor, access controls, approvals, an audit log and connections to the systems you authorize. AI usage is included up to the monthly token limit, and Bista monitors usage with you. Implementation and playbook customization are quoted separately based on scope.
See An Assistant At Work With Your Process
Tell us which team you want to start with and which task takes the most time. We’ll walk you through the relevant playbook and show how the assistant would work with your systems and approval rules.
FAQs
What is Bista AI Assistant?
Bista AI Assistant is an enterprise AI assistant that works by role. A Sales, Purchasing, Manufacturing, Inventory, Finance or Project Management Assistant follows your company’s playbooks, which contain the procedures, business rules, knowledge and tools your company uses to complete tasks. It works within the permissions and approvals you set.
What is a playbook?
A playbook is how your company completes a task, written down. It holds the procedure (the steps), the business rules (thresholds, terms, exceptions), the knowledge it draws on (documents, past work, product and customer context), and the tools it uses (Odoo, email, document storage, the web). Every assistant comes with pre-built playbooks, which you then customize for your business.
Who owns the playbooks?
You do. Playbooks are your company’s knowledge base. You manage and grow them, so operational know-how stays in the business when people move on and gets more refined over time.
How much does it cost?
Fixed monthly plans: $250 for up to 5 users (1 billion tokens a month), $450 for up to 10 users (2 billion tokens), and $1,000 for up to 25 users (4 billion tokens). Above 25 users, contact us for pricing. Hosting and AI usage within the ceiling are included.
What is a token, and why is there a ceiling?
Tokens are the unit AI providers bill by, covering both what the assistant reads and what it writes. Rather than passing a variable bill on to you, we set a fixed monthly price with a generous ceiling of 1B, 2B or 4B tokens depending on the plan, pooled across your users. We monitor usage with you, and if your teams consistently need more, we move you to the right plan.
Can we use our own LLM key?
Yes. With bring your own key (BYOK), the assistant runs against your own model provider account with the same playbooks, hosting and controls. Contact us for BYOK pricing.
Do the language models train on our data?
No. Every model we use is configured so your prompts, documents and business data are never used for model training.
Where is the assistant hosted?
In a compliant, secure hosting environment managed by Bista and included in your plan. There is no AI infrastructure for your team to build, secure or run.
What can the assistant actually do, and what needs approval?
Assistants research, analyze, prepare and draft work, and can carry out actions in your systems. Each assistant acts with the permissions of the people it works for. Each playbook defines which actions need a person to approve them before anything is sent, submitted or changed, and those actions wait in the Approvals list until someone approves or rejects them.
Which systems does it connect to?
Odoo and other business systems, corporate email, shared drives and folders, the open web, and proprietary data platforms such as industry databases, tender portals and sales intelligence tools, plus your own internal applications. The assistant reads across them together, which lets it cross-check facts and recommend a decision instead of answering from one system. You configure every connection, read-only unless you allow more, and Odoo access runs through Bista Odoo MCP with per-model control and full audit logs.
Do we have to roll this out to every department?
No. Many companies start with one or two teams and a task that takes significant time. We adapt the relevant playbooks, connections, and approval rules, then you can add more work and roles as needed.
What is a token?
Tokens are the units used to measure what an AI model reads and writes. Each plan includes a monthly token allowance shared by its users. If your team consistently needs more, we can discuss a plan that fits its usage.
Can the assistant change records or send messages without approval?
You set the approval requirements for each role and playbook. Actions you designate for review stay in the Approvals list until the assigned person approves or rejects them.
Can we use our own language model account?
Yes. Bring your own key is available for organizations that prefer to use their existing model provider agreement. Ask us about the options.