Menu

Blog — Vedron

A Polish-German cross-border seller running on Allegro, Shopify and Amazon Germany consolidated three operational tools (an Allegro connector, an invoicing SaaS, a reconciliation spreadsheet) and one compliance tool (EPR packaging and battery reporting via a separate agency) into Vedron. The move eliminated 11 hours of weekly cross-tool work and brought EPR reporting into the same system that holds the orders.

The setup before Vedron

Four tools, each doing a slice:

Weekly workload across the four tools (owner + part-time assistant): 11 hours. Monthly VAT reconciliation: 6 hours. Quarterly EPR submission: 4 hours of data pulling.

What moved to Vedron

Catalog and orders: one product record per SKU, Allegro listings and Shopify listings pushed and maintained from the same master. Orders from both channels land in the Vedron order inbox. (Amazon Germany was added in month 3.)

Invoicing: XRechnung for the DE B2B flows, KSeF-ready for the PL B2B flows, standard PDF invoice for B2C. VAT split per OSS registration, with the German and Polish lines tagged for the right return.

Bank reconciliation: the bank feed (imported and mapped the excel files automatically for the German account and the Polish account) runs into Vedron. Matching to invoices is automatic monthly by vendor and tax rules.

EPR reporting: product weights and packaging materials are stored on the SKU record (box weight, filler weight, label material, instructions-leaflet weight). Battery-containing SKUs carry the battery type and weight. Vedron produces the EPR submission file in the format each agency expects: VerpackG for Germany (LUCID identification number), BDO for Poland (battery and packaging registers).

Results after 90 days

Measured by the owner, not us:

Owner’s words: “The thing I didn’t expect was EPR. I was treating it as its own problem for years. Having the packaging weights on the SKU record and the agency file generate from the orders made it a non-event.”

The EPR specifics that most sellers get wrong

VerpackG (Germany) requires every seller shipping packaged goods to B2C in Germany to register with LUCID (the official register) and report packaging placed on the market by material (paper, glass, plastic, lightweight metal, heavy metal, composite). The report is quarterly in volume and annual in detail.

BDO (Poland) requires registration for battery-containing products and for packaging. The report is annual in detail.

In both cases, the data the agency wants is: SKUs sold, units sold, packaging weight per SKU by material, battery weight per SKU. Vedron attaches this data to the SKU record once and generates the agency file from the sales data per the submission period.

What did not move

The Steuerberater (tax advisor) still runs on DATEV. Vedron exports the posted invoices to DATEV, which the Steuerberater receives in the format they already use.

FAQ

How long did the move from four tools to Vedron take?

6 weeks of setup, mostly supplier catalog mapping and configuring the Allegro parameters per category. The bank reconciliation and EPR data entry took 2 weeks of parallel running before going fully on Vedron.

Did the owner have to re-register with LUCID or BDO?

No. Vedron produces the submission file in the format each register expects; the registrations stay as they were. The seller continues to submit through the same login.

What happened with the Allegro listings during the move?

Vedron matched existing Allegro listings to the imported catalog by EAN and SKU. 94 percent matched automatically; the remaining 6 percent were manually mapped. No Allegro listing was recreated or lost.

Was the Steuerberater involved in the move?

Yes. The export format for DATEV was validated with the Steuerberater before go-live. The monthly DATEV handoff continues as before, just from Vedron instead of from the invoicing SaaS.

Did the move break any marketplace rankings?

No ranking disruption on Allegro or Amazon. Stock sync and tracking push-back were tested in parallel for 2 weeks before cutover, so marketplace SLAs stayed clean through the move.

All posts

Case study: 4 tools to 1 for a PL-DE seller, EPR included

July 29, 20264 min read
Case study: 4 tools to 1 for a PL-DE seller, EPR included

A Polish-German cross-border seller running on Allegro, Shopify and Amazon Germany consolidated three operational tools (an Allegro connector, an invoicing SaaS, a reconciliation spreadsheet) and one compliance tool (EPR packaging and battery reporting via a separate agency) into Vedron. The move eliminated 11 hours of weekly cross-tool work and brought EPR reporting into the same system that holds the orders.

The setup before Vedron

