The problem. A Polish-German cross-border seller ran Allegro through one connector, invoicing through a second tool, and reconciliation through a third. Plus Allegro's own numbers, which did not automatically agree with any of them. Every filing deadline meant checking that four separate systems told the same story. Then KSeF, Poland's mandatory e-invoicing, moved the deadline closer and raised the cost of getting it wrong.
On top of that, the same seller had to report packaging and battery data under EU Extended Producer Responsibility (EPR) law — separate registers, separate deadlines, nothing to do with tax. That meant answering things like: how many packages did we ship this quarter? How much of each packaging material — cardboard, plastic, other — did that add up to? How many units of each battery type?
The four-tool stack, before
The pre-migration stack:
- Allegro connector: pulled orders from Allegro into a local shop system.
- Invoicing tool: separate from the shop, took orders in CSV, produced invoices.
- Reconciliation spreadsheet: pulled from the shop, the invoicing tool, and Allegro's own reports, matched them by hand.
- Allegro admin panel: the fourth source of truth, used when the other three disagreed.
Every monthly VAT return meant pulling numbers from four places and reconciling them in Excel. Every KSeF-related deadline meant the same but tighter. Every EPR quarterly meant rebuilding packaging and battery numbers from scratch from product data that lived in two places.
The fix
Vedron's team connected every one of those tools into one system — for free, as part of onboarding, before asking for a signature. KSeF, XRechnung and FatturaPA are now generated correctly the first time, not reconciled after the fact.
For EPR specifically, Vedron consolidates order, product and packaging data from every channel into one consistent dataset and turns it into the breakdown regulators ask for: total package counts, packaging material weights by type (derived from the packaging specs on each product), and battery unit counts by type. Ready for each country's register, not a spreadsheet rebuilt from scratch every quarter. Work that used to take days of manual chasing now takes an afternoon of review.
The two-week migration
What actually happened:
- Week 1, Monday: Kick-off call. Vedron's team pulled an export of products, orders and customers from the old stack. Allegro API credentials provisioned.
- Week 1, Tuesday-Thursday: Catalog imported. Allegro connector configured. KSeF submission credentials registered.
- Week 1, Friday: First parallel day. Vedron ran alongside the old stack; results compared for a day of orders.
- Week 2, Monday-Tuesday: XRechnung configured for the two existing German public-sector customers.
- Week 2, Wednesday: EPR packaging data configured per product. First quarterly numbers generated and compared against the seller's existing spreadsheet.
- Week 2, Thursday: Final parallel day. Zero discrepancies.
- Week 2, Friday: Old stack decommissioned.
Two weeks total. No downtime. One parallel-running day on each end to sanity-check.
What changed, in numbers
- Monthly reconciliation time: 2-3 days → under 2 hours.
- EPR quarterly reporting: 2-3 days of spreadsheet rebuilding → one afternoon of review.
- KSeF submissions: previously manual (XML built per invoice, high error rate) → automatic from order data, zero schema errors in the first three months live.
- Tools paid for: four separate SaaS subscriptions → one.
"KSeF and all the EU compliance rules we couldn't sleep over — solved. Vedron's team connected our marketplace, invoicing and reconciliation tools at no cost, and now the numbers from every marketplace flow into one place automatically." — Vedron customer, Polish-German cross-border seller.
Frequently asked questions
How long did the migration take?
Two weeks from kick-off to live on Vedron, including data migration, connector setup for Allegro, invoicing configuration for KSeF and XRechnung, and the first EPR reporting cycle. The seller continued operating on their old stack during the transition.
How much did the migration cost?
Zero. Vedron's team ran the integration setup as part of onboarding, before the seller committed to a long-term contract. That is the standard offer for beta clients: custom integration setup is free for the first two months.
Which marketplaces does this seller use?
Allegro (Poland), the direct storefront, and a smaller presence on Amazon.de. The Allegro integration was the complex piece — Polish VAT, KSeF, Polish-specific invoicing format.
What EPR categories are covered?
Packaging (cardboard, plastic, other materials by weight) and batteries (by unit count per battery type). Both are reported into the respective national registers (Verpackungsregister LUCID in Germany, BDO in Poland) on quarterly deadlines.
How does the EPR number generation work?
Vedron consolidates order, product and packaging data from every channel into a single dataset. For each quarter, the system calculates total package counts, packaging material weights by type (derived from product packaging specs), and battery unit counts by type. The output is formatted for each country's register.
What was the biggest time-saving?
The seller estimates 2-3 days per month of manual reconciliation work eliminated. The EPR quarterly reporting was the single biggest win — previously 2-3 days of spreadsheet rebuilding per cycle, now an afternoon of review.
Talk to us about your setup
Running more than one tool just to stay compliant, or piecing together packaging and battery numbers by hand every quarter? Book a free integration call and we will walk through what the move looks like for your specific stack.
