IdoSell vs Endora Commerce — which one to pick for B2B

IdoSell is the most “Polish” of the large e-commerce systems, and it has earned that label honestly over more than twenty years on the market. You launch a store in days and you never see the server. The things that can eat half a project in Polish retail are built in and maintained by the vendor: two-way Allegro integration, courier brokers, InPost pickup points, KSeF e-invoicing, a bridge to Comarch and Subiekt. On top of that comes something almost nobody offers at this price point: a full WMS with storage zones, shelf locations and a barcode-scanner app. For most Polish stores this is the right answer, and there is no point looking further.

This article is about where “most” runs out.

The difference between these platforms starts at the point of origin. IdoSell built a very good retail engine and added a B2B module on top, an add-on costing PLN 99 to 149 net a month. The module provides individual price lists, trade credit, gated access to the catalog and company sub-accounts with permissions. Endora Commerce went the other way: the buyer is an organization, the price comes from a contract, an order can be the outcome of a negotiation, and retail selling runs as an extra channel on the same data model. Below is where that difference stops being theoretical, and where it makes no difference at all.

The short version

If you only read three sentences: pick IdoSell when you sell wholesale from a price list, the warehouse is a real part of your daily work, and Polish market realities (Allegro, couriers, KSeF, Comarch) simply have to work without a project. Pick Endora when business-to-business selling has mechanics of its own: prices are negotiated, orders travel through steps nobody else has, and your customer base is a tree of branches rather than a list of accounts. And one thing worth saying up front: at launch and for the first several years IdoSell is markedly cheaper. The exact figures are in the cost section.

What each platform actually is

IdoSell

IdoSell is SaaS, run by IAI, a company based in Szczecin. The store lives in the vendor’s cloud: you have no server access, no code and no database. You have an admin panel, a template, integrations and an API.

The pricing model is described as “pay as you grow”: you pay a subscription plus a fee for every order. The published plans are Start at PLN 119, Business at PLN 279, Expert at PLN 699 and Enterprise at PLN 2,299 net a month, plus an Individual tier from PLN 14,299.

Since August 2026 the order billing model has been unified: only the Start plan keeps a free order allowance (20 a month). On Business, Expert, Expert+, Enterprise and Individual every order is billed at the rate for that plan. Store-order rates are PLN 1.59 on Business, PLN 1.49 on the new Expert+ and PLN 0.85 on Enterprise; non-store orders (marketplaces, POS) are cheaper. One important property of this model: the fee does not depend on basket value or revenue. A store with a high average order value does very well on it.

B2B selling is a separately paid module: PLN 149 net a month on Business and Expert, PLN 99 on Enterprise, included on Individual, and not available on Start at all. The module provides discount groups with individual price lists, trade credit with a limit and deferred payment terms, hiding prices from logged-out visitors, a minimum wholesale order value, company sub-accounts with permissions, and paying several invoices in one go.

The B2C and B2B channels can run on separate domains, with different assortments and different price structures, managed from a single panel. That costs a multistore surcharge of PLN 29 to 39 net a month per extra store plus a one-off PLN 99 activation.

Two things deserve calling out, because comparisons usually lose them. First, the built-in WMS: an unlimited number of storage zones per warehouse, products assigned to a floor, rack and shelf, stocktaking in the panel, and the IdoSell Scanner app for barcode terminals. Second, phone and email support on business days at no extra charge. For a company without an IT department that is not a detail.

Endora Commerce

Endora Commerce is a B2B platform written in TypeScript: a Fastify backend with MikroORM and Zod contracts, a server-rendered Next.js storefront, and a React admin panel. Data in PostgreSQL, cache and queues in Redis, search in Meilisearch. Over 60 modules as standard: from the catalog and price lists to KSeF, product feeds and an AI assistant in the panel.

B2C selling runs on the same installation and the same data model: registering a consumer creates a single-person organization behind the scenes, so orders, quote requests, invoices and addresses all travel the same path as in B2B. B2C is enabled separately for each sales channel.