Four tools, each doing a slice:

  • Allegro connector: listings and order ingestion from Allegro. Did not handle invoicing or stock on other channels.

  • Shopify Admin: storefront on Shopify.

  • Invoicing SaaS: generated invoices from a flat-file export of Shopify and Allegro orders. VAT split was manual by jurisdiction.

  • Bank reconciliation spreadsheet: an Excel file maintained by the owner’s wife, matching bank transactions to invoices. The reconciliation was 2 to 3 weeks behind by the end of each month.

  • EPR agency: quarterly submission of packaging weights by material and battery quantities. Data pulled by hand from the invoicing SaaS.

Weekly workload across the four tools (owner + part-time assistant): 11 hours. Monthly VAT reconciliation: 6 hours. Quarterly EPR submission: 4 hours of data pulling.

What moved to Vedron

Catalog and orders: one product record per SKU, Allegro listings and Shopify listings pushed and maintained from the same master. Orders from both channels land in the Vedron order inbox. (Amazon Germany was added in month 3.)

Invoicing: XRechnung for the DE B2B flows, KSeF-ready for the PL B2B flows, standard PDF invoice for B2C. VAT split per OSS registration, with the German and Polish lines tagged for the right return.

Bank reconciliation: the bank feed (imported and mapped the excel files automatically for the German account and the Polish account) runs into Vedron. Matching to invoices is automatic monthly by vendor and tax rules.

EPR reporting: product weights and packaging materials are stored on the SKU record (box weight, filler weight, label material, instructions-leaflet weight). Battery-containing SKUs carry the battery type and weight. Vedron produces the EPR submission file in the format each agency expects: VerpackG for Germany (LUCID identification number), BDO for Poland (battery and packaging registers).

Results after 90 days

Measured by the owner, not us:

  • Weekly cross-tool work dropped from 11 hours to 2 hours (bank reconciliation review, exceptions)

  • Monthly VAT reconciliation dropped from 6 hours to 1 hour (the automated split, reviewed)

  • Quarterly EPR submission dropped from 4 hours of data pulling to a 30-minute review of the auto-generated file

  • Days from month-end to monthly financials ready: 18 days before Vedron, 4 days after

  • One tool and one invoice line replaced four tools and four invoice lines

Owner’s words: “The thing I didn’t expect was EPR. I was treating it as its own problem for years. Having the packaging weights on the SKU record and the agency file generate from the orders made it a non-event.”

The EPR specifics that most sellers get wrong

VerpackG (Germany) requires every seller shipping packaged goods to B2C in Germany to register with LUCID (the official register) and report packaging placed on the market by material (paper, glass, plastic, lightweight metal, heavy metal, composite). The report is quarterly in volume and annual in detail.

BDO (Poland) requires registration for battery-containing products and for packaging. The report is annual in detail.

In both cases, the data the agency wants is: SKUs sold, units sold, packaging weight per SKU by material, battery weight per SKU. Vedron attaches this data to the SKU record once and generates the agency file from the sales data per the submission period.

What did not move

The Steuerberater (tax advisor) still runs on DATEV. Vedron exports the posted invoices to DATEV, which the Steuerberater receives in the format they already use.

FAQ

How long did the move from four tools to Vedron take?

6 weeks of setup, mostly supplier catalog mapping and configuring the Allegro parameters per category. The bank reconciliation and EPR data entry took 2 weeks of parallel running before going fully on Vedron.

Did the owner have to re-register with LUCID or BDO?

No. Vedron produces the submission file in the format each register expects; the registrations stay as they were. The seller continues to submit through the same login.

What happened with the Allegro listings during the move?

Vedron matched existing Allegro listings to the imported catalog by EAN and SKU. 94 percent matched automatically; the remaining 6 percent were manually mapped. No Allegro listing was recreated or lost.

Was the Steuerberater involved in the move?

Yes. The export format for DATEV was validated with the Steuerberater before go-live. The monthly DATEV handoff continues as before, just from Vedron instead of from the invoicing SaaS.

Did the move break any marketplace rankings?

No ranking disruption on Allegro or Amazon. Stock sync and tracking push-back were tested in parallel for 2 weeks before cutover, so marketplace SLAs stayed clean through the move.

Did you enjoy this article?