weclapp vs Xentral

weclapp

The GoBD page states the technical basis for GoBD-compliant working with a procedure documentation, revision-safe filing, immutable documents and complete logging of all processing, and the DATEV pages show bank transaction retrieval with open-item clearing, automated dunning, VAT mapping, e-invoices sent and captured, and DATEV/BMD exports with free tax-advisor access. That is a genuine ledger-and-export story, but we found no public information on several companies in one tenant, OSS or reverse charge, fixed assets or intercompany postings, so I stop short of the higher anchors.

Xentral

The finance pages show a working pre-accounting layer: invoices and credit notes, automated payment matching from PayPal, Stripe, Klarna and Amazon, dunning in the Pro plan, e-invoices sent automatically in ZUGFeRD and XML since 1 January 2025 and read in ZUGFeRD, XRechnung, XML and PDF, GoBD-conformant invoice processing, OSS readiness and a one-click DATEV export with a full export list. But the pages themselves say the ledger side is not there yet — BWA, Saldenliste and UStVA directly out of the system are a long-term goal, direct posting is limited to corrections, and several ledger features are marked as in further development or coming soon, so the books do not close inside the system.

weclapp

The order pages evidence the full chain from quote through order confirmation, goods receipt, picking, shipping, returns and credit notes, with serial and batch numbers, drop shipping, a mobile warehouse app, carrier data transfer, named shop and marketplace connections, and stock valuation per HGB and IFRS feeding the balance sheet. I hold it at this level because we found no public information on multiple named warehouses with storage bins, and recall traceability per batch appears only as branch-level marketing for food and cosmetics firms rather than documented evidence.

Xentral

The goods chain is the strongest part: a documented process from order through payment, picking, shipping, invoice and posting, purchase orders with scanner-based goods receipt that books stock, real-time stock across unlimited warehouses, batch, serial and best-before tracking with FiFo/LiFo, mobile batch picking with location, article and box scanning, DHL/DPD/UPS and shop/marketplace connections, returns with credit notes, order suggestions and EDI, plus stock valuation from purchase prices. What I did not find documented is recall traceability per batch from supplier to customer and attributed, dated warehouse movements — that keeps it off the top level.

weclapp

The production page names bills of materials with tree structure and sub-positions, work plans and production orders, and the project module shows minute-exact time recording billed from logged hours plus budgets, resource planning and Gantt views, with the served models clearly named for services and trade. For my shop this is a working core but not the depth above it: we found no public information on work centres, capacity planning, MRP runs or shop-floor data capture.

Xentral

For manufacturing the pages document bills of materials with production orders consuming stock, external production orders, per-order time tracking on tablets or scanners with material consumption, and post-calculation — and they state the limits openly: not designed for multi-stage manufacturing, detailed capacity planning, fine scheduling or machine connection. Services get projects with subprojects, hours booked and billed from logged time, service reports signed on site and subscription billing; no routings, work centres or MRP runs are documented, which keeps it below the deeper level.

weclapp

There is an open REST API with read and write access plus a standard API, a plugin store, CSV, XML and EDI exchange, connector categories spanning shops, marketplaces, payment and shipping, DATEV and BMD exports, and paid help with migration and shop connection, which is more than a few CSV lists. But this is what I cannot plan a factory integration on: we found no public API reference showing versioning, object coverage, webhooks or sandbox tenants, and the exit path is contractual (30-day transition, 30-day retrieval window, customer-paid egress) rather than a documented full export format.

Xentral

An open API is named, with API access from the Business plan, maximum API rate limits and volume in Scale, a pricing FAQ covering API, Flows and Xentral Connect, and CSV, XML and API bulk import plus a document importer for receipts from the previous system; the marketplace lists 200+ connectors with monthly prices, including DATEV, shops, carriers, payroll via Personio and a free MCP server connecting ChatGPT and Claude to live ERP data. What I could not find is a public, versioned API reference, webhooks, a developer sandbox, or a documented full export of master data, documents and postings when the company leaves — the exact things I need to sign a contract.

weclapp

The onboarding page shows a seven-step introduction, tiered onboarding packages with defined contents, a self-study library, role management with access rights, and named partners with certificate levels, and the terms publish a 99.5 percent availability commitment with support packages and daily backups, plus a cloned demo system for testing. It falls short of the top because the onboarding package prices are on request, no typical duration is stated, and we found no public information on a status page, uptime history or release notes.

Xentral

Go-live is unusually well covered: 8-12 weeks typical with preconfigured processes, named customer cases from 18 days to two months, and a 56+ certified partner network with gold, silver and bronze tiers doing implementation and first-level support; support runs through helpbot, help centre and tickets with an emergency flag, plus Academy and learning paths, no-code customisation in Flows, automatic updates and a Premium SLA named for the Scale plan. But the captured pages show no roles and permissions model, no system-wide change log beyond a per-order history of who did what when, and no published availability figures or status page.

weclapp

The contracting entity is a German GmbH with German law, hosting is stated as Germany-only in certified data centres with AWS Frankfurt named, the security page places the company under Exact Group B.V., subprocessors are listed with addresses under EU standard contractual clauses, an Article 28 data processing agreement template is offered, ISO 27001 is published, and weclappOn gives a private-cloud alternative. I hold it one notch below the top because the infrastructure sits with a US-headquartered provider regardless of the Frankfurt region, and the captured pages give different pictures on whether data goes to an external data centre.

Xentral

The contracting entity is proven German — Xentral ERP Software GmbH, registered at Amtsgericht Augsburg, HRB 23930 — and a data processing agreement is offered in the terms; the privacy policy names AWS, a Seattle-based entity, as provider with the server located in Germany, and US marketing tools such as Google Analytics and the Facebook pixel with IP anonymisation stated. What I could not confirm is the ownership chain or where the ERP's business data itself is hosted — the stated server location refers to the website — and the subprocessors behind the actual service are not listed, so only part of the chain is evidenced.

weclapp

The pricing page publishes per-user monthly figures for three packages (Starter at €39, Dienstleistung at €86, Handel at €163), single licenses from €19 to €68, add-ons from €55, with inclusions listed per plan, implementation and maintenance costs stated as none, and the terms add a 12-month minimum term and VAT-exclusive pricing. What stops me computing a full annual cost: the vendor-recommended onboarding packages are priced only on request, and beyond ten to forty licenses the offer becomes individual.

Xentral

Five editions are public — Launch ab 99 €/Monat, Starter ab 349 €/Monat, Business ab 649 €/Monat, Pro ab 849 €/Monat, Scale on request — each with a feature list, unlimited users at no extra cost and a 14-day trial without credit card, and even marketplace connectors carry monthly prices. But these are starting figures that depend on revenue and shipping volume with no published scaling rule, implementation through partners is unpriced, and minimum term, VAT treatment and what happens to the data on cancellation are not on the captured pages, so the real annual cost is not computable.