.png)
NetSuite SuiteCommerce Integration Guide
NetSuite SuiteCommerce integrates storefront commerce with NetSuite records through REST Web Services, SOAP, RESTlets, SuiteScript, commerce services, and scheduled processing.
NetSuite SuiteCommerce integration options at a glance
NetSuite SuiteCommerce integrations can use NetSuite REST Web Services for supported record operations, SuiteTalk SOAP Web Services for established or WSDL-based integrations, and custom RESTlets for SuiteScript business logic. SuiteCommerce commerce services support storefront functions such as products, carts, checkout, customer sessions, and order submission, although exact contracts vary by edition and implementation. NetSuite also supports CSV import and export, asynchronous and scheduled processing, File Cabinet operations, and read-only SuiteAnalytics Connect access. Martini can authenticate with OAuth 2.0 or token-based credentials, orchestrate calls in workflows, transform payloads, expose controlled APIs, and coordinate scheduled or event-assisted synchronization.
| Integration point | Supported by NetSuite SuiteCommerce? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | NetSuite REST Web Services provide record-oriented create, read, update, and delete operations for supported Customers, Items, Sales Orders, Invoices, and other records. RESTlets provide custom HTTP operations implemented with SuiteScript. | Martini can consume REST endpoints from workflows, manage authentication, map JSON payloads, apply business rules, and expose separate APIs for downstream systems. |
| SOAP APIs | Yes | SuiteTalk SOAP Web Services support WSDL-defined record and business operations and remain relevant for existing integrations or operations better supported through SOAP. | Martini can consume SOAP services, handle XML payloads, transform responses, and route SOAP faults through workflow error handling. |
| Webhooks and outbound callbacks | Limited | Selected record changes can be detected with SuiteScript User Events or other custom logic that makes outbound HTTP requests. A universal webhook subscription model for all NetSuite or SuiteCommerce events was not confirmed. | Martini can expose an API or webhook workflow to receive implementation-specific callbacks, then validate, deduplicate, and reconcile notifications. |
| Bulk, asynchronous, and batch processing | Yes | CSV import and export, SOAP asynchronous requests, Map/Reduce, scheduled scripts, SuiteCloud processing, and related mechanisms support high-volume or background workloads. | Martini can orchestrate batches, transform files, schedule extraction and loading, track checkpoints, and separate transactional processing from bulk workloads. |
| File and attachment APIs | Yes | File Cabinet operations support imports, exports, product assets, documents, and files associated with NetSuite records, subject to permissions and file constraints. | Martini can move files through workflows, transform metadata, call file endpoints, and coordinate file delivery with record updates. |
| Database and analytics access | Limited | SuiteAnalytics Connect provides read-only access for reporting and extraction. It is not direct transactional database access and should not replace APIs for writes. | Martini can orchestrate read-only extraction through supported database connectivity and deliver transformed data to analytics or data platforms. |
| Authentication | Yes | NetSuite supports OAuth 2.0, token-based authentication using OAuth 1.0 signing, roles, permissions, integration records, and selected legacy login-based mechanisms. | Martini can store credentials and secrets in protected environment configuration and use the required authentication configuration for each API or RESTlet. |
| Commerce APIs and SuiteCommerce services | Limited | SuiteCommerce implementations expose services for product browsing, customer sessions, cart behavior, checkout, and order submission, but endpoint structure depends on edition, release, extensions, and account configuration. | Martini can consume confirmed commerce endpoints and map storefront concepts such as carts and checkout sessions to external or NetSuite models without assuming a uniform contract. |
How NetSuite SuiteCommerce exposes data and business events
NetSuite REST APIs
NetSuite REST Web Services provide record-oriented access for supported objects and operations. They are generally the preferred standards-based option for new server-to-server integrations when the required record functionality is available.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates to the confirmed REST endpoint, retrieves or receives the current NetSuite resource, maps it to a canonical model, applies validation and business rules, and writes the result to the target system. Pagination, rate limits, checkpoints, and idempotency are handled explicitly.
Implementation sequence
SuiteTalk SOAP Web Services
SuiteTalk SOAP exposes WSDL-defined NetSuite records and operations. It remains relevant for existing integrations, generated clients, asynchronous requests, and operations that are better supported through SOAP.
Martini implementation pattern
Martini implementation pattern: a workflow consumes the SOAP service, converts XML into the internal model, handles SOAP faults and NetSuite-specific errors, and transforms outbound data back into the required XML contract.
Implementation sequence
NetSuite RESTlets and SuiteScript
RESTlets are custom HTTP endpoints implemented with SuiteScript, while SuiteScript can process records, detect selected events, run scheduled or Map/Reduce jobs, and make outbound HTTP requests. Contracts and behavior are implementation-specific.
Martini implementation pattern
Martini implementation pattern: Martini consumes the RESTlet or receives a callback from custom SuiteScript through an API workflow. The integration treats the custom contract as versioned, validates authorization and payload shape, and uses reconciliation when an event or outbound call is missed.
Implementation sequence
SuiteCommerce services
SuiteCommerce and SuiteCommerce Advanced implementations use commerce services and extensions for product browsing, customer sessions, carts, checkout, and order submission. Exact endpoints vary by edition, account, release, and customization.
Martini implementation pattern
Martini implementation pattern: Martini consumes only the storefront services confirmed for the target implementation, then maps storefront concepts to NetSuite records or external channel models. It avoids assuming that a cart, checkout session, shopper, or product payload maps one-to-one to a standard record.
Implementation sequence
Bulk and asynchronous processing
NetSuite supports CSV import and export, SOAP asynchronous requests, Map/Reduce, scheduled scripts, SuiteCloud processing, and SuiteAnalytics Connect for appropriate workloads. The correct method depends on volume and whether the operation is transactional or analytical.
Martini implementation pattern
Martini implementation pattern: a scheduled or queue-driven workflow divides data into controlled batches, transforms each batch, records checkpoints, and routes transient failures for retry. Large reporting extracts can use read-only analytics access rather than repeated transactional API calls.
Implementation sequence
Common NetSuite SuiteCommerce integration patterns
Pattern 1: Sync SuiteCommerce orders to fulfillment
When to use this pattern
Use this pattern when storefront Sales Orders must be sent to a warehouse or shipping platform and shipment confirmations must return to NetSuite. It supports status validation, idempotent submission, partial fulfillment, and tracking updates.
Integration direction
Example Mapping
| NetSuite SuiteCommerce Field | Canonical Field | Target Field |
|---|---|---|
| internalId | sourceOrderId | orderReference |
| entity | customerId | customerReference |
| itemList.item | lineItems[].sku | items[].sku |
| quantity | lineItems[].quantity | items[].quantity |
Martini implementation pattern
A scheduled workflow or implementation-specific callback retrieves eligible Sales Orders, validates payment and fulfillment status, maps lines and addresses, and submits the order with a stable source identifier. Martini records the cross-reference, retries transient failures with backoff, and creates or updates Item Fulfillments when shipment and tracking data returns.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- business rules
- error handling
Pattern 2: Synchronize products and inventory
When to use this pattern
Use this pattern when SuiteCommerce or another channel needs current product definitions, item attributes, and location-aware availability from NetSuite. It is appropriate for scheduled synchronization where inventory reservations and channel allocation rules must be applied.
Integration direction
Example Mapping
| NetSuite SuiteCommerce Field | Canonical Field | Target Field |
|---|---|---|
| itemId | productId | product.id |
| displayName | productName | product.title |
| locations[].available | availableQuantity | inventory.quantity |
| itemStatus | publicationStatus | product.status |
Martini implementation pattern
Martini retrieves changed Items and Inventory Items using a high-water mark, combines location values, applies sellable-inventory and publication rules, and publishes a normalized product model. The workflow persists the cursor, handles pagination, and records rejected items separately from transport failures.
Martini capabilities used
- workflows
- scheduled synchronization
- API consumption
- data mapping
- transformations
- checkpointing
- error handling
Pattern 3: Synchronize customers and commerce transactions with Salesforce
When to use this pattern
Use this pattern when Salesforce manages customer engagement while NetSuite remains authoritative for commerce transactions, invoices, or financial status. Ownership rules are required for email, addresses, account status, and tax information.
Integration direction
Example Mapping
| NetSuite SuiteCommerce Field | Canonical Field | Target Field |
|---|---|---|
| Account.Id | customerExternalId | externalId |
| Account.Name | customerName | companyName |
| SalesOrder.tranId | orderNumber | Order.OrderNumber |
| Invoice.total | invoiceAmount | Invoice.Amount |
Martini implementation pattern
Martini receives or schedules Salesforce changes, matches them to NetSuite Customers using stable identifiers, and applies field ownership rules before writing. Separate workflows publish Sales Orders and Invoices to Salesforce, classify duplicate and permission errors, and run reconciliation for missed events or status changes.
Martini capabilities used
- API consumption
- workflow orchestration
- data mapping
- business rules
- idempotency
- reconciliation
- error handling
Pattern 4: Export commerce data for analytics
When to use this pattern
Use this pattern for recurring extraction of Sales Orders, Invoices, Customers, Items, and fulfillment data into a reporting or data platform. SuiteAnalytics Connect may be more suitable for large read-only reporting workloads than repeated transactional requests.
Integration direction
Example Mapping
| NetSuite SuiteCommerce Field | Canonical Field | Target Field |
|---|---|---|
| SalesOrder.internalId | orderId | commerce_order_id |
| Invoice.tranDate | invoiceDate | invoice_date |
| Customer.email | customerEmail | customer_email |
| Item.itemId | sku | product_sku |
Martini implementation pattern
A scheduled Martini workflow selects the appropriate REST, SOAP, SuiteQL, or SuiteAnalytics Connect source, retrieves bounded pages or batches, normalizes records, and writes them to the target API or file destination. It stores a high-water mark, validates record counts, and retries only safe operations.
Martini capabilities used
- scheduling
- workflow orchestration
- API consumption
- database connectivity
- data mapping
- file processing
- monitoring
Applications commonly integrated with NetSuite SuiteCommerce
NetSuite SuiteCommerce commonly participates in multi-system commerce, fulfillment, tax, customer-service, and enterprise-data architectures. The exact integration direction depends on which system owns each business object and on the customer’s NetSuite account configuration.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize customers, accounts, commerce orders, and financial status between customer engagement processes and NetSuite transaction data. | Salesforce → Martini → NetSuite SuiteCommerce | Use REST APIs or SOAP services on both sides, match Customers with durable cross-references, map orders and invoices, and route validation or duplicate conflicts for review. |
| Shopify | Coordinate products, inventory, customers, and orders when an organization operates SuiteCommerce and Shopify channels. | NetSuite SuiteCommerce → Martini → Shopify | Schedule item and inventory extraction from NetSuite, normalize product and availability models, and process inbound Shopify orders with idempotency checks before creating Sales Orders. |
| Adobe Commerce | Synchronize catalog, inventory, customers, and orders where Adobe Commerce and SuiteCommerce coexist or NetSuite acts as the ERP backend. | Adobe Commerce → Martini → NetSuite SuiteCommerce | Expose or consume REST APIs, map commerce products to Items and orders to Sales Orders, and use scheduled reconciliation for missed updates and partial fulfillment. |
| Amazon | Exchange product listings, inventory, orders, and fulfillment information for marketplace operations. | NetSuite SuiteCommerce → Martini → Amazon | Publish approved item and inventory data, retrieve marketplace orders, apply channel allocation rules, and write fulfillment and tracking updates back to the appropriate NetSuite records. |
| Avalara | Send transaction information for tax calculation and reconcile tax responses with SuiteCommerce transactions and NetSuite invoices. | NetSuite SuiteCommerce → Martini → Avalara | Validate addresses and transaction lines, call the tax API from a workflow, map the response to transaction tax fields, and distinguish transient failures from tax-validation errors. |
| ShipStation | Send commerce orders for shipment and return tracking and shipment status to NetSuite. | NetSuite SuiteCommerce → Martini → ShipStation | Retrieve eligible Sales Orders, submit fulfillment requests using a stable source identifier, poll or receive shipment updates, and create or update Item Fulfillments without duplicating shipments. |
| Zendesk | Provide support agents with customer, order, invoice, and shipment context from SuiteCommerce and NetSuite. | NetSuite SuiteCommerce → Martini → Zendesk | Publish selected Customers, Sales Orders, Invoices, and Item Fulfillments to Zendesk, apply field-level filtering, and optionally route approved support updates back through controlled APIs. |
| Workday | Exchange selected enterprise, financial, supplier, or workforce-related data where NetSuite and Workday coexist. | Workday → Martini → NetSuite SuiteCommerce | Use scheduled workflows for domain-specific extracts and loads, map only agreed business objects, validate ownership boundaries, and retain reconciliation results for each batch. |
How to build a NetSuite SuiteCommerce integration in Martini
Objective
Establish the NetSuite account, edition, roles, permissions, endpoints, and environment-specific contract before implementation.
Instructions in Martini
- Confirm whether REST Web Services, SOAP, RESTlets, SuiteCommerce services, files, or analytics access is required
- Create the NetSuite integration record and least-privilege role
- Configure OAuth 2.0 or token-based authentication in protected Martini environment configuration
- Confirm sandbox and production endpoint differences
Objective
Select a trigger that matches the event coverage and reliability requirements of the integration.
Instructions in Martini
- Use a scheduled workflow for polling and incremental synchronization
- Use a Martini API for selected SuiteScript outbound callbacks
- Use a RESTlet when custom NetSuite business logic is required
- Document which record operations and status transitions are in scope
Objective
Retrieve authoritative NetSuite or SuiteCommerce data while accounting for pagination, filters, and implementation-specific payloads.
Instructions in Martini
- Use REST Web Services for supported record operations
- Use SOAP when the existing contract or required operation depends on SuiteTalk
- Retrieve current records after receiving an incomplete event notification
- Persist a cursor, high-water mark, or batch checkpoint
Objective
Coordinate calls, transformations, business rules, and downstream writes in a maintainable Martini workflow.
Instructions in Martini
- Separate extraction, transformation, validation, and delivery stages
- Use reusable workflow logic for common authentication and error handling
- Queue or batch high-volume work when synchronous calls would exceed account limits
- Correlate each transaction with its source identifier
Objective
Translate SuiteCommerce concepts and NetSuite records into the target application’s model without assuming one-to-one object equivalence.
Instructions in Martini
- Map Customers, Items, Sales Orders, Invoices, Inventory Items, and Item Fulfillments explicitly
- Distinguish carts, checkout sessions, shoppers, and products from standard NetSuite records
- Transform JSON, XML, CSV, or file payloads as required
- Version mappings for custom fields and account-specific extensions
Objective
Enforce ownership, validation, status, tax, inventory, and duplicate-prevention rules before writing data.
Instructions in Martini
- Validate addresses, payment state, item quantities, statuses, and required identifiers
- Use external IDs or durable cross-references for idempotency
- Handle cancellations, voids, refunds, and partial fulfillment explicitly
- Reject invalid data without treating it as a transient transport failure
Common NetSuite SuiteCommerce data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Customers | Shopper or account information exchanged between the storefront, NetSuite, Salesforce, support platforms, and other customer systems. | Salesforce, Zendesk, Shopify, Adobe Commerce | Martini maps customer identifiers, addresses, status, and ownership fields, applies duplicate-matching rules, and stores a durable cross-reference. |
| Items | Products and sellable item definitions used for catalog publication, pricing, availability, and channel synchronization. | SuiteCommerce, Shopify, Adobe Commerce, Amazon | Martini filters item status and modification time, maps item types and custom fields, and transforms the result into each channel’s product model. |
| Sales Orders | Commerce transactions created from storefront orders and processed for fulfillment, invoicing, cancellation, or refund. | ShipStation, Salesforce, Avalara, Adobe Commerce | Martini validates customer, address, line, payment, and status data; uses external IDs or cross-references for idempotency; and routes failures for retry or reconciliation. |
| Invoices | Billing documents created from orders or fulfillment processes and shared with CRM, tax, finance, or reporting systems. | Salesforce, Avalara, analytics platforms, data warehouses | Martini retrieves or receives invoice changes, maps transaction and tax fields, distinguishes voids and adjustments, and delivers normalized financial data. |
| Inventory Items | Stock levels, locations, availability, and inventory attributes used to determine sellable quantities across channels. | SuiteCommerce, Shopify, Amazon, Adobe Commerce | Martini combines item and location data, applies reservation and channel-allocation rules, and publishes calculated availability on a schedule or through selected events. |
| Item Fulfillments | Shipment and tracking records used to communicate fulfillment progress and delivery information. | ShipStation, Salesforce, Zendesk, commerce channels | Martini handles split shipments and partial fulfillment, maps carrier and tracking data, and prevents duplicate fulfillment updates using transaction identifiers. |
Authentication and security considerations
Authentication and least privilege
NetSuite supports OAuth 2.0 and token-based authentication using integration records, roles, permissions, scopes, and account information. Login-based methods remain relevant to selected legacy services but are generally less suitable for new server-to-server designs.
- Use separate roles and credentials for sandbox and production.
- Grant only the Web Services, REST Web Services, record, File Cabinet, and other permissions required by the workflow.
- Store client secrets, token secrets, account identifiers, and other credentials in protected Martini environment configuration.
- Treat SuiteCommerce shopper sessions separately from administrative NetSuite web-service authentication.
- Validate and authorize custom RESTlet inputs rather than exposing unrestricted record access.
Operational considerations for NetSuite SuiteCommerce integrations
Design for account-specific behavior
SuiteCommerce behavior varies by edition, release, custom extensions, enabled features, installed bundles, custom fields, roles, and SuiteScript. Test against the target account and maintain versioned mappings.
Control volume and state
- Handle REST and SOAP pagination and persist a cursor or high-water mark.
- Use controlled concurrency, batching, queues, and exponential backoff for NetSuite limits and governance.
- Model authorization, approval, fulfillment, shipment, invoicing, cancellation, refund, and void states explicitly.
- Use external IDs or durable cross-references to make retries safe and prevent duplicate transactions.
- Use scheduled reconciliation to identify missed callbacks, partial processing, and downstream failures.
- Test custom fields, optional values, enumerations, file permissions, schema changes, and sandbox-to-production differences.
Why use Martini instead of scripts or point-to-point integrations?
Maintainable orchestration
Point-to-point scripts often combine authentication, mapping, retries, business rules, and monitoring in code that is difficult to reuse. Martini separates these concerns in workflows and APIs while retaining the option for custom logic when an integration requires it.
- Consume REST, SOAP, RESTlet, file, and supported database or analytics interfaces from one orchestration layer.
- Expose controlled APIs for downstream applications instead of distributing NetSuite credentials.
- Reuse mappings, validation, authentication configuration, and error-handling patterns.
- Support scheduled, event-assisted, batch, and API-led processing without changing the target contract.
- Centralize logging, retries, checkpoints, reconciliation, and deployment configuration.
Frequently asked questions
Integration can use NetSuite REST Web Services, SuiteTalk SOAP Web Services, custom RESTlets, SuiteScript-driven callbacks, SuiteCommerce services, scheduled processing, CSV import and export, File Cabinet operations, and read-only SuiteAnalytics Connect access. The suitable method depends on the account configuration, SuiteCommerce edition, records involved, transaction volume, and whether the requirement is transactional, event-assisted, batch, or analytical.
Yes. Martini can consume confirmed NetSuite REST and SOAP APIs, call custom RESTlets, receive selected SuiteScript-generated callbacks through a Martini API, run scheduled synchronization workflows, process files, and map SuiteCommerce or NetSuite data to external systems. No native Martini NetSuite SuiteCommerce connector is documented in the supplied materials.
No. A dedicated connector is not required. Martini can use NetSuite’s confirmed native REST Web Services, SuiteTalk SOAP services, RESTlets, SuiteCommerce endpoints, authentication methods, files, and scheduled or callback-based integration mechanisms.
Lonti does not charge an additional per-connector or per-vendor fee to integrate NetSuite SuiteCommerce with Martini. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from NetSuite, infrastructure providers, or other third-party systems based on subscription, usage, and deployment model.
REST Web Services are generally the first option for new record-oriented server-to-server integrations when the required records and operations are supported. SOAP remains relevant for existing SuiteTalk contracts, generated clients, asynchronous processing, or operations better supported through the SOAP model. RESTlets are appropriate when custom SuiteScript business logic is required.
Selected event-driven behavior can be implemented with SuiteScript User Events, scheduled or Map/Reduce processing, and outbound HTTP requests, but a universal webhook subscription model for every NetSuite or SuiteCommerce event was not confirmed. Martini can receive implementation-specific callbacks through an API and can supplement them with scheduled polling and reconciliation.
Martini can run real-time, callback-assisted, scheduled, or batch workflows. The workflow retrieves or receives data, uses internal IDs, external IDs, timestamps, or other agreed cursors, maps records such as Customers, Items, Sales Orders, Invoices, and Item Fulfillments, applies ownership and status rules, and writes the result to the target system. Pagination and reconciliation are designed into the synchronization.
Martini workflows can classify authentication, permission, validation, rate-limit, duplicate, and temporary service errors separately. Transient failures can be retried with controlled backoff, while non-idempotent transaction creation should not be blindly retried. Stable source identifiers, external IDs, and durable cross-references help prevent duplicate Sales Orders, Invoices, and Item Fulfillments.
Related Martini documentation
APIs
Transformation
Connect NetSuite SuiteCommerce with the rest of your enterprise
Use Martini to orchestrate NetSuite SuiteCommerce APIs, records, files, callbacks, and scheduled processes through maintainable workflows and controlled APIs.