Where data flows between systems, technical and legal requirements meet. This category sets out what to consider in integration projects: data processing agreements with providers and hosts, storage locations and third-country transfers, retention and deletion periods for records, electronic invoice formats and their mandatory fields, evidence requirements in cross-border trade and documentation requirements for audits. Added to this are accessibility and security rules that increasingly affect connected systems too. We describe which documents should be produced during a project and how requirements can be written into specifications early. The articles do not replace individual legal advice, but they prepare those discussions. We also show which entries a record of processing activities should contain when data moves regularly between several systems.
On this page you will find all posts on the topic “Law & compliance”. The newest posts are at the top.
Below each title there is a short text about it. Click on a post. Then you can read the whole text.
Above the list you also see the other topics. At the bottom, a link takes you back to all posts.
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.
Ingredients, allergens and nutrition come from the item master, shelf life and lot number from the batch: how both mandatory data sets reach the shop.
The economic operator as a master data object: move manufacturer, responsible person and product identifiers from the ERP into every distance offer.
Retention periods, deletion classes and one deletion path reaching shop, ERP and accounting at once: what applies, what is deleted and what gets restricted.
On 27 September 2026 provisional importing without authorisation runs out. Which import data the ERP has to carry, and how the 50-tonne total adds up.
From 30 December 2026 every consignment needs a due diligence statement. Which fields the ERP has to carry and how the reference number reaches customs.
Since 1 July 2026 the 150-euro duty relief is gone. Commodity code, origin and net weight from the ERP through middleware into shop and customs declaration.
From 12 August 2026 the EU Packaging Regulation applies directly. How packaging master data, volume logic and reporting emerge from ERP and shop data.
The GoBD require process documentation for every bookkeeping-relevant IT system. How to document the document path of your ERP shop interfaces properly.
The Data Act's switching duties have applied to existing contracts since September 2025. What export APIs, open formats and the 30-day window mean.
Mirror VAT, reverse charge under Section 13b and VAT-ID checks via VIES and BZSt from SAP, DATEV or Dynamics, live into the B2B checkout and onto the invoice.
E-invoice mandate 2027 for B2B merchants above 800,000 euro: generate ZUGFeRD and XRechnung from shop order data and hand them to DATEV, GoBD-compliant.
Digital Product Passport from 2027: aggregate material, repair and origin data per ESPR from ERP and PIM and provide it DPP-compliant via QR code and API.