Orders, inventory, prices, payments and reconciliation in sync, with no retyping and a log of every transaction. For operations running an ERP, store and gateway.
Free first conversation · Reply within 1 business day
Mahout ERP:
Hub with Magento 2, Moip/Wirecard, Asaas and Melhor Envio
Open source:
Official PagSeguro and Mercado Pago Magento 2 modules, 214K installs
NF-e via SEFAZ and OFX bank reconciliation in Mahout ERP
MPC:
Resent until acknowledged (at-least-once), with per-screen delivery logs
Mahout ERP: hub with Magento 2, Moip/Wirecard, Asaas and Melhor Envio
Open source: official PagSeguro and Mercado Pago Magento 2 modules, 214K installs
NF-e via SEFAZ and OFX bank reconciliation in Mahout ERP
MPC: resent until acknowledged (at-least-once), with per-screen delivery logs
The marketplace sold a product that was already out of stock, because the update failed and nobody was alerted.
Finance reconciles payments, fees and payouts in a spreadsheet, and every month closes with differences nobody can explain.
The integration hub covers the basics, but your pricing, bundle or warehouse rule does not fit its configuration.
When the partner API goes down or changes, orders get lost on the way and the customer is the first to notice.
Orders from marketplaces such as Mercado Livre, Shopee and Amazon, integrated through the official API, reach the ERP with customer, items, shipping and payment, and status flows back.
Inventory and prices published to each channel from the ERP, with rules per warehouse, bundle and margin, updated on every change so no channel sells what is out of stock.
Integration with the gateway you choose, through hosted checkout or API, with validated webhooks, refund and chargeback handling and payment status reflected on the order.
Automatic matching of orders, receipts, fees and payouts from gateways and marketplaces, with a discrepancy report so finance works by exception.
Queues, retries at growing intervals, idempotency keys and a failed-message (dead-letter) queue for reprocessing, so a message is neither lost nor applied twice.
A log per transaction with the request and response of each system, failure alerts and a view of what is pending and why.
See also: e-commerce development, custom software development, and AI business process automation.
The integration hub of the ERP for e-commerce, payments and shipping, alongside tax invoicing and bank reconciliation.
Merged contributions to the official PagSeguro and Mercado Pago payment modules for Magento 2, plus other open-source libraries.
Related experience, in integrations: Sunlighten, the internal SaaS behind residential solar operations, wired to Salesforce, DocuSign and Airplane to automate the workflow from sale to installation.
Related experience, in delivery reliability: promotion updates sent to in-store devices with at-least-once delivery.
Facing a similar challenge? Tell us the problem and the timeline.
Free first conversation · Reply within 1 business day
Marketplace and payment gateway integration is the API connection between ERP, online store, marketplaces and payment providers, so that orders, inventory, prices, payments and reconciliation flow without retyping. Hire it when a ready-made hub does not cover your rules, or when sync failures already cause overselling, lost orders or financial discrepancies.
We map systems, APIs, volumes and the points where orders, inventory or payments diverge today. You receive the flow design, a recommendation between a ready-made hub, a native connector or a custom integration, the plan and the estimate.
We specify every flow: fields, rules, the source of truth for each piece of data and what happens on each failure (timeout, duplicate, invalid data). You approve the contracts and the acceptance criteria before any code.
One end-to-end flow in the test environments of the partners, with simulated failure cases. You receive a working PoC, the test logs and a recommendation to proceed, adjust or stop.
The remaining flows in short iterations, with automated tests, monitoring and gradual activation per channel. You receive the integrations in production, with logs, alerts and a documented reprocessing routine.
We follow the first order and reconciliation cycles, tune the alerts and document the operation. Partner API changes and new channels can continue under a monthly retainer.
| Scope | Typical timeline | Engagement model |
|---|---|---|
| Integration discoveryFlows, APIs, failure points, recommendation (hub, connector or custom), plan and estimate | 1–2 weeks | Fixed-scope project |
| Proof of conceptOne end-to-end flow in sandbox, with simulated failure cases | 2–4 weeks | Fixed-scope project |
| ProductionOrder, inventory, pricing, payment or reconciliation integrations, with logs, alerts and reprocessing | 6–12 weeks | Fixed scope or time & materials with a cap |
| Support and evolutionAPI changes, new channels and monitoring | Ongoing | Monthly fractional retainer |
Timelines are typical ranges. Discovery defines the scope and the estimate of each project; the contract can be in USD or BRL.
Want to know which format fits your project?
Free first conversation · Reply within 1 business day
Integration is deterministic code: AI speeds up the build, but it does not decide where an order or a payment goes. Specs and tests come before the code, and every merge gets human review.
Where AI comes inAI coding agents (Claude Code, Codex, Cursor, Copilot, OpenCode) implement connectors, mappings and tests from approved specs.
What humans reviewAPI contracts, idempotency rules, error handling and every merge go through senior human review.
Quality gatesContract and integration tests in sandbox, with simulated failure cases, before every release.
AI in operationsDiscrepancy classification and suggested fixes can come in a later phase, always with human approval.
Your dataCredentials live in a secrets vault, client data never trains models, and we work under NDA.
| Criterion | SaaS integration hub (Bling, Tiny, Olist) | Native platform connector | Custom integration |
|---|---|---|---|
| When it makes sense | Popular channels and standard pricing and inventory rules | The platform or the ERP already offers the connector you need | Rules of your own, systems with no connector or volume that demands control |
| Costs | Subscription, usually by plan or order volume | Included in the platform or sold as a module | Initial development; then hosting and maintenance |
| Business rules | Configurable within what the hub supports | Fixed: the flow is what the vendor designed | They follow your operation: pricing, bundles, warehouses and invoicing |
| When something fails | Depends on the hub dashboard and support | Depends on vendor support | Retries, idempotency, logs per transaction and reprocessing under your control |
| Who maintains it | The hub vendor | The platform vendor | Your team or partner, with tests and monitoring |
When the hub does not cover a rule that affects sales or cash: per-channel pricing with its own margin, bundles, multiple warehouses, invoicing per branch or a system it does not connect to. If a hub such as Bling, Tiny or Olist covers your channels and your rules, stay with it: it costs less and is ready in days. It is also common to keep the hub and custom-build only the missing flow.
Typical timelines are: discovery in 1–2 weeks, a proof of concept of one flow in sandbox in 2–4 weeks and integrations in production in 6–12 weeks. The timeline depends on the number of flows, the quality of the API documentation and the approval time each partner requires, which is outside our control.
The message stays in a queue and is resent automatically, with backoff, until the partner is back. Every operation carries an idempotency key, so a retry does not duplicate an order or a charge. If the error persists, the message goes to a dead-letter queue, raises an alert and can be reprocessed after the fix. Related experience: at MPC, we implemented this pattern for in-store promotion updates, with at-least-once delivery, acknowledgments, automatic retries and delivery logs.
The integration matches every order against the receipt, the fees and the payout reported by the gateway or the marketplace, and flags only the discrepancies. Finance stops checking line by line and handles exceptions: a different amount, an unexpected fee, a late payout, a refund. In Mahout ERP, which we built, bank reconciliation used OFX files, alongside the Asaas and Moip/Wirecard integrations.
We design the integration so that card data does not pass through your servers: hosted checkout or the gateway's own fields, with tokenization. In general terms, hosted checkout leaves the smallest share of PCI DSS scope with the merchant, an API with hosted fields sits in the middle, and processing cards directly demands the most effort. We are not auditors and do not certify compliance: validation is done with your gateway or acquirer.
By integrating the platform with a gateway or payment provider that operates in Brazil, which then offers Pix, installment card payments and boleto through its API. We handle the integration: charge creation, confirmation webhooks, refunds and reconciliation. Local entity, currency exchange and taxes depend on the provider you choose and on your advisors. Related experience: merged contributions to the official PagSeguro and Mercado Pago modules for Magento 2, and the Asaas and Moip/Wirecard integrations in Mahout ERP.
Yes, as long as there is an integration point: an API, a database, files or a queue. In discovery we assess which one is safe and, if needed, build an API layer in front of the ERP. Related experience: at Regal Rexnord, we built order modules integrating applications with SQL Server and the Logix ERP; at ADT Solar, we integrated Salesforce and DocuSign.
It depends on the number of flows (orders, inventory, prices, payments, reconciliation), the quality of the APIs involved and the level of error handling and monitoring required. That is why we do not publish a price list. A 1–2 week discovery defines scope and estimate, and the proposal can be fixed scope or time & materials with a cap, in USD or BRL. Also account for recurring costs: hosting, partner fees and maintenance when APIs change.
AI-focused IT consultancy
Senior engineering from discovery to delivery: whoever designs the architecture also writes and reviews the code.
Master Timm · Updated on
In the first conversation we look at the systems, the flows and where they fail today, and tell you plainly whether a ready-made hub is enough or a custom integration pays off.
Free first conversation · Reply within 1 business day