Your questions. Our clear answers.

Heini works inside your company's digital back office. He gathers preparatory work that today is scattered across emails, spreadsheets, workarounds and multiple systems. Heini starts at product logic and works upward into operational cases — with an approval-first principle.

Heini supports typical areas such as quote preparation, order and purchase-order preparation, receipt pre-work, scheduling, shipping prep, required fields, content and other back-office cases. Which areas are active depends on your size, your operation and the chosen tier. Every relevant step stays subject to your approval.

Heini prepares, the human decides. Suggestions, drafts and prepared steps are visibly handed to the responsible people in the operation. They can approve, change or reject. There is no silent execution in the background.

Yes. The HeiniBar works as one input line in two worlds: in the shop, where repeat customers order, and in the back office, where Marion and Thomas work. The same style, the same voice — separated roles and view. In the shop, the customer describes what they need, Heini finds, knows contract prices and lead times. In the back office, the bar opens with Cmd+K and queues cases for approval. More on the HeiniBar page .

Instead of stitching together five tools — one layer in which the following work together from day one: product data in one source (PIM, CIM, composite products), a constraint editor in seven views, the Digital Product Passport with a validator before every write, an audit trail with source and rationale, hosting in Germany with a dedicated stack per customer, a tier model with mandatory approval, the x-Bar with voice input, and memory control with visible sources. Add-ons add depth for specific needs — they are not entry. More on the blog: What's in HEINI from day one and on Pricing .

No. HEINI prepares and proposes. You approve. Nothing important — money, dunning, outbound writing — runs without your OK. More on Approval folder .

The decision, the rules and the exception. HEINI sorts the day and shows what is stuck — you steer and approve. More responsibility only with your approval. See Solo and team .

Solo: you steer HEINI in one place — from the day list to the decision. In a team, ops sorts the day; more freedom for HEINI is decided by management. Details on HEINI — the colleague .

Yes. HEINI is an AI. Susi is your point of contact within it. HEINI proposes — you approve. Not tax advice, not collection agency. More under Security .

Yes. Every action lands in the audit-proof log — with timestamp, rationale and your approval. One click exports a clean PDF for tax audit, financial audit or GDPR reviews. Independently double-checked so nothing can be altered afterwards. More on Compliance & audit .

Yes. In HEINI control you toggle per role which tasks a colleague takes on and what they may see. More responsibility only with your approval — if a colleague becomes uncertain, they step themselves back. Details on HEINI control .

Where production is connected, HEINI safeguards 3D printing: material, permission and quality must be proven before printing. If proof is missing, HEINI blocks until you decide. More on 3D print safeguard .

You maintain product data once. HEINI prepares shop, Amazon, Google and further channels — only approved content goes live. No retyping in four systems. More on Commerce & e-commerce .

You reach out via Pricing, application or general request. Susi then guides you through onboarding, clarifies the right size, relevant areas and existing systems. For Basis, Finanzen and Betrieb, the start is designed so that no large up-front project is needed. For larger special cases, onboarding is planned more individually.

Heini currently runs in four sizes: Basis, Finanzen, Betrieb and Enterprise. Which one fits depends on how much preparatory work happens today, how many areas are involved and how deeply Heini should be embedded in your existing flows.

Basis fits smaller teams with a clear entry point. Finanzen fits when more back-office prep work and more day-to-day coordination come into play. Betrieb fits structured flows with more depth — warehouse, logistics or multiple process chains. Enterprise is the path for larger structures, special modules and dedicated requirements.

Four plans: Basis €1,290 (5,000 actions), Finanzen €2,990 (20,000), Betrieb €5,990 (60,000), Enterprise from €12,900 (150,000). All prices net per month. Compare on /en/pricing/ — we clarify the right plan for your volume in the demo.

Every prepared step is secured so it can be retraced later. We call this the Proof Layer. It keeps visible on what basis a suggestion or prepared action came about, and who approved what.

