Magento Extension Development
Creating an extension for the big logistics service provider that can be added to Magento stores.
Key Results:
-
Client:
Logistics service provider
-
Service type:
Magento development
-
Core technologies:
Magento, PHP
Magento earns its cost when the catalog is large and the pricing rules are complicated. Forbytes builds for exactly that case: custom modules, ERP and PIM integrations, and a store that stays fast as products multiply.
| Magento Development Benefit | Business Impact |
|---|---|
| Magento 2 upgrade or migration | The store gets security patches and support again |
| Performance-tuned storefront | Pages and checkout stay fast when traffic multiplies |
| Clean, documented customizations | Updates stop breaking features that used to work |
| ERP, PIM, and WMS integrations | Stock, prices, and product data stay in sync everywhere |
| Multi-store and multi-currency setup | New markets launch from one codebase, not a rebuild |
| Managed release pipeline | Deployments run on schedule and without store downtime |
Store & Code AuditReviewing your Magento version, custom code, extensions, and performance under real load.
|
#2
|
Architecture & IntegrationsDesigning the theme, the extension set, and data exchange with ERP, PIM, and logistics.
|
#4
|
Testing & Peak Load ChecksRunning functional, integration, and load tests against production-scale catalog data.
|
#6
|
|
#1
|
Upgrade or Rebuild DecisionChoosing between upgrading in place, rebuilding, or replatforming, with costs for each.
|
#3
|
Development & Data MigrationBuilding the store, replacing conflicting extensions, and migrating your catalog data.
|
#5
|
Launch & Ongoing SupportLaunching off-season, then handling patches, updates, and new features on schedule.
|
That is usually enough to say what is holding the store back. We’ll come back with the risks we see and what an upgrade or rebuild would involve.
Group Manager, Guesty
CIO at AB Stenströms Skjortfabrik
CEO at The African Touch
The work covers new store builds, migration from Magento 1 or another platform, version upgrades, theme and frontend development, custom module development, extension audits and replacement, ERP, PIM, and WMS integration, catalog and customer data migration, performance tuning, and ongoing support. Where the platform decision itself is still open, e-commerce consulting runs first as a separate engagement.
Magento earns its cost when your catalog is large, your pricing or B2B rules are complex, and you need control over the checkout. It stops being worth it when your store is essentially a template with a small catalog, since licence, hosting, and maintenance then buy you flexibility you never use. The audit compares your current running costs against both options before anyone commits.
Magento 1 stopped receiving security patches in 2020, so payment providers and insurers increasingly treat it as a liability. Practical routes are three: migrate to Magento 2, replatform elsewhere, or build custom. A Magento 1 to 2 move is a rebuild rather than an upgrade, because the codebase differs, so we scope it as a project with catalog and customer data migration included.
Yes, and it is a large share of our commerce work. We start with a code, extension, and performance audit that reports on technical debt, security exposure, and which customizations are safe to keep. Then we agree what gets fixed before new features start. An undocumented store adds a handover period, and we scope that separately instead of hiding it inside an optimistic estimate.
We set up and manage the infrastructure on Azure, AWS, or Google Cloud, including the deployment pipeline, monitoring, and backups. Support runs on an agreed model that covers security patches, version updates, bug fixes, and reserved capacity for new features. During your peak weeks, releases pause by default and an engineer familiar with your setup stays on call.
Third-party inventory expands the catalog without buying stock. It also brings seller onboarding, commission rules, listing quality, split payments, payouts, refunds across two parties, and a support queue that now has three sides. Forbytes builds marketplace platforms with that operational load designed in — seller portal, money flow, and the internal tooling your category managers work in daily.
| Marketplace Development Benefit | Business Impact |
|---|---|
| Catalog grows through third-party sellers | Revenue expands without stock purchase or warehouse cost |
| Self-serve seller onboarding with KYC | Partner count scales past what an email inbox can handle |
| Commission rules configurable per category | Margin adapts by product type without an engineering release |
| Split payments and scheduled payouts | Seller money moves on time and stays off your balance sheet |
| Rule-based listing screening with a review queue | Category managers handle exceptions instead of every submission |
| Order-level commission and reconciliation exports | Finance closes the month without rebuilding numbers in a spreadsheet |
Business Model DefinitionCommission, fulfilment, and pricing rules settled before code.
|
#2
|
Platform BuildCatalog, search, orders, and the seller portal on your stack.
|
#4
|
Pilot Cohort LaunchLaunching a first seller group under close operational monitoring.
|
#6
|
|
#1
|
Seller Journey DesignOnboarding, contracts, and KYC verification mapped end to end.
|
#3
|
Settlement ArchitectureWiring split payments, payouts, refunds, tax, and reconciliation.
|
#5
|
Operational ScalingReplacing manual review with automation as listing volume grows.
|
Tell us the seller types, fulfilment model, and markets you plan to open. We come back with a scope split into releases and the ops headcount the model implies.
Group Manager, Guesty
CIO at AB Stenströms Skjortfabrik
CEO at The African Touch
Custom marketplaces are built by a software development company from scratch. In this case, a client pays for the development and maintenance of marketplace solutions. SaaS marketplaces are those offered by third parties. If clients use a SaaS marketplace (like Amazon or Etsy), they pay a regular fee for the use and not for the creation.
et’s mention a few:
Rules first, review second. Category templates define required attributes, so incomplete listings never reach the queue. Automated checks catch duplicate GTINs, image resolution failures, restricted terms, and price outliers against category medians. Everything flagged lands in a moderation queue with seller-level trust scores, so proven sellers publish instantly and new sellers get sampled. Sellers who fail repeatedly get throttled automatically.
A first cohort typically goes live four to six months after kickoff for a build on top of an existing eCommerce platform, with the money layer and seller portal in the first releases. Open seller intake follows two to three months later, once moderation and payouts run without manual steps.
A licensed payment provider handles the money — Stripe Connect, Adyen for Platforms, and Mangopay all support marketplace flows. The buyer pays once; the provider splits the amount between your commission and the seller balance, holds funds through the return window, and releases payouts on your schedule.
We build the ledger that sits above it: order-level commission records, adjustment handling for refunds and partial returns, VAT treatment per market, and reconciliation exports for finance. We stay out of custody of funds, which keeps licensing requirements with the provider.
Advice holds up when the people giving it have shipped the same work. Forbytes ecommerce consultants audit your stack, price the routes forward, and can deliver the one you choose. You leave the engagement with a costed comparison of every option and a roadmap broken into releases.
| Ecommerce Consulting Benefit | Business Impact |
|---|---|
| A priced comparison of every route forward | The replatform decision stops circling and gets signed |
| A ranked list of delivery bottlenecks | Engineering time goes to the constraint, not the loudest ticket |
| Vendor selection based on your traffic and catalog data | You buy the platform that fits your load, not the one that demos well |
| A phased 12–18 month roadmap with checkpoints | Budget gets approved in stages instead of one contested lump |
| A cost model behind each technical option | Finance and engineering argue from the same numbers |
| An honest audit of the inherited stack | You find what breaks before peak season does |
Stack auditReviewing platform, integrations, and code with your engineers.
|
#2
|
Option modellingPricing two or three routes forward against risk and timeline.
|
#4
|
Stakeholder alignmentPresenting trade-offs to your board and defending the numbers
|
#6
|
|
#1
|
Commercial mappingTracing where revenue leaks: conversion, ops cost, failed orders.
|
#3
|
Roadmap designSequencing the plan into phases your team starts next sprint.
|
#5
|
Implementation supportHanding over to your team, or joining it with our engineers.
|
Tell us where delivery slows down — integrations, release process, data quality, platform limits. We will show you what each one costs and what fixing it takes.
Group Manager, Guesty
CIO at AB Stenströms Skjortfabrik
CEO at The African Touch
No. Unlike other consulting firms, Forbytes offers ecommerce business consulting as a separate service independent of web development. If you hire our ecommerce consultant and we create a plan for your ecommerce strategy, it does not obligate you to hire our product engineering team for the plan execution.
Nonetheless, you can scale our cooperation whenever you need it. If you like our ecommerce solutions services and want to continue working with Forbytes — our specialists will be glad to study your business requirements and help you achieve your goals.
Forbytes is one of the ecommerce consultancy companies that can help you build custom enterprise solutions, web and mobile applications, Product Information Management (PIM) systems, etc. We also assist offline businesses in the process of moving online. Our ecommerce advisors ensure effortless migration, with all data preserved and managed online.
Besides, we offer customization services and help with the integration of third-party digital products into ecommerce websites. Our solutions accelerate growth and always are secure as well as forward-looking.
Your engineers sit in the audit sessions and review our findings before anything reaches the board. They know where the problems started, and skipping them produces a report that reads well and helps nobody. Where your team disagrees with a conclusion, we record the disagreement in the report.
Yes, we can. Forbytes runs modernization, integration, and platform teams, so the engineers who scoped the work can build it. Handing the roadmap to another vendor also works — we write it so any competent engineering group can execute it.
Not to overload you with text, we’ve listed only the most common eCommerce consulting services that we offer. However, our approach to ecommerce solution services is human-centric, meaning that there are no strict limits on services. We always can adjust our strategy to the client’s expectations. So, if your request does not fit into any of these categories — you are always welcome to get in touch with Forbytes and get answers to your questions.
An online store is judged on the two weeks a year when everything runs at once. Forbytes builds and rebuilds commerce platforms that hold under that load, connect properly to your ERP, PIM, payment, and logistics systems, and let your team ship changes without waiting for a release window.
| E-commerce Development Benefit | Business Impact |
|---|---|
| Custom or replatformed storefront | The store supports how you sell, not how the template expects |
| ERP, PIM, and WMS integration | Stock, prices, and product data stay correct across systems |
| Performance and load optimization | Peak days run without slowdowns or manual intervention |
| Optimized checkout and payment setup | Fewer abandoned carts at the final step |
| Multi-store and multi-market setup | New markets launch without a separate build each time |
| Automated release pipeline | Changes ship weekly instead of quarterly |
Store & Systems AuditReviewing your current platform, its integrations, performance data, and where sales leak.
|
#2
|
Architecture & IntegrationsDesigning the storefront architecture and its data exchange with ERP, PIM, and logistics.
|
#4
|
Load Testing & LaunchTesting against peak-season traffic on production-scale data, then launching off-season.
|
#6
|
|
#1
|
Solution & Platform ChoiceChoosing between improving the current setup, replatforming, or building custom, with costs.
|
#3
|
Development & MigrationBuilding the store, connecting the systems, and migrating your catalog and customer data.
|
#5
|
Growth & OptimizationRunning conversion experiments, adding markets, and shipping features against a release schedule.
|
Traffic, checkout, stock sync, or the manual work behind it. Describe your setup and we’ll come back with what fails first and what it takes to fix.
Group Manager, Guesty
CIO at AB Stenströms Skjortfabrik
CEO at The African Touch
The work covers building or rebuilding the storefront, connecting it to the systems behind it, and keeping it running as you grow: platform selection, custom development, Magento work, marketplace builds, composable commerce architectures, ERP and PIM integration, catalog and customer data migration, performance tuning, and post-launch support. Where the decision itself is unclear, e-commerce consulting runs as a separate engagement first.
Replatforming is the expensive answer, so it needs a reason beyond frustration. Improving the current setup usually wins when the platform still receives updates, when the problems are performance or integration related, and when your team can work in it. Replatforming earns its cost when licence and hosting fees keep climbing, when the vendor blocks integrations you need, or when every change requires workarounds. The audit gives you both numbers before you commit.
Magento sits at the core of our commerce work, alongside custom builds on Microsoft .NET, Node.js, PHP, and React. For composable setups we assemble the storefront, PIM, search, and checkout from separate services rather than one suite. Platform choice follows your catalog size, integration needs, market count, and who maintains the store afterwards.
Yes, and this is common. We start with a code, performance, and integration audit that reports on technical debt, security issues, and what the previous setup automated versus what your team does by hand. Then we agree what gets fixed first. Handover of an undocumented store adds a discovery period, and we scope that separately rather than absorbing it into an estimate that later slips.
Load testing runs on production-scale catalog and traffic data before your high season, not after an incident. Support during peak periods works on an agreed model with response times and an on-call engineer who knows your setup. Releases stop during your peak weeks by default, and we plan the schedule around your commerce calendar from the start.
Search stays as it was in 2019 because the module sits three layers deep in the monolith. Every vendor demo promises MACH, and every quote assumes an 18-month rewrite with a hiring freeze on new features. Forbytes moves you to composable commerce by cutting one domain at a time — storefront first, then catalog, then checkout — while the current platform keeps processing orders.
| Composable Commerce Benefit | Business Impact |
|---|---|
| Storefront releases independent of backend cycles | Campaigns launch on marketing's schedule, not on the release train |
| Each capability sits under its own contract | You renegotiate or replace one vendor without touching the rest |
| Traffic-heavy services scale on their own | Peak load costs less because you stop scaling the whole platform |
| Market-specific logic lives in its own service | New country launches ship in weeks without core code changes |
| Failure and regression scope limited to one domain | A bad release affects one capability instead of the whole store |
| Migration runs one domain per release | The roadmap keeps moving while the architecture changes underneath |
Domain MappingWe split the platform into catalog, cart, orders, and promotions.
|
#2
|
Pilot ServiceOne service runs behind a proxy while the monolith stays live.
|
#4
|
Orchestration Layer DevelopmentHolding vendor contracts, events, and data rules in one API layer.
|
#6
|
|
#1
|
Cut Sequence DefinitionWe select the first component to detach and define the seams.
|
#3
|
Storefront DecouplingThe storefront moves to its own release cycle and CDN edge.
|
#5
|
Domain RolloutRepeating the migration until the core holds only orders.
|
Tell us the seller types, fulfilment model, and markets you plan to open. We come back with a scope split into releases and the ops headcount the model implies.
Group Manager, Guesty
CIO at AB Stenströms Skjortfabrik
CEO at The African Touch
This depends on a variety of factors, including your business goals, software requirements, scalability requirements, number of software components within the system, etc. The approximate lower bound of the work volume is around 1800-2500 hours. This includes core integration of a headless front-end, ecommerce site, and PIM. The more customizations and composable apps are needed, the more time it will take to complete the project.
Rules first, review second. Category templates define required attributes, so incomplete listings never reach the queue. Automated checks catch duplicate GTINs, image resolution failures, restricted terms, and price outliers against category medians. Everything flagged lands in a moderation queue with seller-level trust scores, so proven sellers publish instantly and new sellers get sampled. Sellers who fail repeatedly get throttled automatically.
You start with demand you already have, which is why an existing retailer builds a marketplace faster than a startup does. We launch with a small invited cohort in categories where your traffic already searches for products you do not stock, using search logs to pick them. Open intake comes after the operational tooling handles that first cohort without manual work.
A licensed payment provider handles the money — Stripe Connect, Adyen for Platforms, and Mangopay all support marketplace flows. The buyer pays once; the provider splits the amount between your commission and the seller balance, holds funds through the return window, and releases payouts on your schedule. We build the ledger that sits above it: order-level commission records, adjustment handling for refunds and partial returns, VAT treatment per market, and reconciliation exports for finance. We stay out of custody of funds, which keeps licensing requirements with the provider.
We offer two main pricing models to choose from. These include a time-and-material approach and a fixed-price model, with the first being more efficient and popular among our clients. Contact us for details.