Deployed · Dreamy.cz

ERP module on top of ABRA Gen

A custom application instead of spreadsheets and an unused off-the-shelf CRM, connected to ABRA via the Web API. ABRA remains the book of record; the application reads from it and can create documents in it. We connect an e-shop, a B2B portal or EDI the same way.

Free audit · 30 minutes How we built it

ERP

ABRA Gen · book of record, warehouses, documents

reads · creates documents

Your application · one login

Stores
Logistics
Sales
Warehouse

Who it is for

The ERP remains the book of record. People in operations need a workspace.

For companies with 10 to 100 people that have an ERP, an e-shop and stores or sales reps in the field. Often also their own delivery service, complaints or goods on order.

Spreadsheets on a shared drive

The transport plan, stock, attendance or the customer database live in spreadsheets, and nobody knows which version is current.

Retyping data between systems

Data gets copied between the ERP, the e-shop and spreadsheets. The bridges between systems sometimes fail quietly and nobody notices.

A CRM nobody uses

The off-the-shelf CRM is paid for, but the sales team does not work in it and its data only mirrors the ERP.

Management cannot see what is going on

Who promised what to a customer, where goods or a deposit are stuck and when a delivery arrives – all of it gets found out by phone.

You do not know whether you have the Web API

The e-shop supplier wants an API, and nobody knows whether it is in your ABRA plan and license, or who will enable it on the server.

Scripts left by someone who has left

Imports and scripts in ABRA were written by a colleague who is no longer with the company. After an upgrade an import stopped working and nobody knows why.

What the application does with ABRA

Connected via the ABRA Gen Web API. Nothing is retyped by hand, and documents are created directly in ABRA, not in a parallel record.

Reads from ABRA

Incoming orders automatically, including address, contact and carrier. A repeated import does not create duplicates.
Deposits, orders from manufacturers and goods receipts.
Warehouses, stock cards, stock levels and sales from invoices.
Customer purchases into the client card in the CRM.
Invoices, credit notes and advance invoices as the basis for commissions.

Can create in ABRA

Orders with a preview of the series, customer, warehouses and prices against the price list.
Advance invoices for orders.
Delivery notes and invoices with deposits deducted, following the same procedure as the back office.
Cash receipts for cash payments and PDFs from ABRA print forms.

Built and deployed. Live writing is switched on after the pilot and approval, and ABRA first validates every document in a dry run.

Modules in one application

One database, one login, shared clients and products. Each module replaces a specific spreadsheet or manual step and is deployed separately.

Logistics and deliveries

Transport requests, a weekly plan, delivery runs with routes and arrival times, PPL labels in bulk and QR navigation for drivers.

Sales and CRM

Clients, communication, tasks, calendar, deals and PDF quotes that turn into an order with one click.

In-store sales

Customer, goods from ABRA with price and available units, then “takes it now” or an order with a deposit. On one screen.

Waiting for goods

Deposits, orders from manufacturers and goods receipts from ABRA. The application watches deadlines and shows what is stuck where.

Complaints

Statutory deadlines, PDF documents, defect statistics by supplier and a complaint created from a forwarded e-mail.

Store stock

Ideal stock levels against stock in ABRA: how long it will last, what to bring from the central warehouse and what to order and when.

Store operations

Plan and turnover, attendance, cash check against ABRA, commission data and messages instead of spreadsheets.

AI connection

Claude works with the data with the same permissions as a person, and every entry it makes can be traced in the history.

Integration with other systems

ABRA Gen integration: e-shop, B2B portal, EDI and CRM

Besides a custom application, we connect ABRA Gen to the systems you already work with. Via the Web API, imports or EDI, depending on what makes sense for you.

E-shop integration with ABRA Gen

Orders from the e-shop into ABRA, stock and prices back to the e-shop. Custom-built where a ready-made connector does not cover your warehouses, sets or price lists.

B2B portal for customers

Your customer sees their prices, availability and document history from ABRA and orders on their own. The order is created straight in ABRA, with no retyping from e-mail.

