Other
NetSuite 2026.1
2026-04-20

NetSuite Connector Adds Loop Returns Integration and Outlook Add-in

NetSuite Connector gains a Loop Returns connector that auto-creates Return Authorizations, Item Receipts, and Cash Refunds from Shopify/Loop Returns, plus a new Outlook add-in for syncing emails and events to NetSuite records.

Affects:NetSuite ConnectorReturn AuthorizationItem ReceiptCash RefundMicrosoft Outlook Add-in

What changed

Loop Returns Connector

A new Loop Returns connector is available within NetSuite Connector. It bridges the Shopify → Loop Returns → NetSuite pipeline for handling product returns, refunds, and exchanges.

When a return or refund action occurs in Shopify/Loop Returns, the connector automatically creates the corresponding NetSuite transaction records:

  • Return Authorization – initiated when a return is requested.
  • Item Receipt – created when returned goods are received.
  • Cash Refund – generated when a refund is processed.

The goal is to eliminate manual data entry and keep NetSuite in sync with Shopify and Loop Returns without custom scripting or middleware.

Important: This is not a self-service activation. You must contact your NetSuite Account Manager to have the Loop Returns connector added to your NetSuite Connector account.

NetSuite Connector for Outlook

A new Microsoft Outlook add-in lets users sync emails and calendar events from Outlook directly to matching NetSuite records (likely entity, transaction, or case records, though Oracle does not specify the exact record types in this note).

This is a separate install — it requires deploying the add-in within your Microsoft 365 / Outlook environment.

What to do

  1. Loop Returns connector: If your organization uses Shopify with Loop Returns for handling returns and refunds, contact your NetSuite Account Manager to enable the connector. Before activation, review your existing return/refund workflows and any custom scripts on Return Authorization, Item Receipt, or Cash Refund records — the connector will create these records automatically, and any beforeSubmit or afterSubmit User Event scripts deployed on those record types will fire on connector-created records.
  2. Outlook add-in: Install the Microsoft Outlook add-in per the Managing NetSuite Connector for Outlook documentation. Coordinate with your Microsoft 365 admin if centralized deployment is required. Verify that the NetSuite roles assigned to Outlook users have appropriate permissions for the records they will be syncing to.
  3. Testing: For both features, test in a Sandbox account first. Confirm that connector-created records respect your approval workflows, saved searches, and any SuiteFlow processes triggered by record creation.

Gaps in the release note

Oracle does not specify:

  • Which NetSuite record types the Outlook add-in can sync to (Contact, Customer, Case, Opportunity, etc.).
  • Whether the Loop Returns connector supports custom field mapping or is limited to standard fields.
  • SuiteScript or REST API implications — it is unclear whether these connectors expose new integration endpoints or simply use existing record APIs under the hood.
  • Any new roles, permissions, or feature prerequisites beyond contacting your Account Manager.

Check the Managing NetSuite Connector for Outlook help topic and your Account Manager for specifics before rolling out to production.