--- title: "Salesforce NetSuite sync for approved fence configurations" description: "Keep approved fence and gate configurations linked to the correct NetSuite order revision." canonical: https://www.stacksync.com/blog/fence-fabricators-and-installers-align-salesforce-approved-configurations-with-netsuite-sales-orders last_modified: 2026-09-18 --- # Fence Fabricators and Installers: Align Salesforce Approved Configurations With NetSuite Sales Orders > 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 Keep approved fence and gate configurations linked to the correct NetSuite order revision. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 5 min read DATA ENGINEERING ## The operating decision Fence fabricators and installers should connect Salesforce's approved commercial configuration to NetSuite order and project records through a versioned handoff. Preserve dimensions, material, finish, gate requirements and the approved drawing reference at the level needed for production. Sales can manage the proposal, while engineering or fabrication review owns technical release and finance owns the commercial order. Two-way sync should expose the accepted state without letting a late CRM edit silently change released work. Explore the complete [fencing fabrication and installation integration and automation hub](https://www.stacksync.com/industry/construction/fencing-fabrication-installation) for the systems and processes around this guide. ![Summary card: Salesforce NetSuite sync for approved fence configurations](https://www.stacksync.com/images/blog-highlights/icp-fence-fabricators-and-installers-align-salesforce-approved-configurations-with-netsuite-sales-orders.webp) ## What this looks like in fencing fabrication and installation A commercial fencing company sells a perimeter package with custom gates. Salesforce contains the opportunity and customer discussions; NetSuite contains the accepted order. After approval, the customer asks to widen one gate. That change affects material and fabrication work but not every fence section. The integration must show the requested configuration separately from the approved order revision, then return the accepted result once the relevant reviewers authorize it. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Proposed configuration | Sales or estimating | Capture dimensions and options without treating them as released fabrication instructions. | | Approved drawing revision | Technical or fabrication owner | Identify the specification permitted for production. | | Commercial order | Order administration | Own accepted quantities, price and customer authorization. | | Project and installation reference | Operations | Connect the fabricated scope to the correct site and work package. | ![Record ownership diagram: Proposed configuration, Approved drawing revision, Commercial order](https://www.stacksync.com/images/blog-diagrams/icp-fence-fabricators-and-installers-align-salesforce-approved-configurations-with-netsuite-sales-orders.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Define the configuration boundary Decide which attributes must remain structured and which belong in the referenced drawing. Gate opening, material type and finish may need explicit fields, while detailed fabrication instructions remain in controlled documents. Avoid burying all configuration in a deal description that cannot be reliably compared. 2. 02 Join approval to a revision Record the exact configuration and drawing version the customer and internal reviewers accepted. Keep technical release and commercial approval distinguishable. A customer approving appearance does not necessarily establish that fabrication reviewed every production detail. 3. 03 Map the order relationship Carry Salesforce opportunity and scope references into the approved NetSuite order context, and return the order identifier to sales. Confirm the actual order object operations and any custom configuration fields. Do not assume every writable customer field implies support for every transaction or custom record action. 4. 04 Protect released work from proposal edits After release, treat a configuration change as a new proposed revision. Compare the changed attributes with the released baseline and show the affected order lines. Keep the current production version stable until the authorized change process approves and applies the revision. 5. 05 Test a partial configuration change Use an example where one gate changes and the remaining perimeter stays the same. Verify quantity, price and drawing relationships before and after approval. Confirm that a retried handoff updates the existing revision reference instead of creating a duplicate order. 6. 06 Represent repeated gate types without losing individual scope Several gates may share a configuration but have different opening dimensions or site positions. Reuse an approved configuration reference where appropriate while retaining the instance or line that identifies each delivered assembly. A revision to one opening should not change every similar gate on the order. Test that the customer-facing summary can explain both the common specification and the location-specific differences the fabrication team must honor. ![6-step operating sequence: Salesforce NetSuite sync for approved fence configurations](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-fence-fabricators-and-installers-align-salesforce-approved-configurations-with-netsuite-sales-orders.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Customer changes one gate width Scope the revision to that gate and preserve unaffected fence sections. ### Finish description differs between CRM and drawing Route the discrepancy to the configuration owner before release. ### Fabrication has already started Attach work-in-progress context to the change review rather than overwriting the original specification. ## What to verify before expanding - Released configuration identifies its approved drawing version. - Late CRM edits remain proposed until reviewed. - Every commercial line resolves to the correct order reference. - A partial change leaves unrelated scope intact. ## Connect this process to the rest of your operation [Explore Stacksync two-way sync](https://www.stacksync.com/two-way-sync) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real proposed configuration example and the exception your team handles most often, for example customer changes one gate width. - [Salesforce–NetSuite for Fence Fabricators and Installers](https://www.stacksync.com/use-case/salesforce-netsuite-fence-fabricators-installers) - [NetSuite–Supabase for Fencing Production and Installation Boards](https://www.stacksync.com/use-case/netsuite-supabase-fencing-production-board) - [Fence Material Reservations: Connect NetSuite Stock With a Supabase Fabrication and Installation Board](https://www.stacksync.com/blog/fence-material-reservations-connect-netsuite-stock-with-a-supabase-fabrication-and-installation-board) - [Commercial Fencing Accounts: Align HubSpot Site Contacts With Acumatica Customer and Project Records](https://www.stacksync.com/blog/commercial-fencing-accounts-align-hubspot-site-contacts-with-acumatica-customer-and-project-records) - [Custom Gate Orders: Route Approved Drawings Through Fabrication Release and Installation Scheduling](https://www.stacksync.com/blog/custom-gate-orders-route-approved-drawings-through-fabrication-release-and-installation-scheduling) - [NetSuite Two-Way Sync Solutions: Enterprise Integration Guide](https://www.stacksync.com/blog/netsuite-two-way-sync-solutions-enterprise-integration-guide) - [Build vs. Buy: Should You Develop Custom Code or Use a Platform to Sync CRM Data?](https://www.stacksync.com/blog/build-vs-buy-should-you-develop-custom-code-or-use-a-platform-to-sync-crm-data) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync Salesforce connector requirements](https://docs.stacksync.com/two-way-sync/connectors/salesforce) - [Stacksync NetSuite connector and object support](https://docs.stacksync.com/two-way-sync/connectors/netsuite) FAQ ## Frequently asked questions Can the integration generate fabrication approval? It can route and record approval, but the technical or fabrication authority must make the decision. Data movement does not establish that a configuration is suitable to manufacture. Should dimensions live only in free text? Use structured attributes where they drive comparisons or downstream decisions, and retain the controlled drawing for detailed instructions. The right balance depends on the product and fabrication process. What is a useful first order to test? Choose a custom gate order with a revised dimension or finish. It exposes version-control problems that a standard catalog item would not reveal. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) 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 - [integration Salesforce and NetSuite integration](https://www.stacksync.com/integrations/netsuite-and-salesforce) - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [platform Two-way sync](https://www.stacksync.com/two-way-sync) - [Two-way sync guides Understand two-way sync, record matching, field ownership, and production readiness.](https://www.stacksync.com/blog#topic-two-way-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering Construction Company Acquisitions: Unify Customer and Job IDs Across Branch Systems 5 min read read](https://www.stacksync.com/blog/construction-company-acquisitions-unify-customer-and-job-ids-across-branch-systems) [Data engineering Construction Job-Cost Visibility: Define Ownership Across CRM, ERP, and Field Records 4 min read read](https://www.stacksync.com/blog/construction-job-cost-visibility-define-ownership-across-crm-erp-and-field-records) [Data engineering Fire and Security Integrators: Align Salesforce Installed Equipment With NetSuite Customer and Service Records 5 min read read](https://www.stacksync.com/blog/fire-and-security-integrators-align-salesforce-installed-equipment-with-netsuite-customer-and-service-records) ## 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/)