EDI with retail chains

EDI for ABRA Gen via GRiT or EDITEL: orders, despatch advice and invoices. Plus monitoring, so someone knows right away about a message that did not go through.

CRM and invoices

A deal in the CRM becomes an invoice in ABRA, and the payment status goes back to the CRM. We connect Raynet via its API, other CRMs depending on the interface they have.

Reporting and Power BI

ABRA data in Power BI or Looker Studio, kept up to date. Reports without manual exports to Excel.

Taking over scripts and imports

Looking for an ABRA Gen developer because the author of your scripts and imports has left? We list what runs on ABRA, document it and test it after an upgrade.

ABRA Gen Web API and other routes: what they can do

What the ABRA Gen API and the other interfaces can do according to the vendor’s documentation as of 28 October 2026 (help versions 25.0 to 26.2). What exactly is possible for you depends on your plan, version and licenses. We go through that in the audit.

Area	What is possible
Web API (REST)	A REST interface on top of ABRA business objects: reading, creating, updating and deleting records. Data in JSON, documentation in OpenAPI 3.0. According to the vendor, the API is available from the Standard plan.
Login and permissions	The integration logs in with a username and password on every request. The Web API server can handle an encrypted connection (HTTPS) on its own. Since version 23.1 the Web API respects user permissions to functions, so the integration can only do what you allow it to.
Changes and synchronization	Changed records can be read with a query using a filter and paging. A definable export can run on its own after a document is saved, and AutoServer takes care of scheduled tasks.
Imports, exports and ISDOC	Definable imports from TXT, CSV, XML and XLS/XLSX with a duplicate check across the whole database. Exports in XML and text. ISDOC/ISDOCX, including receiving e-invoices from e-mail.
EDI	EDI with retail chains via GRiT or EDITEL CZ: orders (ORDERS), despatch advice (DESADV) and invoices (INVOIC).
E-shop and ready-made connectors	The vendor lists four e-shop variants on top of ABRA Gen. Ready-made connectors: Dativery (including Shoptet, Upgates, WooCommerce, Shopify) and Shopsync via Base.com.
Older integrations and scripts	Older web services (SOAP), integration with Windows programs (OLE) and scripts that ABRA runs, for example, when a document is saved. AutoServer runs scheduled tasks even without a logged-in user.
ABRA Aiva	The new ABRA Aiva line is based on ABRA Gen. We build the integration so it can later be switched over to Aiva.

What you can rely on with an ABRA Gen integration

We build new integrations on the Web API. Older integrations and scripts you already have, we first list and only then decide what to switch over.

We never expose the ABRA server directly to the internet. Every transfer can be traced, and if the connection drops, it runs later.
The integration transfers only changes and does not put needless load on the ABRA server.
Each integration has its own API user with minimal permissions.
We test writes on demo data or a copy of the database, as the vendor recommends. On live data the integration only reads at first.
We write to ABRA only via the Web API or imports, never directly to the database.
The integration can be switched over later, for example to Aiva.

When you do not need us

We do not sell ABRA licenses or ready-made connectors. When a ready-made solution is enough, we will tell you.

You only want to connect a standard e-shop or Base.com: There are ready-made connectors with a price list for that, such as Dativery or Shopsync via Base.com. If they cover your rules, we will recommend them.
An e-shop directly from ABRA is enough for you: The vendor offers several e-shop variants on top of ABRA Gen, including an integrated one. A custom build only makes sense with your own rules, a B2B portal or several connected systems.
A retail chain wants EDI and nothing more: There is a ready-made ORiON EDI connector for ABRA Gen, and EDI via GRiT or EDITEL can also be set up by an ABRA consultant. A custom solution only makes sense once EDI ties into the warehouse, dispatch or other systems.
You only need reports from ABRA: Try the built-in ABRA BI first – it supports your own indicators and data from other sources. We build Power BI reporting only when that is not enough.

Traceability and accountability

