How to integrate NetSuite with Medusa

Does Medusa have a NetSuite connector?

Medusa has no first-party NetSuite connector and no NetSuite-specific guide. You integrate NetSuite by writing a custom Medusa module that calls NetSuite's APIs, then running it from workflows, subscribers, and scheduled jobs. The general Medusa ERP integration recipe shows each of these patterns with example code. Everything NetSuite-specific in this entry is Custom work.

Which NetSuite APIs to use from Medusa

NetSuite exposes three integration channels under SuiteTalk and SuiteScript. Oracle's guidance is to build new integrations on REST web services with OAuth 2.0.

To get NetSuite changes into Medusa as they happen, you deploy a user event script whose Copy to clipboardafterSubmit entry point sends the record to a Medusa API route with the Copy to clipboardN/https module. Otherwise, you poll NetSuite from a Medusa scheduled job. Concurrency limits are shared across SOAP, REST, and RESTlets, so batch calls where you can.

How NetSuite data maps to Medusa

Each row is a sync you build in your NetSuite module. The Medusa side of every row uses native commerce modules.

Store the NetSuite internal ID on the Medusa record, for example in Copy to clipboardmetadata or the product's Copy to clipboardexternal_id, so later syncs can match records.

Real-time vs scheduled sync with NetSuite

Medusa supports both timing models with built-in tools. Choose per data type.

• Real-time, Medusa to NetSuite. A subscriber on Copy to clipboardorder.placed runs a workflow that creates the sales order in NetSuite.
• Real-time, inside checkout. A workflow hook on Copy to clipboardaddToCartWorkflow checks stock or purchase rules in NetSuite before an item enters the cart.
• Real-time, NetSuite to Medusa. A user event script posts to a custom Medusa API route that runs an update workflow.
• Scheduled. A scheduled job pulls the item catalog or price levels on a cron schedule.

Code skeleton: push Medusa orders to NetSuite

A Medusa workflow step can define a compensation function that runs if a later step fails. Here the compensation deletes the NetSuite sales order, so the two systems do not drift apart. Copy to clipboardcreateSalesOrder and Copy to clipboarddeleteSalesOrder are methods you write in your own NetSuite module, for example against the REST Copy to clipboardsalesOrder record.

123456789101112131415
import { createStep, StepResponse } from "@medusajs/framework/workflows-sdk"
import { OrderDTO } from "@medusajs/framework/types"

export const createNetSuiteOrderStep = createStep(
  "create-netsuite-order",
  async ({ order }: { order: OrderDTO }, { container }) => {
    const netsuite = container.resolve("netsuite")
    const id = await netsuite.createSalesOrder(order)
    return new StepResponse(id, id)
  },
  async (id, { container }) => {
    if (!id) return
    await container.resolve("netsuite").deleteSalesOrder(id)
  }
)

Run this step in a workflow triggered by an Copy to clipboardorder.placed subscriber, as in the ERP recipe's order sync section. Learn more about compensation functions.

How Shopify and other platforms connect to NetSuite

Oracle's NetSuite Connector is a prebuilt integration for a fixed list of storefronts. Medusa is not on that list, so Medusa projects use custom code or an iPaaS tool.

When Medusa is not the right choice for NetSuite

• You run a standard store on Shopify, BigCommerce, Magento 2, or WooCommerce, and NetSuite Connector covers your order, item, and fulfillment syncs. A prebuilt connector is less work than a custom module.
• You have no developer to own the integration. A Medusa NetSuite integration is TypeScript code you maintain through NetSuite releases.

Medusa fits when NetSuite holds rules the storefront must enforce during checkout, such as customer-specific prices or purchase restrictions, or when you need flows a connector's sync options do not cover.