Skip to content

05 — Systems

Every system makes sense on its own. The difficulty lives in the gaps.

ERP, inventory, CRM, fulfillment, wholesale and reporting were each chosen for good reasons. The trouble starts where they meet: two systems disagree about stock, an order status is technically correct and practically wrong, and someone is reconciling it all in a spreadsheet.

We design and build those connections, decide what should be the source of truth, and make the resulting data usable by the people who need it.

  • ERP integration
  • Inventory & fulfillment
  • CRM
  • APIs & middleware

Method

Ownership before plumbing

Most failed integrations are not technical failures. They are unresolved disagreements about which system is right, made permanent in code.

So we settle that first — per data domain, in writing — then design for the unglamorous parts: timing, retries, partial failures and who finds out when something breaks at 2am.

Decide ownership before you connect anything
  • ShopifyownsStorefront, orders, customers
  • ERPownsCosts, purchasing, financial truth
  • Inventory / 3PLownsStock position and fulfillment status
  • CRM / emailownsContact record and lifecycle state
  • ReportingownsNothing — it reads from everything

When does it move?

What happens on failure?

Who needs to know?

Your tech stack isn't your eCommerce strategy — but it will happily limit it.

What we connect

  • ERP systems
  • Inventory management
  • 3PL & fulfillment
  • CRM and email platforms
  • Wholesale & B2B systems
  • Subscription platforms
  • Reporting and BI
  • Custom middleware
  • Shopify Admin & Storefront APIs
  • Webhooks and event handling
  • Data migration & backfill
  • Monitoring and alerting

Proof

Complex commerce, connected

ROAM Adventure Co.

A wholesale portal built alongside direct-to-consumer operations, plus a platform migration — the kind of work where the storefront is only part of the system.

  • Wholesale portal
  • Migration
  • Development

Wulf's Fish

Extensive custom development across five years for a business whose operational constraints have to be reflected accurately in the buying experience.

  • Custom development
  • Store management

Systems that don't agree with each other?

Describe the disagreement. We've almost certainly seen its cousin.