Heini works with the approval-first principle. He suggests, reviews and prepares. Binding steps stay with the responsible people in the operation. That keeps Heini steerable, not a black box in the background.

Heini is built around a controllable and traceable way of working. For deeper questions on hosting, security and dedicated requirements, see the pages Security and Enterprise .

The DPP is not a compliance nightmare — it is mainly a data and proof question. Anyone who uses it as an opportunity to structure product and required-field data cleanly ends up with a structural win, not a forced obligation. Heini prepares the required fields per batch and serial number from your existing sources. More in the DPP blog post .

An action is a process step with effect — for example a prepared quote, a captured order, a checked document or a prepared production hand-off. Everything HEINI does in the background is summarised. Susi questions, onboarding and initial import do not count. Details on Pricing .

The business memory is the shared working state of your company. HEINI connects approved information from documents, emails, notes, projects and approvals so your HEINI colleagues do not work in isolation. Accounting, back office, schedules and compliance know what has already been clarified — even during substitutions or site moves. Availability, scope and role permissions are agreed in the Enterprise or onboarding conversation.

Only the roles you approve. The state is tenant-separated — another company sees nothing from your house. Within your company role permissions decide who sees which areas. Accounting sees the accounting context, the back office sees the back-office context. Sensitive areas stay tied to roles.

The SaaS platform contracting party is Heini Operations UG (haftungsbeschränkt) . HEINI IP GmbH owns the HEINI® trademark and is an Odoo Ready Partner — not your SaaS contracting party. Details in the imprint and trademarks page.

For visits to this marketing website (Umami, Hetzner Falkenstein) there is no third-country transfer in normal operation. For use of the heini.app SaaS platform (especially AI inference) EU-based sub-processors may be used whose parent companies may be in third countries — as listed in the DPA . Your operational data is hosted in Germany, single-tenant.

No. HEINI can work with existing systems. For a new core, you can consider HEINI ERP from October 2026 or the existing Odoo connection.

Each start has an agreed scope. Individual functions, migration, integrations and acceptance are defined for your rollout.

We start with a representative case, check data and connections and plan migration. You review mappings before approval.

Scope, migration and support determine the proposal. Published HEINI tariffs do not promise to cover every ERP project.

This example covers capture, interpretation and decision support. A receipt acknowledgement does not prove a machine action. Physical intervention needs a specifically agreed and accepted control path.

That depends on interfaces, controls and available access. We validate the connection during the pilot rather than promise universal compatibility.

We assess the connection and the order and material data your business needs. An existing ERP can remain the authoritative source.

We agree a baseline, such as clarification time or handover completeness, and compare the same workflow during the pilot.

The GPU server initially covers the agreed model operation. It does not imply a fully local deployment of HEINI. Standard hosting and connected services are identified separately in the operating plan.

That depends on the agreed configuration. Data paths, telemetry, external services and failure behaviour must be explicitly defined and tested. Owning a server alone does not guarantee isolated operation.

The proposal is tailored to your requirements. Model licences, quality, memory and throughput inform the selection. Supported text, image and other GenAI applications are explicitly agreed.

Company: 2 GPUs, €216,500 hardware upfront and HEINI software from €12,900 net monthly equivalent (€154,800 annually in advance) for one legal entity. Company group: 4 GPUs, €517,000 hardware upfront and software from €24,900 net monthly equivalent (€298,800 annually in advance) for up to 5 agreed legal entities. Setup, infrastructure and external services are additional. Indicative hardware prices, net plus applicable VAT. Configuration and delivery scope as agreed in your HEINI offer.

5-year manufacturer warranty. HEINI exclusively distributes this server offer in Germany, Austria and Switzerland. HEINI software is paid annually in advance as a subscription with updates and agreed support, without per-seat pricing. Local model calls incur no external LLM token fees. Remaining external services and the scope of a local platform are agreed separately.

HEINI distributes this server offer exclusively in DACH: Germany, Austria and Switzerland. Delivery, installation and service scope are stated in your individual proposal.