--- title: "NetSuite Postgres sync for machine serials and retrofits" description: "Machine serials, shipments and approved retrofits modeled across NetSuite and Postgres so service can trace what is installed before requesting a part." canonical: https://www.stacksync.com/blog/equipment-manufacturers-netsuite-postgres-machine-serial-history last_modified: 2026-09-18 --- # Equipment manufacturers: connect NetSuite and Postgres machine serial history > 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 the manufacturer's serial stable across owner changes and customer asset tags, with a retrofit history that explains the installed configuration. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 4 min read DATA ENGINEERING ## The operating decision An equipment manufacturer’s NetSuite–Postgres model should connect each machine serial to its build, shipment, installed configuration and approved service changes. Keep customer asset labels separate from the manufacturer’s identity. Two-way sync can support the permitted exchange of selected records while service engineering owns interpretation of compatibility. A complete serial history helps people assemble a service response, but it must not turn an inferred asset match into permission to ship a replacement part. Explore the complete [industrial equipment and machinery integration and automation hub](https://www.stacksync.com/industry/manufacturing/industrial-equipment-machinery) for the systems and processes around this guide. ![Summary card: NetSuite Postgres sync for machine serials and retrofits](https://www.stacksync.com/images/blog-highlights/icp-equipment-manufacturers-netsuite-postgres-machine-serial-history.webp) ## What this looks like in industrial equipment and machinery A machinery business tracks field modifications in a Postgres service application and shipments in NetSuite. A customer reports a failed assembly using a plant asset tag. The original machine was sold to another owner and later received a retrofit. Looking up only the original shipment gives the service desk an outdated configuration. The integration needs durable serial identity, ownership history and a record of the retrofit’s accepted scope so the service team can determine what is actually installed before preparing a part request. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Manufacturer serial | Manufacturing operations | Maintain the stable machine identity independently from customer asset tags and display names. | | Shipment relationship | Order management | Link the serial to its shipped order and destination while retaining later ownership changes separately. | | Field modification | Service engineering | Record the approved retrofit, applicable serial and completion evidence with its effective scope. | | Service request | Service operations | Link the current customer inquiry to the resolved asset without rewriting the original shipment history. | ![Record ownership diagram: Manufacturer serial, Shipment relationship, Field modification](https://www.stacksync.com/images/blog-diagrams/icp-equipment-manufacturers-netsuite-postgres-machine-serial-history.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Establish serial and alias rules List the identifiers customers and internal teams use for the same asset. Create reviewed aliases where evidence supports the relationship. Do not allow a reused customer asset tag to merge two machines or erase a transfer between owners. 2. 02 Model configuration as a history Store the original approved build and subsequent accepted modifications as related records. Preserve when each change became effective. The current installed configuration should be explainable from that history rather than a mutable text field with no supporting events. 3. 03 Connect shipment and service context Link the machine to ERP shipment references, service cases and current customer relationships. Keep warranty or commercial eligibility separate from possession. A machine changing owners does not automatically establish that every original commercial term transferred. 4. 04 Validate late and corrected updates Test a retrofit recorded after a service request and a corrected serial reference. Confirm that the application points the request to the right asset while retaining the correction history. Reconcile repeated events so a retrofit is not applied twice. 5. 05 Scope any return update narrowly If service needs to update an ERP field, confirm the operation and owner. Preserve the accepted destination response. The operational history can remain valuable even when certain financial or asset transactions require a separate approved process. ![5-step operating sequence: NetSuite Postgres sync for machine serials and retrofits](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-equipment-manufacturers-netsuite-postgres-machine-serial-history.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### A customer supplies only an asset tag Use approved alias evidence or request a nameplate or shipment reference. Preserve uncertainty until the asset is resolved. ### A retrofit is proposed but not installed Keep proposal and completed modification states separate; only accepted installation evidence changes the current configuration. ### A serial was entered incorrectly in an old case Correct the relationship through the review process and preserve why it changed. Do not silently rewrite unrelated history. ## What to verify before expanding - The asset remains identifiable after a customer or location change. - A service user can trace the current configuration to approved modifications. - A proposed retrofit cannot appear as an installed component. - Repeated update delivery preserves one effective modification record. ## 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 manufacturer serial example and the exception your team handles most often, for example A customer supplies only an asset tag. - [Salesforce and NetSuite two-way sync for equipment manufacturers](https://www.stacksync.com/use-case/equipment-salesforce-netsuite-two-way-sync) - [Salesforce and Acumatica two-way sync for equipment aftermarket teams](https://www.stacksync.com/use-case/equipment-salesforce-acumatica-two-way-sync) - [Equipment aftermarket: connect Salesforce parts quotes to Acumatica order status](https://www.stacksync.com/blog/equipment-salesforce-acumatica-aftermarket-parts-quotes) - [Equipment commissioning readiness: connect sales promises, site prerequisites and service dispatch](https://www.stacksync.com/blog/equipment-commissioning-readiness-workflow) - [Equipment warranty RMAs: coordinate replacement, return and credit decisions](https://www.stacksync.com/blog/equipment-warranty-rma-replacement-return-workflow) - [Salesforce ERP Integration: Best Real-Time Sync Solutions in 2026](https://www.stacksync.com/blog/best-data-integration-solutions-for-salesforce-and-erp-with-real-time-sync) - [Bi-Directional Sync for Salesforce and Beyond: Ensuring Operational Efficiency](https://www.stacksync.com/blog/bi-directional-sync-for-salesforce-and-beyond-ensuring-operational-efficiency) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Oracle NetSuite: using external IDs](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_156334828635.html) FAQ ## Frequently asked questions Should the customer’s asset number replace the machine serial? No. It can be a useful alias, but the manufacturer’s serial and its context should remain distinct and stable. Can this data determine the replacement part automatically? It can provide the required history and approved references. Compatibility and consequential substitutions still follow the service-engineering process. Which pilot case is most informative? Use a transferred machine with a completed retrofit and an ambiguous customer tag. It tests identity, time and configuration together rather than only copying an uncomplicated shipment. 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 NetSuite and PostgreSQL integration](https://www.stacksync.com/integrations/netsuite-and-postgresql) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector PostgreSQL integrations](https://www.stacksync.com/connectors/postgresql) - [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 components: connect NetSuite shipments to Postgres lot evidence 4 min read read](https://www.stacksync.com/blog/automotive-netsuite-postgres-lot-shipment-traceability) [Data engineering Electronic components: connect NetSuite and Postgres revision-aware stock allocation 4 min read read](https://www.stacksync.com/blog/electronics-netsuite-postgres-component-revision-allocation) [Data engineering NetSuite and Postgres for manufacturing: model production status without losing order identity 4 min read read](https://www.stacksync.com/blog/manufacturing-netsuite-postgres-production-status-data-model) ## 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/)