The delivery model is the opposite of IdoSell’s: you pay no subscription and no per-order fee, you get a platform rolled out around your processes, with the code in your own Git repository and the data in your own database. The first working prototype takes four weeks, and an average rollout falls roughly in the PLN 60-80k range, excluding integrations with external systems, which are quoted separately.

Performance

Two things get conflated here, so it is worth splitting them: the performance of the platform itself, and the performance of your integration traffic.

The platform itself

IdoSell has an advantage here that comes from the model, not the technology. The store runs in the vendor’s cloud, seasonal peaks are IAI’s problem rather than yours, and on the Enterprise and Individual plans a dedicated server is included. Behind that stand two decades of Polish Black Fridays and thousands of stores on the same infrastructure. Nobody will call you at night because the disk filled up.

Endora renders the storefront on the server in Next.js, with Core Web Vitals targets written directly into the platform requirements (LCP under 2.5 s, INP under 200 ms, CLS under 0.1) and search under 200 ms at the 95th percentile. The target scale is hundreds of thousands of SKUs plus hundreds of orders and quote requests a month on a single VPS: a minimum of 4 vCPU and 8 GB RAM, 8 vCPU and 16 GB recommended. The demo runs on a catalog of more than 120k SKUs, and generating a product feed for 100,000 products produces a 38 MB file with peak memory use under 20 MB, because serialization is streamed.

Those are good numbers, but it is still a server somebody has to monitor, patch and back up. IdoSell does not have that problem by definition, and that is a real advantage rather than a marketing line.

Your integration traffic

Here the picture flips, because in SaaS the performance of your integrations is a line item on the price list. IdoSell grants a monthly allowance of free API calls: 100,000 on Start and Business, 200,000 on Expert, 500,000 on Enterprise and one million on Individual. Every additional block of 100,000 calls, started or not, costs PLN 50. With a dozen thousand SKUs syncing to and from an ERP, stock updates every fifteen minutes and order polling, that stops being an abstract number. Every further integration plugged into the same panel eats from the same allowance.

Endora has no such ceiling, because the API sits on your own server and is not metered. It has a different one: the performance ceiling is set by the hardware you pay for rather than by a contract with a vendor. And you are the one choosing it.

Cost of rollout and running

This is the section worth reading the whole article for, because the conclusion runs against the grain of the article’s own layout.

What exactly you pay on IdoSell

What exactly you pay on Endora

A worked example

Take a wholesaler selling to both companies and consumers: 400 store orders and 150 marketplace orders a month, a B2B channel on its own domain, and an integration with Comarch ERP Optima. On IdoSell that means the subscription plus the B2B module, plus the extra store, plus the Bridge app, plus fees on every order. I am leaving out payment commissions, because they occur on both sides.

And now the same thing over the horizon in which platform decisions actually get made. To the first year I add PLN 309 of activation and PLN 99 for launching the second store. On Endora’s side I assume a PLN 60-80k rollout and a VPS in the PLN 5-10k a year range.

Here is what follows from that table, including the part that is inconvenient for us.

In this scenario IdoSell on the Business plan is cheaper not just at the start but after five years too. PLN 78.7k against PLN 85-130k is not a gap you can talk away with architecture. If your 400 orders a month fit inside the B2B module, cost is not an argument for changing platform, and there is no point pretending otherwise.

What moves the break-even point is the per-order fee, not the subscription. At the same 550 orders a month the Enterprise plan costs PLN 2,830, more than twice the Business figure. After three years it draws level with the upper end of an Endora rollout, and after five it exceeds it by tens of thousands. The more orders you have and the lower their average value, the sooner that moment arrives. High basket value works the other way: at twenty large orders a month IdoSell’s model is simply cheap and nothing will beat it.

