E-Commerce Platforms & Shop Systems
IdoSell
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by DreamCommerce S.A. · www.idosell.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
IdoSell at a glance
- Vendor
- DreamCommerce S.A.
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates IdoSell 2/5, the mean of 6 judges. IdoSell, an e-commerce platform from DreamCommerce S.A., was judged on catalog and checkout, tax and legal, extensibility, operations, data control and exit, and sovereignty. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
IdoSell, an e-commerce platform from DreamCommerce S.A., was judged on catalog and checkout, tax and legal, extensibility, operations, data control and exit, and sovereignty. Its strongest area is operations, which scored 6-7: judges credited a single fulfilment queue across storefronts and the marketplaces Allegro, Amazon and Empik, a built-in warehouse system, returns, dropshipping and courier dispatch to InPost, DPD and Orlen Paczka, all under a single contract. The weakest of the substantive criteria is data control and exit, scored 2-3: everything published about migration runs inbound — products, images, descriptions and customer data — and we found no public information on export completeness, order history leaving or self-hosting. Sovereignty scores sit at 3 with no sovereignty attributes on record; a KNF-licensed payments service and Polish-language support point at a Polish operation, but we found no public information on hosting location or subprocessors. Tax and legal scores run 3-5: platform-side upkeep of KSeF, JPK, Omnibus and GPSR is documented, but scoped to Polish obligations. The only prices published are a free demo and a free individual consultation.
Speaks for it
- Operations, the highest-scoring area at 6-7, puts storefronts, B2B and the marketplaces Allegro, Amazon and Empik into a single fulfilment queue.
- A built-in warehouse system, returns handling and dropshipping from connected suppliers and wholesalers run under a single contract with one provider.
- Parcels are dispatched to InPost, DPD and Orlen Paczka from the panel without logging into courier sites.
- KSeF, JPK, Omnibus and GPSR are implemented platform-side in updates, with KSeF e-invoicing built in.
- Wholesale and retail customers are served on one account with separate price lists, alongside one-click purchase and merchant access to template code, CSS, JavaScript and custom API integrations without an agency.
Held against it
- Data control and exit scored 2-3, with migration documented inbound only and no public information on export completeness, order history leaving or self-hosting.
- Sovereignty scored 3 with no sovereignty attributes on record, and we found no public information on hosting location or a subprocessor list.
- The documented regulatory upkeep is scoped to Polish obligations, and we found no public information on destination-based VAT, OSS, reverse charge or VAT-ID validation.
- We found no public information on variant matrices, bundles, promotions and vouchers, guest checkout, or payment methods beyond IdoPay on a KNF licence.
- We found no public information on maintained interfaces to ERP or accounting systems, or on partial shipments and refunds.
Best for
- You run storefronts plus marketplace sales on Allegro, Amazon and Empik and want one shared warehouse and a single fulfilment queue.
- You serve wholesale and retail on one account and want separate customer price lists with KSeF e-invoicing built in.
- You ship with InPost, DPD or Orlen Paczka and want dispatch handled from the panel without courier-site logins.
- You dropship from connected suppliers and wholesalers and want store, warehouse, payments and couriers under a single contract.
Avoid if
- You sell mainly into Germany or other markets outside Poland — the documented regulatory upkeep covers Polish obligations (KSeF, JPK, Omnibus, GPSR), and we found no public information on destination VAT, OSS or reverse charge.
- You need a documented way out — the published migration story runs one way, bringing in products, images, descriptions and customer data, and data control and exit scored 2-3.
- Your orders must land in a named ERP or accounting system — the integration categories documented from the panel are payments, couriers, marketplace, fulfilment, certificates and partners, and we found no public information on maintained ERP or accounting interfaces.
- You must verify where customer data is hosted and which subprocessors are involved — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 2 of 5 |
| Tax & German legal correctness | 2 of 5 |
| Extensibility & developer surface | 2 of 5 |
| Order operations & back office | 3.5 of 5 |
| Data ownership & exit | 1 of 5 |
| European sovereignty | 1.5 of 5 |
Catalogue & checkout
Show reasoningHide reasoning
How this is scored
Products, variants, pricing rules and the path to payment — the part that either converts or does not.
0 — Flat product list with one price and no variants; checkout is a form and one payment method.
3 — Variants and categories with a standard checkout and two or three payment methods, but no bundles, no tiered pricing and no guest checkout worth the name.
5 — Full variant matrix, product bundles, tiered and customer-group pricing, guest checkout, and the payment methods a German shop needs including invoice and direct debit.
8 — Configurable products, per-channel pricing, promotions and vouchers with rules, a checkout that can be customised without a rebuild, and payment via the major providers plus buy-now-pay-later where offered.
10 — Merchandising and checkout are the product: rule-driven pricing and promotions, A/B-testable checkout, multi-currency and multi-language as standard, and conversion features (abandoned cart, one-page checkout) shipped rather than bolted on.
The Merchant
One-click purchase and templates that reach right into the cart and checkout, plus separate price lists for wholesale versus retail customers, is conversion material I can work with. But I found no public information on variants, bundles, promotions and vouchers with rules, guest checkout, or the payment methods German shoppers expect, invoice and direct debit included. 1
The B2B Seller
Separate customer price lists for wholesale and retail and a one-click purchase flow are the two conversion facts on the page, and the price lists speak directly to trade customers. I found no public information on variant matrices, bundles, guest checkout, or which payment methods a German B2B buyer gets besides IdoPay — payment on account and direct debit are what my clients ask for first, and the page is silent on them. 1
The Developer
Checkout templates are editable at code level and one-click buying ships in the panel, and B2B runs on separate price lists per customer — but we found no public information on variant matrices, bundles, promotions and vouchers, or the payment breadth a German shop actually needs, so shipped conversion tooling alone cannot carry it further. 1
The Operations Lead
Separate price lists for wholesale and retail, full-store templates editable in the panel and a shipped one-click purchase are real conversion levers. Beyond that I found no public information on variant matrices, bundles, promotion and voucher rules, or payment methods beyond the vendor's own licensed payments. 1
The Data Protection Officer
The captured page shows full-store templates editable in the panel, a one-click checkout, and separate price lists for wholesale and retail customers on one account. We found no public information on variant handling, product bundles, tiered pricing, guest checkout, or which payment methods sit behind the vendor's own licensed payment service, so the breadth a checkout needs beyond the licensed service is unevidenced. 1
The Skeptic
Templates are claimed to cover the whole store through cart and checkout with a one-click purchase feature, and B2B customers get separate price lists. But we found no public information on variant matrices, bundles, tiered or rule-driven promotions, or the payment methods a German checkout needs — the only payment named is the vendor's own IdoPay on a KNF licence. 1
Tax & German legal correctness
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, and the checkout requirements German law actually imposes — judged on what the platform does, not on a plugin someone could buy.
0 — A single VAT rate applied everywhere; no B2B handling, no country logic, no legal-text handling in checkout.
3 — Per-country VAT rates configurable by hand, net prices for B2B possible with effort, and legal texts as free-form pages.
5 — Automatic VAT by destination and customer type, VAT-ID validation with reverse charge, gross and net display per customer group, and the mandatory checkout elements (order button wording, withdrawal policy, price indications) handled.
8 — OSS thresholds tracked and reported, correct invoicing per case including reverse-charge notes, small-business and third-country handling, and e-invoicing (XRechnung/ZUGFeRD) for B2B orders.
10 — Tax and legal correctness are maintained by the vendor rather than the merchant: rates and thresholds updated as the law moves, OSS reporting produced, every invoice case correct out of the box, and documented conformity a lawyer could review.
The Merchant
The vendor states that KSeF, JPK, Omnibus and GPSR are implemented on the platform side within updates, which is the right model — but it is a Polish story. I found no public information on VAT by destination, OSS reporting, reverse charge with VAT-ID validation, or the checkout texts German law imposes. 1
The B2B Seller
KSeF, JPK, Omnibus and GPSR are implemented by the platform in its updates and invoicing with KSeF is built in, which is vendor-maintained legal correctness in the Polish mould. But I found no public information on VAT-ID validation, reverse charge, per-country VAT determination or OSS — the machinery a shop selling B2B into Germany must show before I sign. 1
The Developer
Regulatory upkeep is platform-side — KSeF, JPK, Omnibus and GPSR land as updates, with KSeF e-invoicing built in — which is the vendor-maintained pattern I want to see; but it is the Polish rulebook, and we found no public information on OSS, reverse charge, VAT-ID validation or the checkout elements German law imposes, so international selling alone does not evidence automatic VAT by destination. 1
The Operations Lead
The right model is there — KSeF, JPK, Omnibus and GPSR implemented platform-side in updates, invoicing wired to the Polish e-invoicing system. But those are Polish instruments; I found no public information on automatic VAT by destination, OSS, VAT-ID reverse charge or the checkout elements German law imposes, so for a German shop this is promise-shaped. 1
The Data Protection Officer
Regulatory upkeep is done platform-side for named instruments — e-invoicing with the Polish KSeF, JPK, the EU Omnibus pricing rules and GPSR — which shows a vendor-maintained posture rather than merchant-assembled compliance. We found no public information on destination-based VAT determination, reverse charge with VAT-ID validation, OSS reporting, or the checkout legal texts German law requires. 1
The Skeptic
The vendor does say KSeF e-invoicing, JPK, Omnibus and GPSR are implemented platform-side within updates, with invoicing including KSeF bundled — maintenance rather than merchant homework, though scoped to Polish obligations. We found no public information on VAT determination by destination and customer type, OSS, reverse charge with VAT-ID validation, or the mandatory German checkout elements. 1
Extensibility & developer surface
Show reasoningHide reasoning
How this is scored
Themes, apps, APIs and headless — whether the shop can be shaped to the business, and at what cost in lock-in.
0 — Fixed templates, no app ecosystem, no API.
3 — Theme editing within limits and a small app store; a read-mostly API and no local development story.
5 — Custom themes with a template language, an app or plugin ecosystem, a documented REST API, and webhooks for the core order events.
8 — Full storefront API for headless builds, an extension framework with its own lifecycle, staging environments, version control for themes, and documented rate limits.
10 — A platform a team can own: headless-first APIs, open-source or source-available core, plugin architecture with a real dependency model, local development and CI supported, and upgrade paths that do not orphan customisations.
The Merchant
Template code, CSS and JavaScript with custom API integrations, changeable without an agency, means a checkout I can reshape without a rebuild — my first question answered. I found no public information on an app or plugin marketplace, a documented API reference, webhooks, staging environments or headless storefront builds. 1
The B2B Seller
Access to template code, CSS and JS plus custom integrations via the API, without engaging an agency, is a real developer surface for a hosted shop. I found no public information on a documented API reference, webhooks, an app ecosystem or headless storefront builds, so what it costs to shape this platform beyond its own panel is not stated. 1
The Developer
Template code, CSS and JS are open and custom integrations go through an API — better than a closed editor — but I found no public information on version control for themes, a local development story, staging environments, webhooks or any plugin ecosystem, and as the one who maintains the customisations, that silence is the migration risk itself. 1
The Operations Lead
Template code, CSS, JavaScript and custom API integrations without an agency is more than paint. I found no public information on an app or plugin ecosystem, a documented API surface, webhooks, staging environments or local development, so a developer arrives to a key and a wish. 1
The Data Protection Officer
Template code, CSS and JavaScript are open to the merchant, with custom integrations via API and modification without engaging an agency — that goes beyond theme editing within limits. We found no public information on an app or plugin ecosystem for third parties, webhooks for order events, a documented storefront API, or staging environments and version control for themes. 1
The Skeptic
Merchants can reach template code, CSS and JS and build their own API integrations without an agency, and payments, couriers, marketplaces and fulfilment are claimed to connect from the panel without commissioning a developer. We found no public information on a documented API surface, an app or plugin marketplace, webhooks, staging environments, or a headless storefront. 1
Order operations & back office
Show reasoningHide reasoning
How this is scored
What happens after checkout: order management, stock, returns, shipping, and the link to ERP or accounting.
0 — An order list and an email; stock is a number nobody trusts, returns are manual.
3 — Order statuses and basic stock, one shipping integration, and returns handled by hand.
5 — Order workflow with partial shipments, multi-warehouse stock, named carrier integrations with label printing, and a returns process in the system.
8 — Multi-channel order intake, automated fulfilment routing, supplier and dropshipping flows, and maintained interfaces to named ERP and accounting systems.
10 — The shop is the front of an operation: real-time stock across channels and warehouses, returns and refunds fully worked including partials, ERP integration the vendor maintains, and operational reporting a merchant runs the business from.
The Merchant
Store, B2B and marketplace orders land in one fulfilment queue on a shared warehouse, with built-in WMS, returns, invoicing, dropshipping from supplier stock, and carrier dispatch for InPost, DPD and Orlen Paczka — the back office ships rather than gets bolted on. I found no public information on partial shipments and refunds, or on maintained interfaces to named ERP and accounting systems. 1
The B2B Seller
This is the strongest part: a built-in WMS, returns handling, one fulfilment queue across stores and marketplaces, dropshipping from connected suppliers and wholesalers, and shipping through InPost, DPD and Orlen Paczka without logging into courier sites — all under a single contract. I found no public information on maintained interfaces to named ERP or accounting systems, which is where my clients' order flow has to land. 1
The Developer
The back office is real: orders from multistore and the marketplaces arrive in one fulfilment queue, a built-in warehouse system, returns and KSeF invoicing sit under a single contract, couriers are named and booked from the panel, and dropshipping pulls stock and shipments from connected suppliers — but we found no public information on maintained interfaces to ERP or accounting systems, or on partial shipments and refunds. 1
The Operations Lead
One fulfilment queue across stores, marketplaces and B2B, a built-in WMS behind several shops on shared stock, dispatch to InPost, DPD and Orlen Paczka without logging into courier sites, and dropshipping and returns inside a single contract — the visible parts of my day are genuinely worked. But partial shipments and partial refunds have no public information, nor any interface to a named ERP or accounting system, so the back office stops short at the warehouse door. 1
The Data Protection Officer
One shared order queue and warehouse across multiple storefronts on separate domains, built-in WMS, dropshipping from connected suppliers, returns in the same panel, and courier dispatch to named carriers without logging into their sites, with marketplace intake from Allegro, Amazon and Empik. We found no public information on maintained interfaces to named ERP or accounting systems, which is what separates the strong back offices. 1
The Skeptic
Post-checkout looks like a real operation: built-in WMS, returns handled in the system, parcels dispatched to named carriers InPost, DPD and Orlen Paczka without courier-site logins, dropshipping from connected suppliers and wholesalers, and a single fulfilment queue taking intake from the store and the marketplaces Allegro, Amazon and Empik. We found no public information on maintained interfaces to named ERP or accounting systems, or on partial shipments. 1
Data ownership & exit
Show reasoningHide reasoning
How this is scored
Whether the catalogue, customers and order history remain the merchant's: export completeness, hosting choice, and what leaving actually costs.
0 — Export is a partial CSV; order history and customer records cannot leave intact, and hosting is the vendor's alone.
3 — CSV export of products and customers, order history partial, no self-hosting, no documented migration path.
5 — Complete export of catalogue, customers and orders via API or dump, documented deletion, and a stated data-return commitment.
8 — Full-fidelity export including media and order documents, self-hosting or a choice of hosting partner, and no metering that prices a migration out of reach.
10 — Ownership is structural rather than promised: open-source or source-available platform the merchant can run anywhere, database-level access, documented migration in both directions, and contractual data return.
The Merchant
Migration in is well evidenced — products, images, descriptions and customer data transferred for over 400 stores a year, with no gap in sales — but that is one direction only. I found no public information on export of catalogue, customers and order history on the way out, on self-hosting, deletion, or what leaving actually costs. 1
The B2B Seller
The migration story runs one way: products, images, descriptions and customer data are brought in, with 301 redirects and no sales gap, and over 400 shops a year arrive. I found no public information on export completeness for order history, deletion or self-hosting, so what leaving actually costs is not on the page. 1
The Developer
Everything documented about migration points inwards — products, images, descriptions and customer data moved in, domain kept, redirects protecting search visibility — while we found no public information on export of the catalogue, customers or order history, on self-hosting, or on any documented path out; a single-provider contract with no evidenced exit is a one-way door. 1
The Operations Lead
Everything published concerns coming in — products, images, descriptions and customer data migrated, domain kept, 301 redirects, no gap in sales, over 400 shops a year making the move. On leaving, I found no public information on export completeness, self-hosting or a data-return commitment, so the exit door is unmarked. 1
The Data Protection Officer
Migration is documented in one direction only — products, images, descriptions and customer data brought in, over 400 stores a year with no sales gap and 301 redirects for SEO — and that list does not name order history. We found no public information on export of catalogue, customers or orders on the way out, on deletion, or on any choice of hosting, so the cost of leaving is unevidenced. 1
The Skeptic
Everything published about moving data points inward: products, images, descriptions and customer data transferred in, over 400 stores a year, domain kept with 301 redirects and no sales gap during the switch. We found no public information on export completeness, order history leaving intact, self-hosting, or any documented path out — and the single contract with a single provider that makes arrival tidy is exactly what a merchant should understand before relying on goodwill at exit. 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where customer and order data live, who the contracting entity is, and which subprocessors sit in the checkout path. Independently sourced by the sovereignty pipeline.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.
3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — CDN, analytics, payment routing, support tooling — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, complete subprocessor list published, any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that puts the shop entirely under the merchant's control.
The Merchant
DreamCommerce S.A. with a payment arm licensed by the KNF reads as a European contracting entity, and everything runs under one contract with one provider. But the captured page publishes no subprocessor list, and I found no public information on where customer and order data are hosted. 1
The B2B Seller
No sovereignty attributes are on record, and I found no public information on hosting location or the subprocessor chain in the checkout path. Polish-language support and payments on a KNF licence point to a Polish operation, but the captured page names no infrastructure and publishes no subprocessor list. 1
The Developer
The visible stack reads Polish — the vendor, a payments service on a financial-regulator licence, Polish-language support — but the sovereignty record carries no attributes, and we found no public information on hosting location or the subprocessor list, so nothing above inference is evidenced. 1
The Operations Lead
The contracting entity reads European — a Polish joint-stock company behind a KNF-licensed payment service, support in Polish. I found no public information on hosting location or any subprocessor, so the chain cannot be checked end to end. 1
The Data Protection Officer
Everything captured is Polish — Polish-language support, a payments service licensed by the Polish financial regulator, Polish e-invoicing — which points to a European contracting vendor, and the single-contract model puts payments under that one provider. But no sovereignty attributes are on record: hosting location, where any CDN or analytics sit, and the full list of subprocessors in the checkout path are all absent from the public pages. 1
The Skeptic
The vendor presents itself as a Polish company with payments running on a KNF licence, which points at an EU entity, but the sovereignty pipeline has no attributes on record for this vendor. We found no public information on where hosting sits, the contracting entity's jurisdiction, any published subprocessor list, or certification; payments sit in the vendor's own hands under one contract, but the rest of the chain is unlit. 1
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a merchant can compute the real annual cost — licence, transaction fees, apps, hosting — from public pages alone. The category where the headline price is least often the invoice.
0 — No public prices at all; every tier is a sales conversation.
3 — A monthly headline exists, but transaction fees, mandatory apps or hosting costs are unstated — the invoice is unknowable from the page.
5 — Tier prices public with billing period stated and transaction fees given, but at least one commonly needed piece (a required app, hosting, payment gateway rate) is unpriced.
8 — Every tier priced publicly including transaction or revenue-share rates, order or GMV limits, and the cost of the extensions most shops need; VAT treatment and minimum term stated.
10 — Complete price computability: annual cost derivable for a given order volume and GMV including licence, transaction fees, hosting and typical extensions — and for open-source platforms, an honest statement that the licence is free and where the money actually goes.
The Merchant
I found no public information on tier prices, transaction or revenue-share fees, order limits, billing period or minimum term — the page offers a free consultation and a free demo, which makes every price a sales conversation. I judge price against contribution, and with nothing priced publicly there is nothing to weigh. 1
The B2B Seller
The only figures on the page are a free demo and a free individual consultation — the annual cost of licence, IdoPay transaction fees and hosting is not derivable from public information. For a merchant comparing platforms, the price here is a conversation with a specialist, not a computation. 1
The Developer
The only priced items on the captured page are a free demo and a free consultation with a specialist; no tier, licence fee, transaction rate, minimum term or VAT treatment is public, so a merchant cannot compute any annual cost from the page alone. 1
The Operations Lead
The only figures published are a free demo and a free individual consultation. No tier price, transaction fee, billing period or minimum term is on the page, so the annual invoice is unknowable and you book the conversation instead. 1
The Data Protection Officer
The only prices stated anywhere are the free demo and the free individual consultation — no tier price, no transaction fee, no order or revenue limits, no billing period and no VAT treatment. The real annual cost is not derivable from the public pages; every pricing question routes through a consultation. 1
The Skeptic
No price appears anywhere in the captured material — no licence fee, no transaction or revenue-share rate, no order or GMV limits, no hosting line, no VAT treatment, no term. What the page offers instead is a free demo and a free individual consultation, which is a sales conversation by another name; a merchant cannot compute a single euro of the annual invoice from public pages. 1
Questions about IdoSell
Is IdoSell European?
Not determined: the vendor’s pages as captured do not say where IdoSell is based.
Where does IdoSell store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does IdoSell have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to IdoSell?
As of 21 Oct 2026, the panel rates JTL-Shop (3/5), Medusa (3/5) and Shopify (3/5) highest among the other 25 E-Commerce Platforms & Shop Systems products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is JTL-Shop (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: IdoSell alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on compliance on the pages we read (idosell.com). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (1)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.idosell.com Checked 13 Oct 2026 Details →