--- title: "CRM and ERP field ownership for manufacturing orders" description: "Requested, accepted, released and credit-approved order values each get one owner in Salesforce and NetSuite instead of one shared delivery-date field." canonical: https://www.stacksync.com/blog/manufacturing-crm-erp-field-ownership-matrix last_modified: 2026-09-18 --- # Manufacturing CRM and ERP ownership: decide who controls each order field > 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 field ownership matrix gives each order decision one owner, so a CRM edit becomes a request and a planning date, quality release or credit hold cannot be overwritten. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 4 min read DATA ENGINEERING ## The operating decision Manufacturing CRM–ERP field ownership should be defined by the business decision represented by a field. Sales owns a requested delivery date; planning owns the accepted promise; quality owns release; finance owns credit. Two-way sync should carry these decisions without collapsing them into a single editable value. Document identity, allowed direction, revision behavior and exception ownership for the small set of fields that trigger work before expanding into a broader data program. Explore the complete [manufacturing integration and automation hub](https://www.stacksync.com/industry/manufacturing) for the systems and processes around this guide. ![Summary card: CRM and ERP field ownership for manufacturing orders](https://www.stacksync.com/images/blog-highlights/icp-manufacturing-crm-erp-field-ownership-matrix.webp) ## What this looks like in manufacturing A mid-market manufacturer connects its CRM and ERP to reduce status-checking emails. Initially, both applications expose a field called delivery date. Sales updates it after a customer call, while planning updates it after a machine outage. Each synchronization overwrites the other team’s value, and nobody can explain which commitment was accepted. Splitting the requested date from the planned and confirmed dates resolves the semantic conflict. The integration can then transmit the request, route the review and return the decision without pretending the two edits meant the same thing. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Customer request | Commercial operations | Record what the customer asked for, when it was received and which order revision it applies to. | | Accepted commitment | Production planning | Publish the approved date and quantity with the approving owner and applicable revision. | | Quality release | Quality management | Keep held, conditionally accepted and released states distinct from production completion. | | Financial permission | Finance | Maintain credit or commercial approval independently from operational readiness and shipping progress. | ![Record ownership diagram: Customer request, Accepted commitment, Quality release](https://www.stacksync.com/images/blog-diagrams/icp-manufacturing-crm-erp-field-ownership-matrix.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Name the decision before naming the field List the questions people ask during a handoff: what was requested, what was accepted, what is ready and what may ship. Map each question to its authoritative owner. Replace overloaded labels with explicit meanings before choosing a synchronization direction. 2. 02 Define identity and revision rules Specify the customer, order and line references that make a value applicable. Decide whether a change belongs to a new revision or corrects an existing record. Preserve accepted history when later requests arrive, particularly after materials are committed or production has started. 3. 03 Specify conflict handling in business terms For each consequential field, state what happens when another system submits a different value. Options include recording a proposal, rejecting the edit or requiring review. Last-write-wins is appropriate only when the business deliberately accepts that behavior for the selected data. 4. 04 Exercise ownership with both teams present Use a sample containing an approved order, a changed request and a hold. Ask sales and operations to edit their respective fields. Inspect which values moved, which requests await review and what an ordinary user sees. Record disagreements as policy decisions, not just mapping defects. ![4-step operating sequence: CRM and ERP field ownership for manufacturing orders](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-manufacturing-crm-erp-field-ownership-matrix.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### A field is required by both systems but has different meanings Create separate requested and accepted representations, or transform through an explicit rule. Do not solve a semantic disagreement by choosing whichever system updated last. ### No team accepts ownership Keep the field out of an automated decision until a process owner is named. Publishing a value without an accountable owner creates a faster disagreement. ### An approved value is corrected retrospectively Record the correction and its effective scope. Reconcile dependent records without rewriting the history of actions already taken on the earlier approval. ## What to verify before expanding - Each production-triggering field has one named owner and an allowed update path. - A new customer request cannot silently replace an accepted production commitment. - Quality hold and credit hold remain independently visible when production is complete. - Users can explain why an update was accepted, rejected or routed for review. ## 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 customer request example and the exception your team handles most often, for example A field is required by both systems but has different meanings. - [Salesforce and Acumatica for manufacturing: turn an approved quote into a traceable order](https://www.stacksync.com/blog/manufacturing-salesforce-acumatica-order-handoff) - [Manufacturing order revisions after production release: automate the review handoff](https://www.stacksync.com/blog/manufacturing-order-revisions-after-production-release) - [Supplier-delay workflows for manufacturers: connect PO confirmations to customer commitments](https://www.stacksync.com/blog/manufacturing-supplier-delay-purchase-order-follow-up) - [Real-Time Sync for Manufacturing ERP & Shop Floor Data](https://www.stacksync.com/blog/real-time-sync-manufacturing-erp-shop-floor-data) - [Making SQL Server and NetSuite Agree on the Same Record](https://www.stacksync.com/blog/two-way-sync-sql-server-netsuite) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Salesforce: change data capture events](https://developer.salesforce.com/docs/platform/platform-events/guide/platform-events-objects-change-data-capture.html) - [Oracle NetSuite: using external IDs](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_156334828635.html) FAQ ## Frequently asked questions Is field ownership only an IT concern? No. IT implements the behavior, but sales, finance, quality and operations determine the decision authority. A technical mapping cannot resolve an unresolved business policy. Does one system need to own every record? Ownership can differ by record and field. A CRM can own relationship details while the ERP owns financial identity and planning owns accepted production commitments. How much should be documented before a pilot? Document the fields that create work, change promises or authorize financial actions first. Include identity, owner, allowed direction and exceptions; expand after those rules survive representative tests. 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 Automotive component suppliers: connect Salesforce program awards and NetSuite demand 4 min read read](https://www.stacksync.com/blog/automotive-components-salesforce-netsuite-program-award-demand) [Data engineering Equipment manufacturers: connect Salesforce configurations to NetSuite orders 4 min read read](https://www.stacksync.com/blog/equipment-manufacturers-salesforce-netsuite-configured-order) [Data engineering Salesforce and NetSuite for manufacturers: share credit and order status without conflicting ownership 4 min read read](https://www.stacksync.com/blog/manufacturing-salesforce-netsuite-customer-credit-order-status) ## 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/)