The payment gateway is worth costing separately. The integration fee is 0% for IdoPay, Klarna, Stripe, PayPal and InPost Pay, but 0.25% on the Expert and Expert+ plans and 0.19% on Enterprise for every other gateway. On PLN 10m of annual revenue settled through PayU or tpay that is PLN 25k a year on Expert and PLN 19k on Enterprise. That is a cost calculated from revenue, which does not exist on Endora at all, because you connect the gateway directly.

And fairly, from the other side: the IdoSell bill covers hosting, security, updates, compliance and phone support. On Endora those things do not disappear: somebody has to do them and that costs too. You can take that on yourself, or contract it to us or to a partner firm under an SLA covering both administration and development. One more thing: PLN 60-80k is a starting point, not a ceiling. Integrations are quoted separately, and development after launch has its own price.

Ease of extending the platform

The best way to test this criterion is with a single question: how long does it take to add your own “in production” order status and a “contract number” field on the order?

On Endora you do both in the admin panel. Order statuses and the transitions between them are configurable, and you can attach a business event to any transition. Custom fields are added to orders, organizations, customers, categories, products and quote requests as data, with no database migration and no code deployment.

On IdoSell you cannot do the first one at all. The order lifecycle belongs to the platform: you get the statuses the vendor defined, and you model your own process alongside them: with labels, notes and automation through the API. It works and plenty of companies operate that way, but it is a workaround rather than a model.

Credit where it is due, though: extending the system is genuinely open and free of charge. API Admin 3 is fully RESTful, comes with new documentation and a call generator, webhooks have replaced polling, and you can edit the store template with your own SMARTY/XSLT code through the Composer Pro service. That is considerably more freedom than the average SaaS grants. The boundary sits elsewhere: you can build anything around the panel, but you cannot change what the panel is: the order model, the customer model, and the rules by which a price is calculated.

IdoSell has two advantages here that cannot be argued away. Platform updates are free, automatic and never a project. There is no such thing as “migrating to a new IdoSell version”, and new integrations simply appear in the panel. And support is included in the subscription: phone and email on business days, with no bundle of hours to buy.

Endora hands you the code, but you will not find a team that knows the platform from the inside in the first job posting. That is softened by the code being ordinary TypeScript with Zod contracts rather than a bespoke framework. It is not removed, though.

One thing only works in one direction: the Endora panel has an AI assistant. You open the command palette, describe in plain language what should happen, and the assistant shows a plan and executes it once you confirm, within your permissions and with an entry in the audit log.

There is a number behind that, because “fast” on its own means nothing: a less complex module takes 1-3 days in Endora, a larger one up to a week. That excludes integrations with an ERP, WMS, CRM, PIM or OMS: those are always heavily bespoke, and writing one takes up to two weeks. Those are always heavily bespoke and can take considerably longer. The difference against a subscription model is not really about the days, though. It is that there is somebody to ask at all: on SaaS a missing feature joins the vendor’s wish list and arrives when they decide, not when you do.

Integrations with external systems

In B2B this is usually the deciding criterion, because the platform is almost never the source of truth: the ERP is, with a CRM, a WMS and increasingly an OMS beside it.

Where IdoSell wins

Polish market realities handled out of the box. This is an advantage that cannot be recreated quickly, and one no foreign platform has.

• Marketplaces, both ways. Allegro, Amazon and eBay are integrated in both directions: you list and manage offers from the panel, pull in and process orders, stock levels sync automatically, Allegro dispatch times update according to availability, and e-invoices go out to buyers on their own. Endora offers only feed templates here. That is a difference of kind, not of degree.
• IdoSell Bridge for Polish ERPs. Comarch ERP Optima, Subiekt GT and Nexo, WAPRO Mag, enova365, Streamsoft Prestiż, plus a universal mode for systems outside that list. It carries orders across with delivery methods, fees and returns.
• KSeF as standard. Invoices go to KSeF automatically from the panel, with no manual export, on the Ministry of Finance’s latest API. That is not an advantage over Endora, which has KSeF in its core, but it matters that with KSeF now mandatory neither platform leaves you with the problem.
• Open SaaS. API Admin 3 is RESTful, documented and free to extend, webhooks have replaced polling, and IdoSell publishes a separate API for wholesalers taking dropshipping orders from other stores.
• Logistics and payments in one subscription. Courier brokers, InPost, returns, IdoPay and phone support at no extra charge.

