Getting Started with E-commerce Integrations

An overview of how to connect and automate your e-commerce operations with Spojit.

What This Integration Does

Most e-commerce stacks end up as a half-dozen disconnected systems: a storefront (Shopify, WooCommerce, BigCommerce, Adobe Commerce), an ERP or accounting system (NetSuite), a shipping carrier, a marketing platform (Klaviyo), and a warehouse database. Each one knows part of the truth about an order. Spojit's job is to make those systems behave like one system - orders flow downstream, inventory flows upstream, customers stay in sync, and humans don't paste CSVs.

This guide is a map of the territory rather than a single recipe. Each section below names a category of integration, lists the Spojit connectors and tools involved, and points at the more focused tutorials in this collection. Use the "Where to Start" section at the bottom to pick a concrete workflow once you know which pattern matches your business.

Prerequisites

  • A Spojit workspace with at least one workflow created.
  • A storefront connection: shopify, woocommerce, bigcommerce, adobe-commerce-rest, or adobe-commerce-graphql.
  • For order routing to ERP: a netsuite connection with REST + SuiteQL access.
  • For shipping: a shipstation, shippit, smartfreight, or dhl-express connection.
  • For marketing: a klaviyo connection. For payments: a stripe connection.

Step 1: Order Management - Storefront to ERP

The most common e-commerce workflow. A Trigger (webhook or scheduled poll) fires when a new order is created in shopify (list-orders or webhook payload). A Transform node reshapes the order into your ERP's customer/order schema. A Connector node calls netsuite upsert-record to land the customer and create-record for the sales order. A Condition node checks the create result and routes failures to a Slack alert. The same shape works for WooCommerce, BigCommerce, and Adobe Commerce as the source.

Step 2: Inventory - Multi-Store and Warehouse Sync

Inventory drift is the second-biggest source of e-commerce pain. Build a scheduled workflow that fetches stock levels from your source of truth (a warehouse database via mysql execute-query, or NetSuite via run-suiteql), then fans out via a Parallel node to update each storefront. Use shopify adjust-inventory and get-inventory-levels, woocommerce update-product, and bigcommerce update-product. Add a Condition node that compares before/after stock and posts a slack send-message alert when any SKU drops below a threshold.

Step 3: Shipping and Fulfillment

Once an order lands in the ERP, fulfillment is a fan-out problem. A Condition node routes by destination country, weight, or service level into a shipstation create-order call, a shippit create-order + book-order pair, a smartfreight import-consignment, or a dhl-express create-shipment. After booking, fetch the tracking number and call back to the storefront (shopify update-order) to attach it. Finally, send a customer notification through resend send-email or klaviyo create-event.

Step 4: Customer Data and Marketing

Customer profiles tend to scatter across the storefront, the ERP, and the marketing platform. Build a one-way sync from your storefront's list-customers tool into klaviyo create-profile / update-profile, plus add-profiles-to-list to drop new customers into the right segment list. For enrichment, query order history via shopify list-orders filtered by customer, aggregate with the math connector's sum and average, and write the rollup back to the Klaviyo profile. AI Agents can score and segment customers based on the enriched profile.

Step 5: AI-Enhanced Operations

Drop an AI Agent node into any of the above flows for tasks that need reasoning: generating product descriptions for shopify create-product calls, classifying incoming orders for fraud risk before they go to fulfillment, auto-tagging products with categories, or summarizing daily sales for an executive Slack digest. Use Structured Output so downstream nodes can read specific fields. See the Getting Started with AI-Powered Workflows tutorial for the AI patterns.

Step 6: Reporting and Reconciliation

Close the loop with scheduled reports. A daily Trigger fans out via Parallel to pull order counts from each storefront (list-orders with a date filter), payment totals from stripe list-charges, and shipment counts from shipstation list-shipments. A Transform node joins the rollups, the csv connector's from-json tool produces a CSV, and the ftp connector's upload-file tool drops it where finance picks it up. Mismatches between order count and shipment count get routed to a slack alert.

Tips

  • Webhooks beat polling for order events on Shopify, WooCommerce, and BigCommerce. Use Trigger node type "Webhook" and you'll cut latency from minutes to seconds.
  • Upsert, don't insert. Use NetSuite upsert-record keyed by the storefront order ID so reruns don't double-write.
  • Batch inventory updates. A single shopify raw-graphql mutation that touches 100 SKUs is far faster than 100 single-SKU calls.
  • Idempotency keys. Pass the storefront order ID into Stripe and ShipStation as the external reference - it makes reconciliation trivial later.

Common Pitfalls

  • Currency and tax rounding. Storefronts and ERPs round differently. Always store the storefront's totals verbatim in the ERP record, not your own re-computation.
  • Timezones on schedules. "Yesterday's orders" depends on which timezone yesterday is in. Pin a timezone in your trigger and use the date connector explicitly.
  • Storefront rate limits. Shopify's bucket algorithm and WooCommerce's REST limits will throttle a naive sync. Use the Loop node's concurrency cap.
  • Refunds and cancellations. These usually arrive as separate events, not edits to the original order. Make sure your ERP sync handles cancel-order and refund webhooks distinctly.

Testing

Pick a single SKU and a test customer, build one end-to-end flow (place a test order, watch it land in NetSuite, watch a shipping label generate, watch the tracking number appear back on the storefront), and only then turn on the broader sync. Always run new e-commerce workflows against a sandbox storefront first if your platform offers one.

Where to Start

  1. Set up your connections to the platforms you use.
  2. Pick a specific integration from this collection that matches your needs.
  3. Follow the step-by-step guide to build your first e-commerce workflow.

Learn More

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.