Integrations
ERP, payments, subscriptions and fulfillment that stay in sync. Integrations that retry on their own and tell you when they cannot.
Who this is for
- Merchants whose ERP, warehouse and store disagree about stock or order status
- Subscription and digital-content businesses where billing and access must match exactly
- Teams replacing a payment, shipping or ERP provider on Adobe Commerce without stopping sales
What you get
A map of every data flow
Which system owns orders, stock, prices and customers, in which direction data moves and how often.
Integrations that survive failure
Each call goes through a queue and can be retried safely, so a timeout at the ERP does not become a lost or duplicated order.
Alerts before customers notice
Failed syncs and growing queues reported in New Relic or Datadog before they turn into a support ticket.
Documentation your team can run
Field mappings, error handling and recovery steps written down, so the integration does not depend on me.
How it works
Before any code
Map
One flow at a time
Build
After go-live
Watch
In detail
Most integration failures trace back to unclear data ownership or to synchronous calls that block checkout. The rest are jobs that fail silently at night and leave stock or orders out of step by morning.
I start by agreeing which system owns each kind of record, from orders and stock to prices and customers. Then I move work out of the request path into message queues such as RabbitMQ and make every call safe to repeat. Logging is detailed enough to answer “what happened to order 1042” in one query. I have connected stores to NetSuite, SAP and custom ERPs. On the payment side that means Stripe, Braintree, Authorize.Net and Amazon Pay, plus Zuora and Stripe Billing for subscriptions. For shipping and accounting it means ShipStation, QuickBooks and Synder.
At Teabloom I designed the catalog and inventory flow across seven sales channels on these rules, through GeekSeller and Finale Inventory.
You get integrations your team can operate and extend, with monitoring that tells you about a problem before your customers or your accountant do.
At Guidance I built ERP integrations, custom shipping modules and subscription billing for 8-figure-GMV merchants on Adobe Commerce.
The first step is a written map of who owns which data and where each flow can fail. Each integration is then scoped and quoted as its own project.
Questions
How do we start, and how is the work priced?
We start with a written map of your data flows. It shows which system owns orders, stock, prices and customers, which way data moves and where each flow can fail. Each integration is then scoped and quoted as its own project.
What happens when a sync fails at night?
Each call goes through a queue and can be retried safely, so a timeout at the ERP does not turn into a lost or duplicated order. Failed syncs and growing queues raise alerts in New Relic or Datadog before they turn into a support ticket.
Can our own developers run the integrations afterwards?
Yes. Field mappings and recovery steps are written down, and monitoring with alerts is in place before I hand over. The integration does not depend on me.
Can we change our payment, shipping or ERP provider without stopping sales?
Yes, that is one of the cases this work is for. The new flow is built behind a queue, tested against real edge cases and switched on only after that.
Related case study
7Sales channels
One catalog across seven sales channels and a B2B site
Read the case study