An independent NetSuite Shopify agency: we configure Oracle’s connector or Celigo when they cover your flows, and build custom SuiteTalk REST and Shopify GraphQL integrations when they don’t.
California-based leadership · Serving US and international teams
Share your objects, volumes, and timing needs — we'll come back with a written scope.
Please share the systems and workflow—not credentials or customer records. We’ll confirm API access, scope and next steps.
Part of NVIDIA’s program for startups building with AI and accelerated computing.
About the program
Pravin’s experience includes Google and SmartBear. Sravan previously held leadership roles at JPMorgan Chase and First Republic Bank.
Meet the founders9110 Alcosta Blvd Ste H345, San Ramon, CA 94583
US-led delivery, with engineering in India. Supporting US and international organizations.Most brands that look for a Shopify NetSuite agency already have a sync that half works: orders reach NetSuite in 20-minute batches, stock lags a shipment by an hour, and finance ties out Shopify Payments payouts in a spreadsheet. The choice is between Oracle’s own NetSuite Connector, an iPaaS app such as Celigo, and a custom build on SuiteTalk REST and the Shopify GraphQL Admin API. AIONDATA is an independent consultancy, not an Oracle or Shopify partner, so we configure the connector or Celigo when they fit and build custom when they don’t.
These decisions shape the scope, cost and acceptance tests. The flows below describe possible implementation behavior, not a preinstalled connector or a guarantee for every product edition.
A Sales Order commits stock and leads to an Item Fulfillment, then an Invoice or Cash Sale; B2B orders on terms need an Invoice. Oracle’s B2B connector posts an invoice at order sync unless its PostCustomerDepositForShopifyB2B setting creates a Pending Approval sales order instead.
inventorySetQuantities writes available or on_hand as an absolute value. We send quantity available from each mapped NetSuite Location, minus a buffer, never on hand.
Shopify Plus includes nine expansion stores; Oracle’s connector needs a separate connector account per store. Each store maps to one subsidiary, Location and price level.
Oracle says to use OAuth 2.0 and that from 2027.1 no new TBA integrations can be created. The account concurrency limit (5 on Standard, 15 on Premium, 20 on Enterprise and Ultimate, plus 10 per SuiteCloud Plus license) is shared by every integration, so the integration record gets its own allocation.
Shopify exposes each ShopifyPaymentsPayout to apps with the read_shopify_payments_payouts scope. Oracle’s connector documents settlement syncs for Amazon, not Shopify, and Celigo sells payout import as an add-on.
Field mapping
The records, match keys and triggers most implementations start from. Your scope confirms each row against your editions, custom fields and business rules.
| Source | Target | Match key | Direction | Trigger | Notes |
|---|---|---|---|---|---|
| Inventory Item, Kit Item, matrix item | Product and ProductVariant | Item name or custom SKU field = variant SKU | NetSuite → Shopify | Scheduled delta on last modified date, plus on-demand resync | Web-sale items only; UPC, weight and base price mapped; matrix children become variants. |
| Item availability by Location | InventoryLevel per Location (inventorySetQuantities, name available) | Location internal id = Shopify Location id | NetSuite → Shopify | Every 5 to 15 minutes, plus after Item Fulfillments and Item Receipts | Quantity available minus a buffer; compareQuantity on; idempotency key per push. |
| Customer-specific pricing (price levels per Customer) | B2B price list on a catalog assigned to a company or company location | Customer internal id stored on the Shopify company | NetSuite → Shopify | Scheduled | Per-location assignment needs Plus. |
| Shopify Customer | Customer | Email, or Customer internal id stored on the Shopify customer | Shopify → NetSuite | CUSTOMERS_CREATE webhook or first paid order | Subsidiary chosen by store; internal id written back after the first order. |
| Shopify Company and company location | Customer (company) with sub-customers, terms and credit limit | Company external id = Customer internal id | NetSuite ↔ Shopify | COMPANIES_CREATE webhook; NetSuite terms changes on a schedule | New companies created in NetSuite after approval; terms mirrored. |
| Shopify Order (paid) | Sales Order | Shopify order id in a custom body field; existing-order check before create | Shopify → NetSuite | ORDERS_PAID webhook, plus a sweep on updated_at | Lines, shipping, discounts and tax mapped; Location from the fulfillment order. |
| Shopify payment transaction (sale or capture) | Customer Deposit on the Sales Order, applied to the Invoice or Cash Sale | Transaction id | Shopify → NetSuite | With the order, and on later captures | Each gateway maps to a clearing account; fees handled in payout reconciliation. |
| Item Fulfillment (shipped) | Fulfillment (fulfillmentCreate on the fulfillment orders) | Created-from Sales Order → Shopify order id | NetSuite → Shopify | On shipped status, polled every few minutes | Carrier and tracking from the package lines; partials supported. |
| Shopify Refund | Return Authorization, Credit Memo and Customer Refund | Refund id | Shopify → NetSuite | REFUNDS_CREATE webhook | Restocked lines create a Return Authorization first; shipping-only refunds create a Credit Memo; the gateway refund posts as a Customer Refund. |
| ShopifyPaymentsPayout | Bank deposit, fee journal and deposit application | Payout id; balance transaction → payment transaction id | Shopify → NetSuite | Daily, after each payout is issued | Net to the bank, fee to expense, lines matched to Customer Deposits and Refunds; needs read_shopify_payments_payouts. |
Download this mapping as a CSV worksheet · no email required
Options, cost and timeline
A prebuilt connector is sometimes enough. This comparison shows when each route fits, what it typically costs and how long it takes.
| Approach | Typical cost | Typical time | Fits when | Watch for |
|---|---|---|---|---|
| Oracle NetSuite Connector (formerly FarApp) | From about $199.92/month (B2C Standard) to about $916.58/month (B2B) (vendor list price on the Shopify App Store, Sep 2026), billed by Oracle NetSuite | Days to weeks to authorize the store, map fields and test | One store with standard flows, a 3PL, or Shopify B2B with invoice posting | Schedules of 20, 60 and 90 minutes unless the real-time option applies; one connector account per store; no transfer orders; no Shopify payout sync listed; B2B catalogs per company |
| Celigo Shopify – NetSuite Integration App | No public price; Celigo charges by endpoints and flows rather than transactions, with a 30-day free trial | Days to weeks for the standard flows, longer for custom mapping | Teams already on Celigo, orders imported as Sales Order, Cash Sale or Invoice, Shopify POS | Payout report import is an add-on; confirm which edition includes your flows and who watches the error queues |
| Custom integration (AIONDATA) | Quoted after a short discovery; hosting and support priced separately | Usually a few weeks for the standard flows; two to three months with several stores or subsidiaries, B2B pricing or payout reconciliation | Several subsidiaries or stores, kits, custom records, payout reconciliation, B2B terms from NetSuite, or owning the code | Someone must own monitoring, quarterly Shopify API versions and NetSuite release retests |
| Agency-run connector or iPaaS | Monthly fee quoted per scope, on top of the Oracle or Celigo subscription | Ongoing | Teams without integration staff who want one party to configure the tool, watch failures and fix mappings | Agree response times, who corrects NetSuite data errors, and your access to mappings and logs if you change agency |
Vendor prices are list prices from their public pages on the date shown; confirm current pricing with each vendor.
Most merchants create a Sales Order from the ORDERS_PAID webhook, because it commits stock in the shipping Location and gives the warehouse an Item Fulfillment to work from. The captured payment posts as a Customer Deposit against that Sales Order and is applied when the Item Fulfillment ships and the Invoice or Cash Sale is created; B2B orders on terms post an Invoice due under the Shopify payment terms. Payouts close the loop: each ShopifyPaymentsPayout carries its net amount, issue date, a fee summary and its balance transactions, so the integration posts a bank deposit, expenses the fees and matches each line to the Customer Deposit or Customer Refund in NetSuite.
Shopify says it does not guarantee webhook order, that delivery is not always guaranteed, and that an app should reconcile with periodic reads on updated_at; it retries a failed HTTPS delivery 8 times over 4 hours, then deletes a subscription created through the Admin API after 8 consecutive failures. The integration therefore stores every event, processes it once, writes inventory with compareQuantity and an idempotency key, and keeps failures visible until someone resolves them.
Both vendors ship official MCP servers, and neither sees the other system. Oracle’s NetSuite AI Connector Service is a remote MCP endpoint per account at no extra fee, with the free MCP Standard Tools SuiteApp for records, reports, saved searches and read-only SuiteQL under a non-administrator role; its custom tools cannot call external APIs. Shopify’s connector for Claude edits products, inventory and discount codes and reads orders at no extra Shopify fee, but cannot issue refunds, cancel orders or process returns. For questions that span both, we build a separate MCP server that calls SuiteTalk REST and the GraphQL Admin API: read tools first, and write tools such as releasing a held order behind the approval rules your team sets.
Technical details last reviewed September 30, 2026. Product capabilities and prices change; confirm them for your edition.
Sources: NetSuite Help: SuiteTalk REST Web Services overview · NetSuite Help: REST Web Services supported records · NetSuite Help: Token-based Authentication · NetSuite Help: OAuth 2.0 · NetSuite Help: Concurrency limits by service tier and SuiteCloud Plus · NetSuite Help: Concurrency limit per integration · NetSuite Help: The sandbox account · NetSuite Help: Data not copied to sandbox · NetSuite Help: AI Connector Service FAQ · NetSuite Help: Shopify Connector FAQ · NetSuite Help: NetSuite Connector sync frequency · NetSuite Help: Shopify B2B in NetSuite Connector · Shopify App Store: NetSuite ERP Connector · Shopify docs: API versioning · Shopify docs: Webhooks · Shopify docs: HTTPS webhook delivery · Shopify docs: WebhookSubscriptionTopic · Shopify docs: Bulk operations · Shopify docs: inventorySetQuantities · Shopify docs: fulfillmentCreate · Shopify docs: ShopifyPaymentsPayout · Shopify docs: REST Admin API (legacy) · Shopify docs: GraphQL Admin API rate limits · Shopify docs: Access scopes · Shopify Help Center: B2B features by plan · Shopify Help Center: Shopify Plus plan · Shopify Help Center: Shopify connector for Claude · Celigo: Shopify – NetSuite Integration App · Celigo: pricing
Outcomes
The connector for one store with standard flows and a 3PL: it maps orders, products, inventory, fulfillments and refunds out of the box. Celigo if you already run it or need its Sales Order, Cash Sale or Invoice import options. Custom for several subsidiaries or stores, kits, payout reconciliation, B2B terms owned by NetSuite, or to own the code.
The Shopify App Store listing for NetSuite ERP Connector shows B2C Standard from about $199.92/month, B2C Premium and POS at about $249.92/month and B2B at about $916.58/month (vendor list price, Sep 2026), billed by Oracle NetSuite. Celigo publishes no prices and charges per endpoint and flow, not per transaction.
Oracle’s help lists the connector’s standard schedules as orders every 20 minutes, products every 60 and fulfillments and refunds every 90. Our builds take orders from the ORDERS_PAID webhook and create the Sales Order within seconds to a few minutes, push availability every 5 to 15 minutes or after each Item Fulfillment, and sweep on updated_at because Shopify does not guarantee webhook delivery.
Every REST and RESTlet request counts against one account limit: 5 on the Standard tier, 15 on Premium, 20 on Enterprise and Ultimate, plus 10 per SuiteCloud Plus license, in sandbox as well as production. The integration record therefore gets its own allocation and catalog work is throttled.
Any plan works for D2C; API budget and B2B differ. Shopify grants 100 cost points per second on Standard plans, 200 on Advanced, 1,000 on Plus and 2,000 on enterprise, and caps B2B at three active catalogs below Plus. Plus includes nine expansion stores and lists from $2,500 per month on a one-year term.
A paid order becomes a Sales Order with the Shopify order id in a custom body field and the order name in the memo. The captured payment posts as a Customer Deposit, applied when the Invoice or Cash Sale is created after fulfillment. A refund with restocked lines creates a Return Authorization and Credit Memo, a refund without restock only the Credit Memo, and the money leaving the gateway posts as a Customer Refund.
Yes. NetSuite price levels and customer-specific prices map to Shopify price lists on catalogs, which attach to companies or, on Plus, to individual company locations. Terms on the company location (Net 7 to Net 90 or due on fulfillment) match the NetSuite customer terms.
The NetSuite item name or a custom SKU field equals the Shopify variant SKU; matrix items, Kit Items and units of measure are handled explicitly in the mapping workbook. Shopify customers match a Customer by email or by the NetSuite internal id stored on the Shopify customer after the first order.
It waits in a retry queue with the NetSuite message, and the named owner gets an alert. Technical errors retry with backoff; data errors wait for a fix and a replay. Every create first checks for a transaction with the same Shopify order id, so a replay cannot create a second Sales Order.
Yes, as an optional flow. Shopify’s Admin API returns each payout with its net amount, issue date, a fee summary and its balance transactions. We post the payout as a bank deposit, expense the fees and match the lines to the Customer Deposits and Refunds in NetSuite.
Each has an official MCP server that sees only its own data: Oracle’s NetSuite AI Connector Service with the free MCP Standard Tools gives Claude or ChatGPT records, saved searches, reports and read-only SuiteQL, and Shopify’s connector for Claude edits products and inventory and reads orders but cannot refund or cancel. To trace an order from checkout to payout, we build a separate MCP server that calls both APIs, since NetSuite custom tools cannot call external APIs, with writes behind your approval rules.
A standard items, availability, orders, customers, payments, fulfillments and refunds build usually takes a few weeks including sandbox testing. Several stores or subsidiaries, B2B price lists, kits, payout reconciliation and backfills extend that, typically to two to three months.
Other pairs involving NetSuite or Shopify.
The enquiry form is at the top of this page. Share your objects, volumes and timing needs and we'll come back with a written scope.
Go to the enquiry form