{"id":29202,"date":"2024-10-26T07:06:00","date_gmt":"2024-10-26T06:06:00","guid":{"rendered":"https:\/\/www.web-systems.pl\/off-the-shelf-vs-custom-b2b-system-2026\/"},"modified":"2024-10-26T07:06:00","modified_gmt":"2024-10-26T06:06:00","slug":"off-the-shelf-vs-custom-b2b-system-2026","status":"publish","type":"post","link":"https:\/\/www.web-systems.pl\/en\/off-the-shelf-vs-custom-b2b-system-2026\/","title":{"rendered":"Off-the-shelf vs custom B2B system &#8211; what to choose in 2026?"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">The choice of a commerce platform for a B2B channel can decide a company&#8217;s competitiveness for years to come. I am not exaggerating. In 2026, business-to-business e-commerce is no longer just a product catalog and an order cart. You need integration with ERP, WMS and CRM, dynamic price list management and, more and more often, <a href=\"https:\/\/www.web-systems.pl\/en\/development-of-artificial-intelligence-based-applications\/\">AI-based mechanisms<\/a>. The scale of requirements is growing faster than ever and companies face a fundamental question: a ready-made B2B platform or a solution built to measure? We at Web Systems, a software house from \u0141\u00f3d\u017a operating since 2006, have delivered both approaches dozens of times. We have seen projects where a ready-made system worked perfectly for years. But we have also seen ones where, after a dozen or so months, the client came back asking for migration to a custom application, because the boxed platform was blocking growth. We know the real cost of both paths, we know where the traps appear, and we can point to the moment when an investment in custom development starts to pay off. This article is not another vague comparison. Instead of repeating marketing slogans, we go through concrete decision criteria: from architecture and scalability, through hidden costs, to the MVP rollout strategy. We discuss every point from the perspective of a contractor who knows project problems from the inside. Do you run a wholesale business with a thousand SKUs? Or a manufacturing company serving several dozen regular partners? You will find guidance here that will help you make an informed decision instead of a costly experiment.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Spis tre\u015bci<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.web-systems.pl\/en\/off-the-shelf-vs-custom-b2b-system-2026\/#How_a_ready-made_B2B_system_differs_from_a_custom_solution\" >How a ready-made B2B system differs from a custom solution<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.web-systems.pl\/en\/off-the-shelf-vs-custom-b2b-system-2026\/#When_a_ready-made_B2B_system_is_enough_and_when_it_becomes_a_trap\" >When a ready-made B2B system is enough, and when it becomes a trap<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.web-systems.pl\/en\/off-the-shelf-vs-custom-b2b-system-2026\/#Hidden_costs_what_the_brochures_of_B2B_platforms_do_not_mention\" >Hidden costs: what the brochures of B2B platforms do not mention<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.web-systems.pl\/en\/off-the-shelf-vs-custom-b2b-system-2026\/#Architecture_and_scalability_the_foundation_of_a_B2B_system_for_years\" >Architecture and scalability: the foundation of a B2B system for years<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.web-systems.pl\/en\/off-the-shelf-vs-custom-b2b-system-2026\/#How_to_approach_the_choice_decision_criteria_for_companies_in_2026\" >How to approach the choice: decision criteria for companies in 2026<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.web-systems.pl\/en\/off-the-shelf-vs-custom-b2b-system-2026\/#FAQ_the_most_common_questions_about_B2B_systems\" >FAQ: the most common questions about B2B systems<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.web-systems.pl\/en\/off-the-shelf-vs-custom-b2b-system-2026\/#How_much_does_a_custom_B2B_system_cost_compared_with_a_ready-made_platform\" >How much does a custom B2B system cost compared with a ready-made platform?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.web-systems.pl\/en\/off-the-shelf-vs-custom-b2b-system-2026\/#Can_you_start_with_a_ready-made_system_and_move_to_a_custom_solution_later\" >Can you start with a ready-made system and move to a custom solution later?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.web-systems.pl\/en\/off-the-shelf-vs-custom-b2b-system-2026\/#Summary_a_ready-made_or_a_custom_B2B_system\" >Summary: a ready-made or a custom B2B system?<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_a_ready-made_B2B_system_differs_from_a_custom_solution\"><\/span>How a ready-made B2B system differs from a custom solution<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A ready-made B2B system is a platform available in a SaaS model or as licensed software. You buy the product, configure it for your needs and start selling. Typical examples? Solutions based on Magento or Shopware, or Polish platforms such as IdoSell B2B or Sote. A custom solution is a completely different story: it is built from scratch around the specific business processes of the company. A team of developers designs the architecture, builds the functionality and delivers an application owned by the customer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical features of ready-made B2B platforms:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Quick start &#8211; a rollout within a few weeks, sometimes even days<\/li>\n<li>Limited customization &#8211; modifications are possible only within the limits set by the vendor<\/li>\n<li>Subscription model &#8211; predictable monthly costs, but they grow with scale<\/li>\n<li>Vendor dependency &#8211; updates, roadmap and feature availability depend on the supplier<\/li>\n<li>Ready modules &#8211; catalog, cart, partner management, basic discounts<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Custom systems? Here you get a full match with your processes, control over the source code and the architecture. The entry cost is higher, yes. But in exchange you get freedom to develop without anyone&#8217;s approval. The client owns the application and does not have to ask an external vendor for permission to modify a feature that happens to be blocking their business. Every element of the system, from discount logic to the quotation mechanism, reflects the company&#8217;s real workflow.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>\u201cThe most important principle is separation of concerns: dividing the application into methods, classes, files, packages, modules and layers that have clearly defined responsibilities and boundaries.\u201d<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">This architectural principle applies to both types of system, but in practice, and I say this from experience, only in custom solutions can you be sure it has been applied consistently. And one more thing. The split into &#8220;ready-made&#8221; and &#8220;custom&#8221; is not binary. More and more often we see a hybrid approach: companies start on a boxed platform, and the modules that really have to work their way (for example an advanced product configurator or a non-standard discount system) are built as custom extensions connected through an API.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"When_a_ready-made_B2B_system_is_enough_and_when_it_becomes_a_trap\"><\/span>When a ready-made B2B system is enough, and when it becomes a trap<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A boxed platform works very well in a few scenarios. If a company offers a relatively simple product catalog, a standard order process and serves a small number of partners, a ready-made solution will cover its needs without unnecessary complications. It also works when you care about a fast market entry: launching B2B sales online in weeks instead of months. Are you still testing the digital channel and have no established processes yet? A SaaS platform is a sensible first step.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The problem appears at the moment we call the inflection point. What is that? It is the situation where the cost of working around the limits of a ready-made system exceeds the cost of building a custom feature. We see it regularly with clients who come to Web Systems after two or three years of working on a boxed platform. They started with a simple catalog, and today they need multi-level discount logic that takes purchase history into account, individual currency price lists and automatic price recalculation based on NBP (Polish central bank) exchange rates. The ready-made system did not anticipate that, so the IT department builds yet another set of spreadsheets and manual workarounds. Rather sad.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical problems that signal the vendor lock-in trap: API limits that make full synchronization with the ERP impossible, no control over the database structure, no way to modify the checkout process, a forced update schedule that can break working integrations. Each of these obstacles generates costs, both direct (extra plugins, paid consultations with the vendor) and indirect (lost sales opportunities, frustrated partners).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Tip:<\/strong> Before you sign a contract with a ready-made platform supplier, write down a list of the business processes you have to handle over the next 2-3 years. For each of them check whether the platform offers native support or whether it needs a plugin or a non-standard modification. If more than 30% of the processes require workarounds, consider the custom path from the start. Seriously, that 30% threshold has worked for us many times as a good indicator.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>\u201cResearch covering in-depth proprietary studies, industry best practices, trend analysis and quantitative modeling makes it possible to develop innovative approaches that support stronger and more sustainable business results.\u201d<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">That way of thinking, based on data and modeling rather than on intuition, should accompany the decision about a B2B platform. Instead of following the popularity of a solution, it is better to analyze your own processes and consider how they will evolve. Because they will. They always evolve.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Hidden_costs_what_the_brochures_of_B2B_platforms_do_not_mention\"><\/span>Hidden costs: what the brochures of B2B platforms do not mention<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The price list of a ready-made B2B platform looks tempting. A few hundred zloty a month for the basic package, a few thousand for the enterprise version. Sounds fine, right? Well, exactly: reality turns out to be more complex. The base license is only the beginning of the spending. On top of it come premium plugins for specific functions (invoice export, advanced filters, integration with a particular ERP), user limits that force you into a more expensive plan, and fees for exceeding transaction thresholds. In one of the projects we analyzed before migration to a custom system, the client was paying more than three times more for the SaaS platform than the basic price list suggested. Three times!<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The cost of integration with external systems is a separate spending category and it is almost always underestimated at the planning stage. Connecting a B2B platform with an ERP (for example SAP, Comarch, Enova), a WMS warehouse system, a CRM tool or a logistics platform requires development work regardless of the chosen model. But the difference is this: in a custom system you design the integration exactly around your needs. In a boxed platform you have to adapt to the limits of the available API, which often means functional compromises or the need to build additional intermediate layers. And that is more money.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Maintenance and updates generate further costs, which look completely different in each model. In SaaS the vendor is responsible for infrastructure and security, but at the same time imposes the schedule of changes, and those changes can force modifications on the client&#8217;s side. I have experienced it myself. In the custom model the company controls the update cycle but takes responsibility for monitoring, patching and reacting to threats. Neither option is free of charge: they differ in how the risk is distributed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">But the most expensive mistake we see? Data migration when the platform changes. Companies that decide to move after a few years on one system discover that exporting commercial data &#8211; order history, individual price lists, discount structures, partner assignments &#8211; is a project in itself. It takes weeks and swallows tens of thousands of zloty. That is why, when comparing options, we always recommend a TCO (Total Cost of Ownership) analysis over a horizon of at least three, ideally five years. Only that perspective reveals the true cost ratio of the two approaches.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Architecture_and_scalability_the_foundation_of_a_B2B_system_for_years\"><\/span>Architecture and scalability: the foundation of a B2B system for years<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>\u201cApplication architecture is the foundation of high-quality software. A well-defined architecture makes it possible to build scalable, maintainable applications that can adapt to a constantly growing ecosystem of devices and requirements.\u201d<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">This principle, although formulated in the context of mobile applications, describes the challenges of B2B systems perfectly. A commerce platform serving dozens of partners today has to be ready for hundreds tomorrow. Without rewriting the code from scratch. Architecture is not an abstract idea from a textbook: it is the foundation that decides whether the system survives growth in scale, new integration requirements and changing business needs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Separating the layers &#8211; user interface, business logic and data &#8211; is really the key to the longevity of any B2B system. In custom solutions we design that separation deliberately from day one, choosing the technology stack to match the specifics of the project. Ready-made platforms also use a layered split, but their architecture has to be universal enough to serve thousands of different customers. And that means compromises which, in your particular case, may turn out to be blockers to growth.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The API-first approach we use at Web Systems when <a href=\"https:\/\/www.web-systems.pl\/en\/software-development\/\">building custom systems<\/a> treats every module as an independent service communicating through well-defined interfaces. What does that give you in practice? Replacing the payment module, adding a new sales channel or connecting another warehouse does not require rebuilding the whole application. And it makes an enormous difference in integrations: a B2B system talking to five or seven external services needs stable, versioned endpoints, not monolithic code where changing one function can wreck order synchronization. I have seen it more than once.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The security of commercial data &#8211; price lists, discounts, payment terms, transaction history &#8211; requires special attention. In the SaaS model the data lives on the vendor&#8217;s infrastructure, so you have to trust their security policy and regulatory compliance. A custom system gives you full control over data location, encryption, access policies and auditing. And in 2026 AI mechanisms built into B2B platforms play an ever larger role, from product recommendations and dynamic price list adjustment to chatbots supporting partner service. In custom systems we can select models and training data precisely for the specifics of the client&#8217;s industry instead of relying on the vendor&#8217;s generic algorithms. The difference in accuracy can be enormous.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_approach_the_choice_decision_criteria_for_companies_in_2026\"><\/span>How to approach the choice: decision criteria for companies in 2026<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The decision about the B2B system model should be based on a methodical process. Not on the impression left by a sales presentation (although those can be convincing, no question). Based on several dozen projects delivered at Web Systems, we have worked out a sequence of steps that helps companies make an informed decision:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Business process audit<\/strong> &#8211; map all the flows related to B2B sales: from the request for quotation, through the order and invoicing, to complaint and return handling<\/li>\n<li><strong>Integration analysis<\/strong> &#8211; identify the systems the B2B platform has to communicate with (ERP, WMS, CRM, logistics, payments, BI) and assess the complexity of each connection<\/li>\n<li><strong>Growth estimate<\/strong> &#8211; estimate the number of partners, SKUs, orders and users over a 3-year horizon; take seasonality and planned expansion into account<\/li>\n<li><strong>TCO budgeting<\/strong> &#8211; compare the total cost of ownership of both options over 3 and 5 years, including licenses, integrations, maintenance, training and the cost of a possible migration<\/li>\n<li><strong>Vendor lock-in risk assessment<\/strong> &#8211; check the data export terms, API availability and the platform supplier&#8217;s pricing policy in case your strategy changes<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The MVP (Minimum Viable Product) approach works both when choosing a ready-made platform and when building a custom system. Instead of rolling out a complete system at once, you launch the features that are really needed &#8211; catalog, cart, basic integrations &#8211; and collect feedback from partners. Iterative expansion lets you verify assumptions in practice and avoid investing in features that ultimately turn out to be unnecessary. Because yes, part of the features from the initial requirements is never used. I have checked.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There are situations where the most sensible strategy is to deliberately start with a ready-made platform and plan a migration to a custom solution once a certain scale is reached. But it has to be planned from the beginning: pick a platform with a good export API, keep the data in a structured form, document the business processes. Prototyping and a proof of concept before the final decision let you verify the technical assumptions without committing the full budget. The worst scenario? A migration forced by a sudden decision of the vendor to change the price list. Plan B should exist before it becomes urgent.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Whatever model you choose, and I want to stress this, the choice of technology partner matters more than the technology itself. A company that understands your processes, can advise on architecture and is able to take you through the rollout, maintenance and development of the system. That counts for more than the specific backend technology. The platform will change. The relationship with a competent contractor stays.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"FAQ_the_most_common_questions_about_B2B_systems\"><\/span>FAQ: the most common questions about B2B systems<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_much_does_a_custom_B2B_system_cost_compared_with_a_ready-made_platform\"><\/span>How much does a custom B2B system cost compared with a ready-made platform?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A ready-made B2B platform in the SaaS model costs from a few hundred to a few thousand zloty a month for the license alone. On top of that come the costs of configuration, integrations and premium plugins: in total from 20,000 to 80,000 PLN in the first year, depending on the complexity. A custom B2B system? An investment in the range of 80,000-300,000 PLN at the MVP stage, with the option of iterative expansion. The difference in entry cost is clear, but over five years the TCO of the two approaches can level out, especially when the ready-made platform requires paid extensions and costly workarounds. The price of a custom system depends above all on the number and complexity of the integrations, how complicated the discount and pricing logic is, the performance requirements and the scope of process automation. I always recommend starting with an MVP estimate based on a process audit, not with rough guesses.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Can_you_start_with_a_ready-made_system_and_move_to_a_custom_solution_later\"><\/span>Can you start with a ready-made system and move to a custom solution later?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes, and it is a strategy we regularly carry out with Web Systems clients. But it requires deliberate planning from day one. The optimal moment for migration? The point where the cost of monthly workarounds and missing features starts to exceed the amortization instalment of a custom system. That usually happens after 18-36 months of intensive use of a boxed platform. Migration risks include the loss or corruption of historical data, operational downtime while switching systems and the need to retrain users. To minimize them, document your processes from the start, take care of data quality and choose a starting platform with good export options. The worst scenario is a migration forced by a sudden vendor decision to change the price list or end support. Plan B should exist before it becomes urgent.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Summary_a_ready-made_or_a_custom_B2B_system\"><\/span>Summary: a ready-made or a custom B2B system?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There is no universal answer. The decision depends on the complexity of your business processes, the number and nature of integrations with external systems, the planned scale of growth, the budget over several years and the degree of control over data and infrastructure. A company with a simple catalog and a standard order process can function perfectly on a ready-made platform for years. A business with multi-level pricing logic, a specific quotation workflow and the need to synchronize with several ERP systems will almost certainly reach a return on investment faster with the custom approach.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In general, make the decision on the basis of solid analysis. A process audit, an integration map, a growth estimate, a TCO comparison. Not on the basis of a supplier&#8217;s advertising or an opinion from a forum. What counts is the fit with the reality of your company, not the market popularity of a solution. The MVP approach limits the risk whatever path you choose, and iterative expansion of the system guarantees that you invest only in features that actually bring value to your partners.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At Web Systems we have been helping companies make these decisions and turn them into working systems since 2006. Are you facing a choice of B2B platform? Planning a migration from an existing solution? Do you want to build an MVP from scratch? <strong>Contact us<\/strong>. We will audit your needs, propose an architecture and price the rollout, so that you can make a decision based on facts, not guesses.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>The choice of a commerce platform for a B2B channel can decide a company&#8217;s competitiveness for years to come. I am not exaggerating. In 2026, business-to-business e-commerce is no longer just a product catalog and an order cart. You need integration with ERP, WMS and CRM, dynamic price list management and, more and more often, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":28148,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[820,812,826],"tags":[887,948,958,1176,1114,1385,1132],"class_list":["post-29202","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business","category-e-commerce-en","category-technology","tag-b2b-en","tag-e-commerce-en","tag-erp-en","tag-implementation","tag-saas-en","tag-sales-platforms","tag-software-house-en"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/posts\/29202","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/comments?post=29202"}],"version-history":[{"count":0,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/posts\/29202\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/media\/28148"}],"wp:attachment":[{"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/media?parent=29202"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/categories?post=29202"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/tags?post=29202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}