Which types of solution are available?
sevdesk documents Shopify integrations operated by partners, and Lexware also describes a partner integration. Alternatives include specialised multi-destination apps such as zrapp, configurable middleware and custom API projects. The term native app is too vague without naming the actual developer.
A partner app may suit a standard process well. Middleware is more flexible but leaves tax logic, retries and duplicate protection to your team. A specialised app preconfigures these workflows but must still disclose its edge cases and limitations.
| Approach | Operator check | Strength | Test closely |
|---|---|---|---|
| Destination partner app | App Store developer and support | tight focus on one accounting system | refunds, history import, error visibility |
| Specialised Shopify app | product provider and data processing | predefined Shopify workflows | tax boundaries, idempotency, destination differences |
| Middleware | your account plus connectors | custom workflows | retry, duplicates, API changes, tax |
| Custom API | your team or agency | maximum flexibility | operations, monitoring, maintenance and cover |
The ten decisive criteria
A feature list becomes meaningful only when the exact workflow is described. Refund support, for example, may mean a full credit note, an item-level partial credit or only a manual reminder.
- Invoice trigger: paid, created, fulfilled or manual?
- Idempotency: what happens when the same webhook is delivered twice?
- Failure state: is there a transfer log, reason, retry and clear next action?
- Refund/cancellation: test full, partial and repeated cases separately.
- Tax: domestic, mixed rates, discounts, shipping, EU B2C/OSS, EU B2B, exports and § 19.
- VAT ID: format detection only, or qualified VIES validation with evidence?
- E-invoicing: who creates which profile and what recipient data is required?
- Delivery: can the destination API actually send email?
- Historical import: range, progress, duplicate protection and resume behaviour.
- Data governance: operator, hosting, processing agreement, deletion and support path.
Acceptance test before going live
Run the same controlled cases through every candidate and compare the result in Shopify and the accounting system. Do not use a production order whose document flow has already been completed.
- Paid domestic order with shipping, discount and two VAT rates.
- Deliver the same webhook again: no second invoice may be created.
- Check a full refund, a partial refund and a second partial refund separately.
- Cancel both a draft and a finalised invoice.
- Test EU B2C/OSS and EU B2B with documented VAT-ID validation.
- Trigger missing customer data, an invalid token and exclusion tags.
- Limit historical import to a small range and start it again.
- Download an e-invoice and validate its profile or XML.
How should you assess sevdesk, Lexware Office and zrapp?
If your process is fixed on sevdesk, start with the partner solutions documented by sevdesk and run the test list. Apply the same method to the partner integration described by Lexware Office. Provider pages are the source for current features and pricing.
zrapp connects Shopify to either sevdesk or Lexware Office and provides paid-order transfer, a transfer log, metafield writeback, exclusion tags and historical import. Destination differences remain: email delivery is possible through sevdesk but not through the Lexware API currently used. Partial refunds need special review in both destinations.
See connect Shopify to sevdesk and connect Shopify to Lexware Office for the setup details.
Total cost, not only the monthly fee
On the day you decide, compare the current App Store price, required accounting plan, usage limits and trial period. Add setup time, maintenance, incident handling and manual exceptions. A monthly fee alone says little about the process cost.
Record the date, plan and linked source behind the decision. The comparison stays traceable if a provider later changes its price or feature scope.