Where Endora wins

Endora’s integration layer is generic: there is no list of “supported ERPs”, there is a documented contract: a partner API, signed webhooks and encrypted provider credentials. Any ERP, CRM, WMS or OMS plugs in as an adapter module, whether that is Comarch, SAP, an in-house system written twenty years ago, or a platform nobody has heard of yet. It is the same path that produced the Stripe, PayU and tpay adapters.

The specifics this layer stands on:

• A partner API with live OpenAPI — the document is generated from the contracts in the code, with no call allowances and no PLN 50 surcharge per additional 100,000 requests.
• API keys scoped to an organization and a channel — an integration sees exactly that company’s prices and limits and can do no more than its own buyer. There is no parameter that bypasses the rules.
• Idempotent orders — a repeated request returns the same order, never a second one. That holds for concurrent repeats too.
• Webhooks signed with HMAC-SHA-256, up to eight attempts with growing backoff, and a separate view of failed deliveries with manual retry.
• Bulk quoting — a single request prices up to 200 line items for a specific organization, guaranteed to match the cart to the penny.
• Credentials encrypted with AES-256-GCM, tested on save and masked on read.
• Comarch ERP Optima and Subiekt GT natively, alongside KSeF in the FA(3) format with the KSeF number, the official receipt and a verification QR code on the PDF.

The difference comes down to this: if your systems are on IdoSell’s list, you buy the integration along with the subscription, and that is faster and cheaper than anything written to order. If your ERP is bespoke, heavily modified, or the integration has to understand what an organization and its credit limit are, you are writing code either way. The difference is that on Endora you write it in your own repository, with no call allowances and no waiting for a vendor to accommodate your case.

B2B: where Endora Commerce genuinely stands out

Let me start with what there is no point hiding: IdoSell’s B2B module covers classic wholesale in full. Discount groups with individual price lists and the option to exclude part of the assortment, trade credit with a limit and deferred terms, a customer balance, hiding prices from logged-out visitors, a minimum wholesale order value, company sub-accounts with split permissions, paying several invoices in a single transfer, and a separate B2B store on its own domain. If your B2B fits the sentence “regular customers buy at their own prices and pay on terms”, this module handles it for PLN 149 a month and no rollout will beat that.

The difference shows up where selling stops being a variant of retail.

1. Quote requests as a full negotiation loop. The scope of IdoSell’s B2B module includes no RFQ and no price negotiation mechanism: it has price lists, meaning terms agreed in advance. On Endora this is the core: the customer submits a request, the sales rep quotes it with a lead time and an expiry date, both sides can modify the terms, and an accepted quote turns into an order without retyping a single line.

Alongside that comes the none price display mode, which hides every pricing element and routes purchase intent into a quote request. It is an option for assortments that are never sold from a price list. IdoSell can hide prices from a logged-out visitor; Endora can have no price at all, because the price is yet to be created.

2. An organization hierarchy with inherited terms. IdoSell models a company as a customer account with sub-accounts. That is a flat structure: sub-accounts carry permissions, but there is no tree down which commercial terms flow. On Endora the head office and its branches form a tree: order visibility flows downward, while the price list and the credit limit are inherited from the nearest ancestor. A group with several levels needs no duplicated configuration and no separate account per branch.

3. Price as an engine, not as a list. An individual price list is an assigned column of prices. Endora’s engine resolves the price on every request from group price lists, individual contracts, quantity breaks and time windows. On top of that comes a rule builder covering channel, group, organization, category and currency, and deterministic resolution of overlapping rules. A quote pulled through the API goes through the same engine as the cart, so the two match to the penny.

