Integrations
ERP and email integrations for quote and order automation
The whole list, with the connection method and the honest status of each one. If a system is not built yet, this page says so — you will find out during the pilot anyway, and it is cheaper to find out now.
Sample data
What flows each way.
Your ERP stays the source of truth. Ettore reads what it needs to draft the work and writes back only what a person approved.
- 01
Catalog — read
Products are mirrored and indexed so a free-text description or another brand’s code can be matched. No second catalog to maintain.
- 02
Customers and price lists — read
Each draft carries the price that customer actually pays. Price lists are refreshed nightly, with a manual refresh for mid-day changes.
- 03
Stock — read, live
Availability is read from the ERP when the draft is built, not from a copy.
- 04
Mailboxes — read
Outlook or Gmail. Ettore reads incoming requests; replies are drafted for a person to send.
- 05
Quotes and orders — written, after approval
Drafts are written to the ERP only once a person approves them. Ettore never confirms a sales order on its own.
The connections
Two things a catalog usually hides: how the connection is actually made, and whether it exists. Both are in the table.
Odoo
LiveERP: catalog, customers, pricelists, and quote write-back
Odoo’s standard XML-RPC external API. No plugin to install in your instance.
Outlook
LiveThe shared inbox where customer requests arrive
Read-only mailbox access. Ettore does not send from your account unless you configure that.
Gmail
LiveThe shared inbox where customer requests arrive
Read-only mailbox access, same terms as Outlook.
SAP Business One
On requestERP
On request: we build the connector for your SAP Business One setup.
Microsoft Dynamics
On requestERP
On request: we build the connector for your Dynamics setup.
Something else
On requestThe ERP or system you actually run
Tell us what it is. The answer depends on what its API allows, and we would rather look at it than guess.
What a connection actually involves
Three things, in this order. The slow part is almost always getting the ERP credentials approved internally, not the technical work.
- 01
Read access to the inbox
The shared mailbox that receives requests. Ettore starts watching it and classifying what arrives.
- 02
Read access to the ERP
Products, customers and pricelists. Ettore indexes the catalog so it can resolve a written request to a real SKU.
- 03
Write-back, once you trust it
Approved quotes are written into the ERP as records. This step is switched on when your team is satisfied with the drafts, not on day one.
What your IT team will ask
Answered architecturally, because that is what survives a security review. Anything specific to your setup we answer directly rather than on a marketing page.
Your ERP stays the source of truth
Ettore mirrors and indexes your catalog so it can match a request. It never becomes the system of record for a product, a customer or a price — there is no second copy to reconcile.
The mailbox connection is read-only
It reads the inbox that receives requests. Sending from your account is off unless you deliberately turn it on.
Only approved work is written back
Nothing reaches your ERP on the strength of a match alone. A person approves it first.
One customer’s data is never visible to another
Isolation between customers is structural, not a configuration flag someone could get wrong.
No new infrastructure
Connect a mailbox, connect the ERP. There is no migration, no warehouse to stand up, and nothing for your customers to change.
Anything beyond this, we answer directly
Data processing agreements, hosting questions, a security questionnaire — send them to us. We would rather answer them properly than print badges here.
Integration questions we get asked
Our ERP is not on the list. Is that a no?
No. It is a question about what your ERP’s API allows, and we would rather look at it than guess from the name. Tell us what you run.
How long does connecting take?
The technical connection is short. What sets the calendar is getting ERP credentials approved on your side, which is usually the longest step of the whole pilot.
Do you need write access to our ERP from day one?
No. Read access is enough to start drafting. Write-back is switched on later, when your team is satisfied with what the drafts look like.
Can we connect more than one mailbox?
Yes. Most start with one and add the rest afterwards — it is configuration, not a second project.
What happens to a request Ettore cannot resolve?
It goes to a person with the unresolved lines marked. It is never quietly guessed, whatever mode you run in.
What if our catalog data is messy?
That is the normal case, and it is the problem rather than an obstacle to it. Ettore matches free-text requests against the catalog you actually have. Where it cannot resolve a line, it says so instead of guessing.
Can it read our customer-specific pricing?
Yes. Customer pricelists are part of what it reads, so the draft quote carries that customer’s real prices rather than a list price someone then has to correct.
Tell us what you run.
Bring the system names and a real request from your inbox. That is enough for us to say what connects today and what would have to be built.