Something happens, in SAP or around it.
- Starts from anything: 303 SAP events, changes on any SAP object, emails, forms, schedules, webhooks and IDocs.
- Visual editor with conditions, steps in parallel, Draft and Live.
Connect SAP with email, AI, documents, approvals and printing. Replace manual work with automated processes, without building custom SAP developments.

An order is created in SAP, a supplier replies, someone fills in a form. Oranid decides what comes next and gets the job done, in SAP and around it.
Start with one useful workflow. Build from there.
Your SAP
ECC or S/4HANA, cloud or on-premise
Automation running
Every run kept, every SAP call recorded
Add your SAP system and the apps your process needs. Oranid finds its release and the objects it offers.
Arrange the steps on the canvas, or describe them to the AI. Each SAP step is a method from the SDK.
Publish it. Every run is kept with its history; if SAP is down, the run waits and carries on.
Three demos: a workflow built by hand, one built with AI, and SAP answering a question in plain words.
SAP is where they start. The value is everything after: the PDF, the email from your own address, the alert in Teams, the signature, the AI that reads the reply.
Suppliers answer the purchase order by email, as they always have. AI reads each reply, its PDF included, and checks dates and quantities against SAP. A match is saved as the confirmation; a change goes to the buyer and to planning in Slack, and the supplier gets the answer.
Outside SAPSupplier emailsAI reading PDFsSlackGoogle Sheets
An operator scans the QR code on the machine and reports the breakdown with a photo. AI sets the priority, the notification is created in SAP, maintenance is alerted in Teams and the job card prints in the workshop. When the order is done, the operator is told the machine is back.
Outside SAPForm on the phoneAIMicrosoft TeamsWorkshop printerEmail
A new sales order sends its contract for electronic signature. Signed, the delivery block comes off, the customer gets the signed copy and it is filed in Notion. Declined, the sales rep is told the same minute.
Outside SAPElectronic signatureEmail to the customerNotion
A supplier fills in a form, no account needed. Its VAT number is checked online, AI flags anything missing and purchasing approves. The business partner is created in SAP, the code of conduct is signed and the welcome email goes out.
Outside SAPForm for outsidersVAT check APIAISignatureEmail
A request from the website becomes a quotation in SAP within minutes. AI reads what the customer wants, the quote PDF is checked by sales and sent from your address. A week later, if it is still open, the customer is followed up.
Outside SAPWebsiteAIPDF quoteEmail follow-up
When goods leave, the carrier is booked through its API and the tracking number written back to SAP. The customer gets the tracking link, sales is told in Slack, and two days later the customer is asked how the delivery went.
Outside SAPCarrier APIEmail to the customerSlackCustomer feedback form
A complaint arrives by email. AI sorts it and drafts the reply, a quality notification is opened in SAP, the customer is answered and quality is told in Slack. When SAP closes the notification, the customer gets the outcome.
Outside SAPMailboxAIEmail to the customerSlack
Every weekday at 7:00, the materials under safety stock are listed from SAP. If there are any, AI writes what matters most, and the planners get the report by email and in Slack, and the shortage board in Google Sheets is updated, before the first meeting.
Outside SAPScheduleAIPDF reportEmailSlackGoogle Sheets
Oranid ships with an SDK of SAP's own standard APIs, imported from SAP's API files and kept the way SAP wrote them. Your team picks what to do; nobody writes an integration first.
import { get } from 'sap.PURCHASE_ORDER';
import { list } from 'sap.PURCHASE_ORDER_ITEM';
import { get as supplier } from 'sap.SUPPLIER';
// One step in a workflow: an order, its lines, its supplier.
export default async function run({ order }: { order: string }) {
const po = await get({ PurchaseOrder: order });
const lines = await list({ filter: { PurchaseOrder: order } });
const s = await supplier({ Supplier: po.Supplier });
return { supplier: s.SupplierName, lines: lines.length };
}Your SAP stays where it is, and each company's data stays its own.
The team behind Oranid comes from SAP projects. We help you start, build and run, so your first process goes live quickly and the next ones follow.
Consultants who have run SAP projects and know how purchasing, production and finance really work. We speak your key users' language, and your IT's.
We pick one process with you, connect your SAP and have it running in a few weeks.
Workflows, documents and connections, made by people who know both Oranid and SAP.
Support from SAP people, and new processes as your business grows.
No. Oranid uses SAP's standard APIs, its business events and the IDocs it sends. For an SAP at your site, a small agent runs on your network; nothing goes into SAP itself.
SAP ECC and SAP S/4HANA: S/4HANA Cloud, public and private editions, and S/4HANA on-premise. The SDK's ready-made methods are S/4HANA's standard APIs; on ECC, Oranid receives the IDocs SAP sends, and calling BAPIs and sending IDocs are in pilot: we check them on your system first. Oranid reads your release when you test the connection.
Yes. After the demo, we can run a short pilot on one of your processes, on your SAP, with your team. We agree its scope and length together.
Oranid is built for ERPs, and SAP is the first. A workflow also reaches email, documents, printers, signatures, AI and any API or MCP tool.
No. Workflows are built in a visual editor or by describing them to the AI. A code step is there when a team wants one.
Encrypted with your company's own key, and in your own database and region if you need it.
We'll show you how it runs in Oranid, in a 30-minute call.
Book a demo