Connect Shopify to Lexware Office

Lexware Office was formerly called lexoffice. To connect it with Shopify, there is the app “Lexware Office+”, which creates invoices, credit notes and delivery notes in Lexware Office from orders. For many shops, it is the right choice. A custom integration pays off with B2B customers who need e-invoices, with your own posting rules, or when payouts should be matched cleanly to invoices.

Which data flows from Shopify to Lexware Office

1. Order becomes an invoice in Lexware Office, with the invoice number from Lexware on payment or shipment
2. Refund becomes a credit note referencing the invoice immediately
3. Customer becomes a contact, for private customers a collective contact if you wish with the first invoice
4. Delivery country and customer type become the tax type, including for EU distance sales with every invoice
5. Payout from Shopify Payments becomes a breakdown per invoice and fee per payout
6. Payment status from Lexware is noted on the Shopify order on every change

What already exists for Shopify and Lexware Office

The app “Lexware Office+” by Appify has been in the Shopify App Store since June 2024. According to its listing, it transfers orders to create invoices, credit notes and delivery notes from them, and is prepared for DATEV and OSS. In the higher plan, sales, matching suggestions and transaction fees are added. The app has many good reviews. A Lexware Office account is required.

If you sell to private customers in Germany and payments run through Shopify Payments or PayPal, test this app first.

Where the standard stops

• Payments are read-only in the API

  The Lexware Office Public API provides the payment status of an invoice but does not create payments. An invoice counts as paid only after matching with the bank account or a manual payment in Lexware. A Shopify payout is a lump sum. Without a breakdown per invoice, matching remains manual work.

• E-invoicing for business customers

  From 2027, companies with more than €800,000 in prior-year revenue must send e-invoices, and from 2028 everyone must, with transitional rules. Lexware Office can issue invoices as XRechnung or ZUGFeRD. For that, the contact needs the right details, for public authorities for example the Leitweg-ID (routing ID). Shopify has to capture this data at checkout.

• Two requests per second

  According to the documentation, the Lexware API allows up to two requests per second. During a discount campaign with hundreds of orders per hour, the transfer has to run through a queue, otherwise invoices get lost.

• EU distance sales

  For sales to private customers in other EU countries, the API has its own tax types. Which one applies depends on your setting for the origin or destination principle. The integration has to set this correctly for each order.

How we build the integration

Shopify side: A dedicated app in your shop reads orders, refunds and payouts through the GraphQL Admin API. Webhooks for paid orders and refunds trigger the transfer, and an hourly query picks up missed events. We read company name, VAT ID and Leitweg-ID from order or customer fields.

Lexware side: We write through the Public API at api.lexware.io with an API key that you create in Lexware Office. We create invoices directly finalized, so Lexware generates the number and document. For business customers, we set the e-invoice profile. Through event subscriptions, we learn when the payment status changes. The messages are signed, and we verify the signature.

Operation: A queue keeps to the limit of two requests per second and retries rejected calls with a pause. In the log, each order has its invoice number. If your API key is renewed, we recreate the event subscriptions, because Lexware deletes them in the process.

Process and price range

In the free integration check (30 minutes), we go through customer types, countries and payment methods. You receive a fixed-price offer within 3 working days. A simple connection between two systems starts at €1,900 net, and operation at €149 per month. The path there is described under Process and pricing.

Updated: 10/20/2026