--- title: "Sync Front and NetSuite" description: "Sync Front and NetSuite so customers, sales orders, and invoice status sit next to the conversation, and address or contact fixes flow back into the ERP." canonical: https://www.stacksync.com/blog/sync-front-and-netsuite last_modified: 2026-07-21 --- # Answering Billing Questions Without Leaving the Inbox > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md A guide to connecting Front with NetSuite so the person writing the reply can see the customer, their open orders, and their invoice status without opening the ERP. It covers what to surface, how the two connect, which fields stay read-only, and what flows back. Author Ignacio Malpartida · GTM Engineer Published July 21, 2026 Read time 7 min read APP TIPS Look at what actually arrives in a shared inbox and a pattern shows up fast. Where is my order. Why was I invoiced twice. Has the credit been applied. Can you resend the receipt. Almost none of it can be answered from the message itself, because the answer lives in the ERP. So the person reading it in Front opens NetSuite, searches for the customer, reads two or three records, goes back to the inbox, and writes the reply. It works, and it costs a few minutes every single time, on the questions that arrive most. ![What NetSuite adds to a reply in Front: who the customer is, what they bought, what they owe, and a path to write corrections back](https://www.stacksync.com/images/blog-highlights/fr-netsuite-summary.webp) Syncing Front and NetSuite closes that gap in both directions. Here is what to surface, what to keep locked, and what should flow back. For the wider picture see the guide to an [enterprise iPaaS for Front](https://www.stacksync.com/blog/enterprise-grade-ipaas-for-front). ## The answer usually lives in the ERP A shared inbox is where customers reach you, but the ERP is where the facts are. Order numbers, ship dates, invoice status, credit terms, and balances are all in NetSuite, and none of them are in the email. That is the whole reason for the tab switching. There is a second cost that is easier to miss. When the answer is expensive to find, people guess, or they escalate to finance for something a two-line lookup would have settled. Putting the record next to the conversation removes both the delay and the guess. ## How the two connect The connection is a sync engine sitting between the two systems, not a plugin bolted onto either. It matches the sender to a NetSuite customer, decides which fields move in which direction, and keeps both sides from overwriting each other. ![Front and NetSuite connected by a two-way sync engine that matches customers on email and domain, keeps finance fields read-only, and tracks the origin of every write](https://www.stacksync.com/images/blog-diagrams/fr-netsuite-concept.webp) *The person writing the reply sees the order. Finance still owns the numbers.* Read-only fields are the part worth designing carefully. Invoice amounts, balances, and posted transactions should never be editable from an inbox, because the ERP has to stay the system of record for anything an auditor will look at. Contact names, billing contacts, and addresses are a different matter: those are usually wrong in the ERP and right in the email. ## What lands next to the conversation Once the match is made, the useful subset of the ERP travels with the thread. Not the whole customer record, just the handful of facts that answer the questions people actually ask. ![NetSuite customer, order, and invoice data flowing through the sync engine into the Front conversation sidebar, with corrected contact details flowing back](https://www.stacksync.com/images/blog-diagrams-mermaid/fr-netsuite-topology.webp) *Customer, orders, and balance travel to the conversation. Corrections travel back.* The return path is what keeps the ERP clean over time. A customer replies from a new billing address or names a different accounts-payable contact, and that correction can be written into NetSuite from the conversation instead of becoming an internal request that waits three days. ## What syncs between Front and NetSuite A typical two-way sync keeps these in step, with direction controls that keep financial fields owned by NetSuite. | NetSuite | Front | Direction | | --- | --- | --- | | Customer record | Matched contact | Matched or created | | Billing contact and address | Contact details | Both ways | | Open sales orders | Conversation context | NetSuite to Front | | Invoice status and due date | Conversation context | NetSuite to Front | | Account balance | Conversation context | NetSuite to Front, read-only | | Support tag or case reference | Conversation tag | Both ways | Contact data is two-way because the inbox sees corrections first. Financial fields stay owned by NetSuite. ## One reply, no tab switching When Front and NetSuite are synced, the person answering has the order in front of them, the invoice status is current, and a correction they spot in the email lands in the ERP instead of in someone’s memory. The reply gets written once, with the right numbers in it. If sales also needs those conversations, pair this with [Front and Salesforce](https://www.stacksync.com/blog/how-to-sync-front-with-salesforce) or [Front and HubSpot](https://www.stacksync.com/blog/two-way-sync-solutions-front-hubspot) on the same engine. You can also look at the [Front connector](https://www.stacksync.com/connectors/front), or [book a demo](https://www.stacksync.com/book-a-demo) and we will match a real customer live. FAQ ## Frequently asked questions Can Front show NetSuite customer data? Yes. Once Front and NetSuite are synced, the sender is matched to a NetSuite customer on email and company domain, and their record, open sales orders, and invoice status can be shown next to the conversation the team is answering. Does the sync write back into NetSuite? For the fields you allow. Contact details, billing contacts, and addresses are commonly writable from the inbox, because that is where corrections show up first. Amounts, balances, and posted transactions stay read-only so the ERP remains the system of record. How is a sender matched to the right NetSuite customer? Exact email address first, then the company domain, then a review queue for anything unmatched. That layered order is what keeps a personal address or a new subdomain from creating a duplicate customer. Will this slow NetSuite down or hit its limits? No. Only changed fields are sent, and requests are queued, ordered, and retried with backoff, so the sync stays inside NetSuite’s governance limits instead of hammering it with full-record reads. Can Front feed a CRM at the same time? Yes. The same Front connection can push conversations into a CRM while reading customer and invoice data from NetSuite. Each pair is configured separately but runs on one engine, so adding the second does not disturb the first. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector Front integrations](https://www.stacksync.com/connectors/front) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips AI Agents for Beverage Brands: Investigate Distributor Delivery Claims 5 min read read](https://www.stacksync.com/blog/ai-agents-for-beverage-brands-investigate-distributor-delivery-claims) [App tips AI Agents for CPG Order-to-Cash: Investigate Order and Payment Exceptions 5 min read read](https://www.stacksync.com/blog/ai-agents-for-cpg-order-to-cash-investigate-order-and-payment-exceptions) [App tips AI Agents for Household Brands: Investigate Refill and Case-Quantity Disputes 5 min read read](https://www.stacksync.com/blog/ai-agents-for-household-brands-investigate-refill-and-case-quantity-disputes) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)