Apps & Integrations
Your storefront and your back office, telling the same story.
Most commerce problems that look like storefront problems are integration problems. Stock that lies, pricing that drifts, orders that need re-keying, a finance team reconciling by hand. We build the pipelines that keep every system reading the same numbers.
Why Integrations Break
The demo always works. Tuesday afternoon is the test.
Nearly every integration works on the day it is built. The ones that fail six months later fail for the same handful of reasons: a webhook fired twice and created two orders. A rate limit hit during a catalog push and half the products silently stopped updating. An ERP field changed and nobody found out until finance did the month-end.
So we build for the failure cases first. Every message is idempotent, so a replay cannot duplicate an order. Every job is queued and retried with backoff, so a two-minute outage is a delay rather than a data loss. Every pipeline is monitored and alerts a human when something stalls — because the dangerous integration is not the one that breaks loudly, it is the one that quietly stops.
That discipline is the same whether we are shipping a NetSuite connector, a SAP order pipeline, or a one-off API between your storefront and a system nobody else has heard of.
Connectors & Pipelines
The integrations we build most.
Each of these is engineered per client against your actual ERP configuration — not a one-size plugin that assumes a stock chart of accounts.
Shopify NetSuite Connector
Bi-directional sync between Shopify or Shopify Plus and NetSuite: items and inventory out, orders and customers in, fulfilments and refunds back. Built as a private app on Shopify's webhooks with a queue in between, so peak-hour order bursts never overrun NetSuite's governance limits.
- Orders, customers, fulfilments, refunds, and returns
- Inventory and price-level sync including B2B customer tiers
- Governance-aware batching that respects NetSuite limits
- Replay-safe: duplicate webhooks cannot duplicate orders
Platform: Shopify & Shopify Plus
BigCommerce NetSuite Connector
BigCommerce's API-first design makes it a natural fit for ERP-driven catalogs. We sync items, pricing, and stock from NetSuite into BigCommerce and push orders back, with the same pipeline serving a hosted storefront or a headless Catalyst frontend.
- Catalog, price list, and multi-location inventory sync
- Order, invoice, and shipment write-back to NetSuite
- Customer group mapping for B2B pricing
- Works identically for hosted and headless storefronts
Platform: BigCommerce
Magento & Adobe Commerce NetSuite Connector
The deepest of the three, because Adobe Commerce carries the most complexity: multi-source inventory, shared catalogs, company accounts, and negotiable quotes all need to reconcile with what NetSuite believes. Built as a proper Magento module, upgrade-safe and testable.
- Multi-source inventory reconciliation across warehouses
- Company accounts, shared catalogs, and contract pricing
- Quote and order sync including partial shipments
- Delivered as an upgrade-safe module, not core patches
Platform: Adobe Commerce & Magento
SAP & Dynamics Pipelines
Enterprise ERPs rarely expose a clean commerce API, so the work is middleware: a translation layer that speaks your ERP's language on one side and your platform's on the other, with the mapping, queuing, and error handling that makes the difference between a pipeline and a liability.
- Field mapping and transformation documented as a contract
- Queue-based delivery with dead-letter handling
- Batch and delta sync strategies for very large catalogs
- Staging environments that mirror production behaviour
Custom API Development
For everything that is not a named connector: the legacy warehouse system, the in-house pricing engine, the supplier feed that arrives as a nightly file, the marketplace that needs your catalog in its own dialect. We design the contract, build both ends, and document it for whoever inherits it.
- REST and GraphQL API design, build, and documentation
- Webhook infrastructure with signing, retries, and replay
- Supplier, dropship, and marketplace feed pipelines
- Middleware services with monitoring and alerting included
Marketing, Search & Fulfilment Stack
The rest of the stack around the ERP: email and SMS platforms that need clean event data, search and merchandising tools that need a well-modelled catalog, 3PLs that need accurate fulfilment messages, and payment and tax services that must reconcile to the cent.
- Email, SMS, and loyalty platforms with reliable event streams
- Search, merchandising, and review platform integration
- 3PL, shipping carrier, and returns-portal connections
- Payment gateway, fraud, and tax service integration
Published Work
Apps we built and shipped publicly.
We do not just consume other people's extensions. These are our own, live on the official marketplaces and installable by anyone.
Native Msg
AdobeA messaging extension published to the Adobe Commerce Marketplace, engineered for reliability and easy install.
commercemarketplace.adobe.com ↗Torod Shipping
AdobeA shipping-carrier integration module on the Adobe Commerce Marketplace for automated rates and fulfilment.
commercemarketplace.adobe.com ↗Shopify App Store
ShopifyOur own app published to the Shopify App Store — built to the same review standards we apply to client private apps.
See Shopify work ↗How We Build Them
Six rules we don't bend.
Idempotent by default
Every message carries a key and every handler is safe to run twice. A replayed webhook produces one order, not two — the single most common cause of ERP chaos.
Queued, retried, dead-lettered
Nothing calls a downstream system synchronously and hopes. Failures retry with backoff and land in a dead-letter queue a human can inspect and replay.
Monitored, with alerts
Dashboards for throughput, latency, and failure rate, plus alerts when a pipeline stalls. Silent failure is the expensive failure.
Mapping as a contract
Field mapping is written down and agreed with your finance and ops teams before build, so "which field is the tax code" is settled in week one, not month four.
Rate limits respected
Every platform and ERP has governance limits. We batch, throttle, and schedule around them so a catalog push never takes the storefront's API budget with it.
Documented and handed over
Runbooks, architecture notes, and the code in your repository. If we disappear tomorrow, your next engineer can read how it works.
FAQ
Integration questions.
Why not just buy an off-the-shelf NetSuite connector?
Sometimes you should, and we will tell you when. Packaged connectors work well when your NetSuite instance is close to standard. They struggle when you have custom records, non-standard item types, unusual pricing logic, or B2B rules — which is most businesses past a certain size. We often start by assessing whether a packaged option plus light customisation beats a bespoke build.
Can you fix an integration someone else built?
Yes, and it is common. We start by instrumenting it so we can see what is actually failing rather than guessing, then give you a repair-or-replace recommendation with costs for both. Sometimes the answer is three days of retry logic rather than a rebuild.
How do you handle go-live without double-posting orders?
We run the new pipeline in shadow mode first — processing real messages, writing to a staging ERP instance, and reconciling against the live system until the numbers match. Cutover then happens with a short freeze window and a documented rollback.
Who owns the middleware — you or us?
You do. It runs in your infrastructure or an account you control, the code sits in your repository, and the runbook is written for a third party to follow. We offer ongoing support because clients want it, not because you would be stranded without it.
What does an integration project usually cost and take?
It depends almost entirely on how customised your ERP is and how many object types are in scope. We scope integrations in a fixed-price discovery that produces a field-level mapping document and a costed build plan, so you see the real number before committing to the build.
Start a Project
Which systems need to agree?
Tell us your platform, your ERP, and what is currently being re-keyed by hand. We will come back within one business day with an integration approach and a realistic scope.