SAP Business One
SAP Business One runs the mid-sized company end to end — sales, purchasing, inventory, accounting — usually with a small team and no capacity to answer the same operational question forty times a week.
SAP Business One runs the mid-sized company end to end — sales, purchasing, inventory, accounting — usually with a small team and no capacity to answer the same operational question forty times a week.
What SAP Business One holds, and why that matters here
Business One is the SME edition of the same idea: one system holding orders, stock, invoices and customers for a company of tens to a few hundred people. The distinguishing feature is not the data model but the staffing. In a large enterprise a dedicated team fields internal lookups. In a Business One shop, that job lands on whoever is nearest, usually alongside their real one.
That makes the case for connecting an assistant unusually strong here. The volume of questions is lower than in a large enterprise, but the cost of each one is higher, because it interrupts someone whose time is not fungible.
- Sales — quotations, orders, deliveries, returns and their document flow.
- Inventory — stock by warehouse, committed and ordered quantities, price lists.
- Purchasing — supplier orders, goods receipts, and what is inbound.
- Accounting — customer balances, ageing, incoming payments and credit notes.
- Business partners — customer and supplier records with their terms.
Questions Elbi can answer from Business One
What is the status of quotation 4021?
Where a document sits in the sales flow — quoted, ordered, delivered, invoiced — without anyone opening the client.
How much of this do we have?
Stock by warehouse with committed quantity separated out, which is the number that actually matters when promising a customer.
What does this customer owe?
Balance and ageing, so a salesperson knows before they walk in rather than after.
What is the price for this customer?
The applicable price list rather than the default, which is where most quoting errors originate.
Has the supplier shipped?
Purchase order and goods receipt status for the person who has promised a date to a customer.
What did we sell last month?
Simple period totals that would otherwise mean building a report or asking the person who knows how.
How Elbi reads Business One
- Its own Business One user, not a borrowed loginYour administrator or partner creates a dedicated user for the assistant in the company database it needs, with authorisations limited to the documents and master data in scope. Nobody's personal login is shared, and nothing breaks when a colleague changes their password.
- Reads go through the Service LayerThe Service Layer is Business One's web API. Where your version provides it, the assistant signs in to it as that user and reads sales documents, item quantities, business partner balances and price lists. Working through Business One's own business objects, rather than querying tables directly, keeps the connection in terms your partner already knows.
- The question is tied to a document and a business partner"What is the status of quotation 4021" becomes a read of that quotation and the documents copied from it — order, delivery, A/R invoice — and whether each is open or closed. A customer asking about "my order" is matched to their business partner code through your own sign-in, so they only ever see documents under that code.
- Stock is reported as available, not just on handFor stock questions it reads in-stock, committed and ordered quantities per warehouse and reports what can actually be promised, rather than the on-hand figure that tempts people into over-promising.
- The reply is a sentence, in the asker's languageField names, series prefixes and status flags stay behind the scenes. The customer gets a sentence in Arabic or English with the document number, date and amount where they help.
- Anything it creates can start as a draftCreating a sales quotation or logging an activity against a business partner is switched on per action, if at all. The safer Business One pattern is a draft document that a colleague reviews and adds, so nothing reaches the ledger without a person.
What the assistant's Business One user can and cannot do
| Direction of access | Read-only authorisations by default. Drafting a quotation or recording an activity is enabled deliberately, one action at a time, and can wait for a person to confirm. |
|---|---|
| Who can see what | Customers are matched to their own business partner record through your sign-in. Staff see what their own role in the business would let them see. Item costs, gross profit and purchase prices can be kept out of scope entirely. |
| Credentials | You create the Business One user and hold its password. Changing the password or withdrawing its authorisations cuts the assistant off at once, and needs nothing from us. |
| Where data goes | A balance or stock figure read from Business One is used for the answer and nothing else. The conversation carrying it is destroyed within 24 hours, normally as soon as it ends, and no outside AI service ever sees the figure. |
| Audit | Each lookup can be logged with the question, the document or record read, the agent and the conversation — useful when someone later asks why a customer was quoted a particular balance. |
| If it is unavailable | If the Service Layer or the company database cannot be reached — during an upgrade, for instance — the assistant says so and offers a person. It does not quote a stock figure it could not read. |
What this replaces in a Business One company
In a company of this size the bottleneck is almost always one or two people who know the system. Everyone routes questions to them. They are also the people running month end, chasing suppliers and covering for absences, so the queue forms behind exactly the individuals who can least afford it.
An assistant with a read-only view of Business One takes the routine half of that queue away entirely. Not the judgement calls — those still need the person who knows the business — but the lookups, which are the majority by count and contribute nothing when a human performs them.
It also matters out of hours. A mid-sized distributor takes orders and questions well outside the hours it staffs, and the alternative to an assistant is not a faster human — it is silence until morning.
Where Business One companies put it to work
Wholesale and distribution
Stock and price questions, which are the entire sales conversation and the main source of quoting errors.
Light manufacturing
Order status and material availability, asked by people who are on a shop floor rather than at a desk.
Professional services
Invoice and payment status, which is most of what a small finance function is asked about.
Retail groups
Multi-branch stock visibility, so a branch can answer for another branch without a phone call.
Getting value from Business One
Start with the questions that already reach the one or two people who know Business One. In most companies they are a short list — is it in stock, where is my order, what does this customer owe, what price do they get. Counting a month of those messages and calls is normally enough to choose the first scope, and it is rarely the list anyone would have guessed.
Pricing deserves early attention. Business One can hold several price lists, period and volume discounts, and special prices for individual business partners, so the figure a customer should hear is often not the one on the item master. Having the assistant read the price that actually applies, and say plainly when it cannot work one out, is where the effort tends to pay back first.
Leave judgement where it is. Credit holds, returns and anything that moves money stay with a person. The assistant earns its place by taking lookups off the desk of the same person who also runs month end.
Connecting Business One, step by step
- List the questions, then the documents behind them"Where is my order" means sales orders, deliveries and A/R invoices; "do you have it" means items and warehouses. Working from the questions keeps the assistant's authorisations short and easy to review.
- Bring in your Business One partner earlyMost companies run Business One with an implementation partner who knows the add-ons, user-defined fields and approval procedures in your database. They are usually the quickest route to creating the user and confirming what your version exposes through the Service Layer.
- Create the user and set its authorisationsRead-only on the forms in scope, no authorisation on the rest. Whether that user needs a licence of its own is worth settling with your partner at this point rather than after go-live.
- Map user-defined fields and local namesUDFs, user-defined tables, warehouse codes and item groups are mapped, so the assistant says "the Jeddah warehouse" rather than a code, and reads the custom field your team actually relies on.
- Test the awkward documentsPartial deliveries, cancelled orders, an item spread across several warehouses, a business partner with many contact persons, a customer asking about someone else's order. These are rehearsed before launch, because they decide whether people trust the answers.
- Go live on a few questions, then widenStart with stock and order status, read a month of real questions, then add balances or pricing once the first answers have held up.
Personal and financial data in Business One
Business One holds more personal data than it first appears: contact persons on every business partner, phone numbers and email addresses, delivery addresses, and for a sole trader the customer record is effectively a person. Under the Saudi Personal Data Protection Law, reading those details during a conversation needs a purpose and a lawful basis like any other processing.
In practice that means keeping contact-person fields out of scope unless a question genuinely needs them, identifying a customer before any balance or ageing is disclosed, and keeping the lookup log that shows what was read and why. A salesperson asking for a customer's balance should get it only if their own role would show it. If customers will have their records read during a chat, telling them so in the language they are using belongs in the first design, not in a fix after launch.
What typically changes once Business One is connected
Other ways Business One companies handle this
The most common answer is more seats: a few extra people get a Business One licence, often a limited one, so they can look things up themselves. That helps staff, but not customers or suppliers, and every seat is another login to manage and another person who can see more than the question required.
SAP's web client and mobile sales app give licensed users a lighter way into the same data, and partners build customer portals and add-ons on the Business One SDK. Where one of those already answers a question well, it should keep doing so; the assistant is for the people and the channels those tools do not reach.
Where connections go wrong is breadth. A user that can read every form in the database is hard to authorise and hard to explain; one scoped to the documents behind five common questions is easy to both. The other trap is reporting: a simple monthly total is fine, but analysis across years of documents belongs in Business One's own reports, not in a chat.
And the unhappy path matters. An upgrade weekend, an order number that does not exist, a customer who cannot be matched to a business partner — saying "I could not find that in Business One" and offering a person is what keeps the answers trusted.
Common questions about Business One
It is often more practical than in a large enterprise, because the questions are concentrated and the people answering them are the ones you can least afford to interrupt. The scope is smaller, so the deployment is shorter.
Normal for Business One. Those fields are mapped during deployment. What matters is deciding which of them the assistant should be able to read, which is a business decision rather than a technical one.
Read is the default. Creating a quotation or logging an enquiry can be enabled deliberately, and those actions can require a person to confirm before anything is committed.
No. The assistant signs in as the Business One user you created, with the authorisations you gave it. You hold that user's password and can change it, or withdraw the authorisations, at any time without going through us.
They do not need a Business One login to ask. The assistant reads Business One as its own user, and how SAP's licence terms treat that user, and people reaching Business One data through another application, is worth settling with your partner before go-live.
While the Service Layer or the database is down, the assistant says it cannot reach Business One and offers a person. Afterwards it is worth re-checking the scoped lookups, because add-ons and user-defined fields are where upgrades tend to change things.
Connect it to your own systems
A working assistant against your own records, in both languages.