4. Credit limit as a reservation, not a balance. Trade credit on IdoSell is a limit and a payment term. On Endora the limit is reserved atomically at the moment the order is placed and released once the invoice is paid or the order is cancelled, with payment methods filtered out when the limit runs out. That is the difference between a report and control: with concurrent orders from several branches of the same company, a balance calculated after the fact tends to drift.

5. Your own order lifecycle and fields that come from contracts. Statuses, transitions and business events are configured in the panel, and extra fields are added to orders, organizations, customers, categories, products and quote requests with no deployment. On IdoSell the order status belongs to the platform, and a custom field exists when the vendor anticipated it.

6. The sales channel as a first-class dimension. Storefront, marketplace, distributor portal, mobile app and POS are separate channels of the same installation, with their own products, prices, promotions, content, settings, analytics and search index. IdoSell’s equivalent is multistore: it works and it is managed from one panel, but every additional store is a separate subscription and a separate configuration.

On top of that comes something that does not show on a feature list: every sensitive operation lands in the audit log with the state before and after the change, and a sales rep can step into a customer’s context and see the prices through their eyes, with a visible banner and an entry in the log.

Where IdoSell has the advantage within B2B itself: the warehouse and logistics. A WMS with zones, locations, stocktaking and a scanner app sits in the same panel as wholesale orders, whereas Endora offers multi-warehouse with reservations and backorders but no warehouse app. Add to that paying several invoices in a single transfer, sub-account permissions split into “places orders” and “approves and pays” available on day one, and a ready API for a wholesaler taking dropshipping orders from other stores. That is a B2B scenario IdoSell handles better than most of the market.

When IdoSell will be the better choice

1. You sell wholesale from a price list, with no negotiation. Regular customers, assigned prices, deferred terms, repeat orders. The B2B module covers that in full, and it will be faster and cheaper than a rollout.

2. The warehouse is a real part of your daily work. Storage zones, shelf locations, scanner-driven picking, stocktaking. Endora has multi-warehouse but no warehouse app. IdoSell has both, in the same panel.

3. Allegro and marketplaces are a meaningful channel. Two-way integration with Allegro, Amazon and eBay, with stock sync and order pulling, is built into IdoSell. On Endora that is feed templates today.

4. You do not have and do not want technical staff. No servers, no updates, no on-call, and phone support included in the subscription. That is real value, not a false economy.

5. Time and starting budget matter. A few hundred zloty a month and a few weeks instead of tens of thousands and several months. If you are testing a B2B channel rather than building it for a decade, speed beats flexibility.

6. Your average order value is high and your order count is not. A fee charged per order rather than on revenue is exceptionally favourable then, and no one-off model will beat it.

7. You want one vendor for everything. Store, payments, couriers, returns, invoices, KSeF and support on one contract and one invoice.

When Endora Commerce will be the better choice

1. Selling goes through negotiation. Quote requests are the main path, not an add-on. Part of the assortment carries no displayed price at all, because the price emerges in conversation. That is the scenario IdoSell’s B2B module does not cover.

2. The order process has steps of its own. Technical verification, buyer-side approval, production, picking, partial releases. If your order lifecycle does not fit the vendor’s statuses, working around it with labels starts costing more than your own platform.

3. Your customer base is a tree, not a list. Corporate groups, branches inheriting the price list and credit limit from head office, order visibility flowing downward. Sub-accounts are not a substitute.

4. The price list is an engine. Individual contracts, quantity breaks, time windows, rules by channel and currency, overlapping promotions with deterministic resolution. If your sales team needs more than an assigned column of prices, this is the boundary.

5. Order volume is high and baskets are small. A fee on every order grows linearly with the business. At a few thousand orders a month it is worth working out what is left after five years.