You know who did what and when.

Data is not collected as a by-product, but in a structured way, with an author and a time for every action. No more lost information, an overview in real time – and a clean basis for reports, BI and AI.

Staff performance, attendance and cash are visible only to those with permission.

Every record has a full history: who, when and what changed from what to what.
Customer communication: who spoke to whom, about which products and with what result.
Logistics: who entered it, who is handling it and who delivered it, when it was dispatched and delivered.
Documents in the ERP: who created which document and when.
Entries made via AI are marked “via Claude” in the history.
Real-time notifications about what someone else has done.

Built fast, module by module and in your brand

3 weeks

from the first line of code to the whole system

3 days

a custom CRM including data migration

1 afternoon

replacing the store spreadsheets

2 days

switching to the client’s brand

In your brand

Logo, colors and typeface are in one place. The application and PDF documents – quotes, complaint documents – carry the company’s brand from day one.

Feedback within days

We work in feedback from operations continuously: ten points from the owner in four days. Behind that are hundreds of automated tests and deployments that roll back to the previous version on their own if there is an error.

How we proceed

01
List of spreadsheets and processes

We go through what lives in spreadsheets today and who works with what. We only take the structure, not personal data.
02
Platform and one module

We start with the module that hurts the most. We add more only once the first one has taken hold.
03
Read-only verification

We verify the ABRA connection on live data without a single write. You see right away what is missing in the data.
04
Writing after the pilot

We switch on writing to ABRA only after the pilot and your approval, globally and for each user separately.

Reference · Dreamy.cz

DreamyApp for Dreamy.cz

A seller of premium mattresses and furniture with an e-shop, four stores, B2B sales and its own delivery service. One application with one login brings together logistics, CRM, in-store sales, waiting for goods, complaints, warehouse and store operations. It replaces the Excel transport plan, the off-the-shelf CRM and more than ten types of spreadsheets that the stores kept on a shared drive.

Connected to ABRA Gen, Shoptet and PPL
More than 30 screens
Almost 60 tools for AI
In the client’s brand

Frequently asked questions

Do we have to leave ABRA?

No. ABRA remains the company’s book of record, and the application is a workspace that reads from it and creates documents in it. We do not build a separate accounting warehouse outside the ERP.

What do we need on the ABRA side?

The ABRA Gen Web API. According to the vendor it is available from the Standard plan, is licensed by the number of users with access and runs only on Windows. The integration user must have API login enabled in ABRA, and for access from outside we recommend an encrypted connection (HTTPS), which the Web API server can handle on its own. We create separate users with minimal permissions for reading and for writing (each counts towards the API license) and allow only the server the application runs from. We go through what you already have in the audit.

Does ABRA Gen support webhooks?

The vendor does not document a separate HTTP webhook mechanism. Changes are therefore transferred at regular intervals. ABRA Gen also supports an export after a document is saved and scheduled tasks in AutoServer. A repeated transfer does not create duplicates.

Will the application write anything to ABRA without our knowledge?

No. The default is read-only. Live writing is switched on globally and for each user separately, and ABRA first validates every document in a dry run. A repeated import does not create duplicates.

Does it work with our ERP?

In live operation the application runs on top of ABRA Gen and Shoptet. We connect POHODA, ABRA Flexi and Money S3 the same way: read-only first, verification on live data, then writing.

What if the developer disappears?

We build on widely used standard technologies, with documentation, hundreds of automated tests and deployment manuals. The data is in one place and backed up.

What about GDPR?

Anonymization after retention periods while keeping statistics, export and erasure of personal data with one button, and consents per channel. The AI connection is switched off by default and is only switched on after approval.

Are you an ABRA partner?

No, we build integrations. We do not sell licenses. You arrange ABRA Gen licenses and Web API user licenses with ABRA or your ABRA supplier; we build the application and the integration.

How much does it cost?

It depends on the systems and the scope. We do not publish a price list, because no two companies are the same. You get the price and timeline after the audit, in advance and in writing.