Documenting Interfaces: OpenAPI Instead of Tribal Knowledge
Describe shop-ERP interfaces with OpenAPI: fields, error codes, examples and scopes, the description as a contract and the handover package for a switch.
On this page you will find the posts from our blog. The newest posts are at the top.
Each post explains one topic. Below the title there is a short text about it. Click on a post. Then you can read the whole text.
Above the list you see the topics. Click on a topic. Then you only see the posts on this topic.
The posts are on more than one page. Below the list you can choose another page.
Describe shop-ERP interfaces with OpenAPI: fields, error codes, examples and scopes, the description as a contract and the handover package for a switch.
DATEV discontinues its Rechnungsdatenservice 2.0 on 31 Dec 2026. How shops and ERP connectors check whether they are affected and move their document route.
Black Week 2026: prepare the order flow between shop and ERP – measure the backlog, move night jobs, add a queue with alerts, freeze changes, define a fallback.
How internal AI assistants reach the ERP through the Model Context Protocol: business-level tools, per-user permissions, approval before writes, audit log.
What does connecting an ERP to your online shop cost? Six cost drivers, recurring items, 2027 deadlines and a budget frame per integration type for planning.
Shop or ERP: which system issues the invoice and assigns the number? A decision matrix for partial delivery, cancellations, marketplaces and e-invoicing.
Withdrawal function under Section 356a BGB: how the click becomes a record that blocks order lines in the ERP, proves the deadline and triggers the refund.
The repair rules have applied since 31 July 2026 to eleven product groups. How spare parts, guide prices and repair orders flow from the ERP into shop and portal.
Energy label and product information sheet in the online store: which fields belong in the item master, how the EPREL number reaches every channel and how cut-over works.