6. The ERP has to be written anyway. A bespoke system, a heavily modified WMS, an OMS assembled from several tools. Since you cannot buy the integration off the shelf, it is worth checking whether it is better written against somebody else’s API call allowance or in your own repository.

7. You are launching a distributor portal or several channels at once. A separate assortment, prices, content and search index per channel from one panel, with no multiplying subscriptions and no separate configurations.

8. You want the code and the data. No lock-in, no migration if the vendor’s terms change, no dependence on whether a given feature survives the next release and which plan it lands in.

9. Your fields and processes come from contracts rather than a standard. Contract numbers, packaging units, buyer-side cart approval, custom business events on status transitions. On Endora most of that is configuration in the panel.

What Endora Commerce does not have

This section is in the article so that you can make a decision on the strength of it, rather than merely feel persuaded.

• A WMS with a warehouse app. Endora has multi-warehouse with reservations and backorders, but no storage zones, no shelf locations and no scanner app. IdoSell has all of it built in, and that is a strong, concrete advantage.
• Two-way marketplace integrations. Allegro, Amazon and eBay are served with feed templates rather than an integration with the marketplace API. If Allegro is your second sales channel, that is a real gap.
• Upkeep bundled into a single price. Somebody has to look after the server, the backups and the updates. IdoSell takes all of that off your hands. You can run that yourself, or contract it to us or to a partner firm under an SLA.
• Phone support included in a subscription. There is no subscription, so there is no hotline: there is a partner or your own team.
• An extensions marketplace. You cannot bolt on a feature in five minutes. Anything unusual is development work.
• A deep talent pool. Endora is developed with a partner or your own TypeScript team. The market of agencies working on IdoSell is noticeably wider.
• Twenty years of references. If your requirement is a documented decade of operating at extreme scale, IdoSell has it and Endora does not.

A short checklist

Answer these questions for yourself. The answers usually line up on one side.

1. Do your customers ask for a price before ordering, or do they buy at prices already assigned to them?
2. Does the order process have steps that cannot be called “paid” and “shipped”?
3. Are your customers single companies, or structures with branches inheriting terms?
4. How many orders do you place a month, and what is their average value?
5. Is the warehouse a process you need to run inside the system, or is a stock level and a reservation enough?
6. Is Allegro or another marketplace a real sales channel, or just a shop window?
7. What is your horizon — testing a channel for a year, or building it for five?
8. Is owning the code and the data a requirement for you, or just a nice extra?

A majority of “we negotiate prices”, “an unusual process”, “branches with inheritance”, “a lot of orders”, “we are building for years”, “we want the code” points to Endora. A majority of “selling from a price list”, “the warehouse is our process”, “Allegro is our channel”, “no technical staff”, “time and starting budget matter” points to IdoSell.

Summary

IdoSell and Endora Commerce solve different problems, even though both sell to companies. IdoSell gives you a mature Polish SaaS in which Allegro, couriers, KSeF, the warehouse and support all work from day one and require no project. You pay for that with a fee on every order, with the limits the vendor sets, and with the fact that B2B there is a module added to a retail engine.

Endora gives you a platform designed around business-to-business selling, with quote requests, an organization hierarchy, a pricing engine and your own order lifecycle in the core, at a one-off rollout cost and with no per-order fees. In return you take on running a server, the platform’s youth, the missing warehouse app and a narrower talent pool.

The simplest test: if your B2B can be described as “wholesale from a price list”, IdoSell will almost certainly be enough and will be cheaper, even after five years. If the description contains the words “we negotiate”, “branches” or “our orders go through”, it is worth costing the other option.

The Endora panel and storefront are online, so the fastest route is to click through the demo yourself or to book a free workshop, where we will walk through your processes and systems and scope the first rollout together with the integrations.

And if the conversation shows IdoSell is the better choice, we will say so plainly. A failed rollout is not a good reference for anybody.