edoc

What the product is

edoc is a suite of document and process software from edoc solutions gmbh in Weilerswist, Germany. Its low-code piece is edoc automate, a workflow platform that business departments use to model and run their own processes. The rest of the suite covers invoices, procurement, order confirmations and contracts.

The reader it fits is an operations, finance or HR team inside a company that already runs an ERP and wants approvals, forms and document handling built around it. The company's site is written in German, and so is its support. This entry covers the edoc.de offer as a whole, with edoc automate as the builder.

What you build and how

The company describes edoc automate as working "wie eine digitale Werkzeugkiste" (like a digital toolbox). It ships built-in basic functions and a user-friendly workflow designer, and the company says individual processes can be digitized in very short order with them. The people it has in mind are what its blog calls "Citizen Developer", technically capable staff in a business department who build software for their own area without going through the IT department. In the blog's words, they can design individual workflows, co-design input masks and define the architecture of the process. The same page says the citizen developer reaches a limit once work moves into deeper technical layers or the definition of interfaces. That is a plain admission about where no-code stops.

The blog lists what customers have built with the platform: complaint management, service handling, sick-leave notification, an employee portal, a customer portal, vacation requests, an IT support ticket system, travel expense claims and visitor management. Those are the typical shapes of a business process application, a request, a check, an approval, a record.

Two examples come from the company's own use. The first is an internal lunch app built with edoc automate, where all employees see the weekly changing menu and place and manage orders. The second is an offer approval workflow. Offers are uploaded and edited centrally. Above a freely definable offer value, approval runs in several stages through the inside sales team or the sales management. The approved offer is then sent by email and filed automatically in the ECM system. That one example shows the mix the platform is built for: a form, a rule on a value, a multi-step approval, an email and a filing step.

On the data and integration side, the company's home page says its software integrates directly into existing ERP systems such as SAP, Microsoft Dynamics ERP and Infor, and "viele weitere Plattformen" (many other platforms). A row of logos names SAP, Microsoft Dynamics 365, Microsoft 365 and Salesforce. The stated idea is that staff keep working in their familiar interfaces while documents, information and process data are available across systems. You pick the operating model: cloud, on-premises or hybrid.

The home page groups the offer by application area. These are incoming invoice processing, procurement workflow, order confirmation, purchase-to-pay, contract management, individual business processes, document management, digital signature and digital personnel file. Each of these maps to a named product. The product menu lists edoc invoice, edoc procurement, edoc order confirmation, edoc automate and edoc contract. It also lists a d.velop family (d.velop documents, d.velop sign, d.velop postbox and d.velop connect for Salesforce), an xSuite family for SAP (xSuite Invoice, Procurement, Order Confirmation and Orders) and managed services.

For a process-automation buyer, the practical reading is this. Standard document processes such as invoices and contracts come as dedicated products, and everything that does not fit those shapes goes to edoc automate. The company's own phrasing for that second group is "Individuelle Business-Prozesse" (individual business processes). The ECM system named in the offer approval example is the document archive the finished workflow writes to.

The pages do not describe the editor in detail. They do not say how the form designer handles data types, whether there is an app store of templates, what the API looks like, or how permissions are modeled. They also do not describe AI features, mobile apps, code export or self-hosting beyond the on-premises option. A buyer should ask for a demo for those answers.

The evidence from the pages

Pricing is not published. The pages show no plan names, no per-user or per-process prices, and no free tier. What they offer is a free, non-binding first conversation that the company asks you to book, in which it discusses your current state and requirements and works out together "ob und wie" (whether and how) its solutions can help.

The company positions itself on experience. It says you benefit from best practices and the experience of "hunderten ECM- und Digitalisierungsprojekten" (hundreds of ECM and digitalization projects). It also names personal contacts, holistic consulting and German-language support among the reasons to choose it. One customer quote appears on the home page, from Andreas Feldberg, Vice President and CFO of Tsubaki Kabelschlepp GmbH: "Mit edoc haben wir bei Digitalisierungsprojekten stets einen kompetenten und zuverlässigen Partner an unserer Seite" (With edoc we've always had a competent, reliable partner at our side in digitalization projects).

The blog post on low-code and no-code is dated December 10, 2025. It sets out three approaches. High-code needs extensive programming skills and gives maximum flexibility and control, at higher cost for developers and maintenance. Low-code offers visual tools and prebuilt modules and requires a basic technical understanding but little programming. The post says low-code reaches its limits with very complex applications and is usually not suited to projects needing very high performance and extreme scalability. No-code needs no programming at all, uses drag-and-drop tools and ready-made templates, and delivers quick results, but you are restricted in individual customization and depend on the platform's features and updates. That reads as a candid account of the trade-offs, written by a vendor of one of the tools.

The post also lists benefits it attributes to the approach: improved agility, cost reduction, faster transformation and a user-centered front end, because the people who define a process know its requirements. It points to an on-demand webinar about speeding up business processes with low-code and no-code technology using edoc automate.

The company's site lists no compliance certifications, no hosting regions, no usage limits, no template counts and no user counts. Those are gaps in what the pages say, not statements that the company lacks them.

Who it suits and who it does not

edoc suits a mid-sized or larger company in the German-speaking market that already runs SAP, Microsoft Dynamics or Infor and wants invoice, procurement, contract and custom approval processes to sit beside that system. The cloud, on-premises and hybrid options matter to teams with strict data-location rules. Business departments that are tired of queueing for IT will recognize the citizen-developer idea, with the company's own caveat that interfaces and deeper technical layers still need technical hands.

It suits a solo founder or a small team much less. There is no published self-serve plan, no free tier and no public template gallery on the pages, so you start with a sales conversation rather than a signup. An agency looking for a client-portal builder, or a developer who wants to export code, will find nothing on the pages that points that way.

The main caveat is information. The company shows its range of products and examples clearly but gives few specifics about the builder itself, so judging how far edoc automate stretches beyond approvals and forms means seeing it demonstrated against your own process.