Skip to content
Salt & Scale

Ecommerce engineering · Integrations

Integrations & automation.

ERP, CRM, and 3PL pipelines for Shopify and Adobe Commerce: real-time and batch, with retry logic and dead-letter queues. Built so failures show up in your dashboard, not in a customer complaint.

Start a project See the engineer behind it

In short

Ecommerce operations break when systems don't talk to each other reliably. Salt & Scale builds the integrations that keep Shopify or Adobe Commerce in sync with your ERP, CRM, 3PL, and warehouse management systems, in real time and in batch. Work includes webhook handlers, REST and GraphQL middleware, order and inventory sync pipelines, and automation workflows for marketing and fulfillment. Every integration ships with retry logic, observable failure states, and enough documentation that your team can diagnose problems without calling us. Prior integration work includes a microservices suite built for Hive Brands that achieved 99.9% sync reliability across promotions and operations systems.

Scope of work

What's included.

  • 01

    ERP, CRM, and 3PL integrations

    Real-time and batch sync between Shopify or Adobe Commerce and NetSuite, SAP, Salesforce, ShipBob, and other systems, with retry logic and observable failure states built in.

  • 02

    Inventory and order sync

    Bidirectional sync keeping inventory counts, order status, and fulfillment data consistent across your storefront and warehouse or 3PL, with conflict resolution for oversell scenarios.

  • 03

    Customer data sync

    Shopify customer records to CRM and email platform (Klaviyo, HubSpot, Salesforce), with segment tagging, purchase history, and lifecycle events mapped correctly.

  • 04

    Marketing and fulfillment automation

    Event-triggered automations (post-purchase sequences, reorder reminders, back-in-stock notifications, and fulfillment status updates) built on reliable webhook infrastructure.

  • 05

    Webhooks, middleware, and connectors

    Custom webhook handlers, transformation middleware, and API connectors. The plumbing that moves data reliably between systems that don't speak each other's language natively.

  • 06

    Integration audits

    A scoped review of an existing integration that's causing problems: failure log analysis, retry behavior review, data contract verification, and a written report with prioritized recommendations.

The process

Map. Build. Deploy.

01 Map

Document the data contract.

We document every data entity that moves between systems, the direction it flows, the transform rules, and the error scenarios. This becomes the spec for the build.

02 Build

Live test data, full round-trip.

Integration built and tested against sandbox environments for both systems, not mocked data. We verify the full round-trip, including failure and retry scenarios, before go-live.

03 Deploy

Monitoring on day one.

Go-live with monitoring dashboards, alerting thresholds set, and a runbook documenting the integration's behavior and how to troubleshoot common failures.

What we aim for

Outcomes we target.

01

Integration reliability

Retries, dead-letter queues, and alerting so the integration fails loudly, not silently. Your team should know about a problem before a customer does.

02

Manual work eliminated

Every integration replaces a human-in-the-loop data transfer. The measure of success is the number of times your team has to touch the data manually after go-live.

03

Observable systems

Monitoring dashboards, structured logs, and alerting thresholds, so your operations team can see the state of every sync without reading code.

Outcomes vary by project scope and the quality of the APIs being integrated. Metrics referenced elsewhere on this site are from individual engagements and are not guarantees of future results.

Prior commerce engineering

Systems that stayed in sync.

The work below is prior employment and contracting, not Salt & Scale case studies, but the experience that informs every integration engagement today.

  • Hive Brands

    Microservices suite for promotions and operations integration. 99.9% sync reliability across promotional logic, order pipelines, and operational systems.

  • PAX Labs

    Custom OMS in PHP and MySQL on the backend of PAX Labs' headless Shopify contract — the order operations layer that connected commerce to fulfillment reliably at scale.

  • Sanrio (via Corra)

    Laravel API layer integrating Shopify Plus, Magento, and back-office systems across multiple regional brands and currencies.

Common questions

Things people ask first.

If your question isn't here, send a note. Most replies come back the same business day.

  • What systems do you integrate with?
    We've built integrations with NetSuite, SAP, Salesforce, HubSpot, ShipBob, ShipStation, Klaviyo, and custom ERP and WMS systems. If the system has a documented API, we can integrate with it. If it doesn't, or if the API is underdocumented, we'll tell you upfront and help you evaluate alternatives.
  • What's the difference between real-time and batch sync?
    Real-time sync uses webhooks: when something changes in one system, a webhook fires and the other system is updated within seconds. Batch sync runs on a schedule (every 15 minutes, hourly, nightly) and reconciles data in bulk. Real-time is better for order status and inventory. Batch is more reliable for large catalog syncs and financial reporting where occasional lag is acceptable. Most production integrations use both.
  • How do you handle integration failures?
    Every integration we build includes retry logic with exponential backoff, dead-letter queues for failed messages, and alerting when failure rates exceed a threshold. We instrument the pipeline so failures show up in your monitoring dashboard, not in a customer complaint two days later. We also document common failure modes and how to resolve them.
  • Can you audit an existing integration that's causing problems?
    Yes. A focused integration audit (reviewing the code, checking retry behavior, examining failure logs, and assessing the data contract between systems) is a scoped engagement we offer independently of a full rebuild. We'll give you a written report on what's breaking and why, with prioritized recommendations.

Let's fix the integration.

Tell us the systems involved, the data that needs to move, and what's currently failing or missing. We'll respond within one business day.

Start a project See all services