What does it mean to add a subsidiary to an existing NetSuite account?

Adding a subsidiary to an existing NetSuite account means introducing a new legal entity that operates within the same NetSuite instance as the original company. The new subsidiary shares the same scripts, workflows, bundles, customer records, and global lists as the existing account, which requires careful scoping to ensure the new entity operates independently without affecting the original. In practice, this involves restructuring the account hierarchy, auditing installed logic to determine what applies to the new subsidiary, designing roles and permissions to isolate the new entity's data and access, and validating the configuration in a sandbox environment before applying changes in production. For businesses that want consolidated reporting and a single system to manage and license, adding a subsidiary is more practical than opening a separate NetSuite account, but it requires more precise design work upfront.

What happens when two subsidiaries share customers in NetSuite?

NetSuite customer IDs are globally unique across an account, which means a customer that already exists under one subsidiary will conflict with an import file that includes the same customer for a second subsidiary. Snapshot resolved this for Kurtz Bros. Central Ohio by designing an import approach that brings in only customers genuinely new to the account and reuses existing records, without editing or merging them, where a customer already exists under Northern Ohio. Transactions, balances, and reporting remain separated by subsidiary. A COH-specific pricing framework handles price separation at the order level, so shared customer records do not result in shared or inherited pricing. Businesses evaluating Multi-Subsidiary Customer enablement should understand that this feature is not easily reversed in a live account and warrants careful consideration before activation.

How does custom pricing by subsidiary work in NetSuite?

Custom pricing by subsidiary in NetSuite requires building a pricing framework that applies the correct prices for a given subsidiary's orders without inheriting or conflicting with another subsidiary's price structures. For Kurtz Bros. Central Ohio, Snapshot built COH-specific price levels at the item level, a custom customer-product-location pricing record for customer-specific overrides, and custom sales order and quote forms with client scripts that select the right price based on the employee, customer, item, quantity, and delivering location. Validation scripts catch mismatches before orders reach fulfillment. Guardrails on the COH forms prevent Northern Ohio pricing from being applied to a COH order. Native NetSuite pricing serves as a fallback when no COH-specific price exists. NetSuite custom pricing by subsidiary is a development engagement, not a configuration toggle, and the design needs to account for quote-to-order conversion, manual override scenarios, and edge cases specific to how each subsidiary prices its products.

Does Snapshot work with multi-entity businesses running NetSuite?

Snapshot works with multi-entity businesses at various stages of NetSuite adoption, including companies looking to consolidate related entities into a shared account and businesses managing separate subsidiaries that need to coexist without operational overlap. Kurtz Bros. is a long-standing Snapshot client whose Northern Ohio operation represents years of NetSuite consulting, development, ecommerce integration, and ongoing managed services work. Expanding that account to include Central Ohio required building on that existing relationship and system knowledge to design a multi-company setup that served both entities without compromise. Snapshot approaches multi-entity NetSuite engagements with a design-first mindset, establishing the permission model, hierarchy, and data strategy before any configuration work begins.

NetSuite Subsidiary Management Case Study

Q: How do you keep two subsidiaries in the same NetSuite account from seeing each other's data?

Keeping two subsidiaries isolated within a shared NetSuite account requires a permission-first design approach. Because NetSuite does not allow deletion of shared records without removing them from the entire account, isolation is enforced through roles, form restrictions, and subsidiary-scoped logic, keeping shared records in place. Custom roles can be built to grant administrative access limited to a specific subsidiary, which is necessary because NetSuite's standard Administrator role cannot be restricted by subsidiary. Transaction forms are restricted so only the intended subsidiary's roles can access or use them. Scripts and workflows are scoped to fire only for the correct subsidiary. Global lists and shared records are managed through naming conventions and saved searches to keep each subsidiary's views accurate without touching shared data. Sandbox validation before any production change is essential to confirm that no crossover exists between entities.

Kurtz Bros. Central Ohio

Industry: Landscape Supply

Scope: NetSuite Subsidiary Restructuring, Script and Workflow Audit, Permission and Visibility Management, Customer Strategy, Custom Subsidiary Pricing Framework, Delivery Rates Framework, Sandbox Testing, Production Migration

How Kurtz Bros.' Central Ohio business joined a live, fully integrated NetSuite account as its own subsidiary without disrupting active operations

About Kurtz Bros.

Kurtz Bros. is a multi-generational Ohio landscape supply company with deep roots in bulk material distribution, serving professional contractors and landscapers across Northern and Central Ohio. Kurtz Bros., Inc. (Northern Ohio) had been fully operational in NetSuite for years, with SuiteCommerce, a BigCommerce and Celigo integration, and a range of connected systems running production daily. Kurtz Bros. Central Ohio, LLC operated as a separate but related entity on its own ERP system, handling ticketing, invoicing, and accounting independently.

As the family of companies looked to consolidate onto a single platform, the goal was clear: one system to license, support, and grow from. However, the two businesses needed to remain financially and operationally separate. Kurtz Bros. partnered with Snapshot to design and execute the expansion, adding Central Ohio as its own subsidiary while leaving Northern Ohio's operations, integrations, and data untouched.

Project Overview

Kurtz Bros. Central Ohio had been running its own ERP for years, managing ticketing, invoicing, and accounting independently from Northern Ohio. Consolidating onto a single NetSuite account made financial and operational sense, but it introduced a layer of complexity: every script, workflow, bundle, and customer record already in the account would apply to the new subsidiary by default, while Northern Ohio continued running its daily operations throughout.

To bring Central Ohio in without disrupting Northern Ohio, Snapshot designed the entire engagement around a single governing principle: limit visibility and access, never delete. Removing Northern Ohio records from Central Ohio's view would remove them from the account entirely. Snapshot set up roles, permissions, and subsidiary-keyed logic to enforce data isolation and leave shared data untouched.

In addition, Snapshot restructured the account hierarchy, audited every installed script and workflow, built a custom permission model for Central Ohio administrators, and delivered a COH-specific pricing and delivery framework, all validated in a two-sandbox environment.

Subsidiary Restructuring and Script Audit

NetSuite was originally a single-subsidiary account for Kurtz Bros. Snapshot introduced a new root parent entity and repositioned Northern Ohio and Central Ohio as sibling subsidiaries beneath it and reviewed financial reporting before and after the restructuring to confirm accuracy.

With the hierarchy in place, Snapshot exported every active script, workflow, and bundle installed in the account and generated plain-language summaries of what each one did. Snapshot and Kurtz worked through the full list together, so Central Ohio could identify which pieces of logic needed to be excluded from the new subsidiary. Snapshot made the updates in sandbox, received client approval, and applied them in production. Snapshot also set the default subsidiary on the SuiteCommerce storefront to ensure web orders continued routing to Northern Ohio.

Permission and Visibility Management

Kurtz Bros. Central Ohio's ownership had a firm requirement: Central Ohio users should only be able to see and affect Central Ohio data, administrators included. NetSuite's standard Administrator role cannot be restricted to a single subsidiary, so Snapshot designed a custom admin-style role that delivers broad administrative access scoped entirely to Central Ohio. Snapshot built the role across both sandbox environments and into production, with the Central Ohio and Northern Ohio teams defining the additional roles each subsidiary would need before and after financial go-live.

Central Ohio transaction forms were restricted so only Central Ohio roles could access or use them, while scripts and workflows were scoped by role or subsidiary through custom role permissions. Global lists, terms, and categories shared across the account were managed through naming conventions, saved searches, and form-level filtering to keep Central Ohio's views clean without deleting shared records. Before moving anything forward, the Central Ohio team validated in sandbox that no crossover of data or activity existed between the two subsidiaries.

Customer Strategy

NetSuite customer IDs are globally unique across an entire account. When Central Ohio began importing its customer records, many of those customers already existed under Northern Ohio. The solution was to let shared customers remain shared, with Central Ohio's pricing framework carrying the separation at the transaction level.

Central Ohio only imports new customers to the NetSuite account. For customers that already exist under Northern Ohio, Central Ohio reuses those records without editing or merging them. Transactions, balances, and reporting stay separated by subsidiary because the pricing framework, not the customer record, is where the separation lives.

Central Ohio Pricing and Delivery Framework

Central Ohio's pricing differs from Northern Ohio, and varies further by customer, product, and delivery location. Snapshot built a subsidiary-specific pricing framework that selects the correct price at the order level based on those variables, with validation logic to catch mismatches before an order reaches fulfillment. Quoted pricing follows the same logic, carries through to the converted sales order, and supports manual override where needed. Guardrails on the Central Ohio order forms prevent Northern Ohio pricing from being applied to a Central Ohio order by mistake, and native NetSuite pricing serves as a fallback when no Central Ohio-specific price exists.

Delivery charges were previously calculated from a zip-code-driven spreadsheet. Snapshot replaced it with a structured delivery framework in NetSuite that calculates charges based on load type, weight, and delivery location, generating a delivery line directly on the sales order or quote. Delivery rates set on a quote are preserved when the order is converted. Snapshot built the underlying data model to accommodate automated rate lookup by zip code, location, and material basis.

Testing and Production Migration

Snapshot ran testing across two separate sandboxes to keep the two companies' validation work cleanly divided. One sandbox was connected to Northern Ohio's live systems and used exclusively for regression testing, confirming that every change made for Central Ohio had no effect on the operating company. The other was a clean, isolated environment where Central Ohio's configuration, financials, and workflows were built and validated end to end.

Once testing was completed, Snapshot migrated everything to production in a single coordinated pass, ensuring nothing was left in an intermediate state.

What's Live and What's Next

Central Ohio is running accounting and financials in NetSuite today, with its pricing and delivery frameworks live, subsidiary data isolated as designed, and Northern Ohio's operations, ecommerce integrations, and connected systems untouched throughout. The customer strategy has held up in production, with shared records reused cleanly and transactions staying separated by subsidiary.

Future plans include expanding NetSuite to cover Central Ohio's daily order entry, dispatch, and invoicing, adding a joint venture entity as a new subsidiary, continuing to build on the framework Snapshot established during this project.

Why Companies Choose Snapshot:

Our Core Expertise

At Snapshot, we don't just implement software, we assist companies in modernizing and scaling operations by simplifying operational complexity

NetSuite Consulting & Development

With over 12 years as a NetSuite Alliance Partner, we provide full-lifecycle consulting, SuiteApp development, and long-term optimization. Our focus is on leveraging NetSuite as the core engine of your business to drive scalability and predictive insights.

eCommerce Excellence

With over 25 years of commerce expertise, we understand that a storefront is only one piece of a much larger picture. Our approach takes into consideration your entire ecosystem—from the customer-facing experience to the critical business systems that power fulfillment, finance, and operations. We ensure your commerce platform isn't just a "bolt-on," but a high-performance tool built around your unique business architecture.

Data Integration Expertise

We specialize in high-performance connectivity using Celigo, Patchworks, and custom solutions. We focus on unifying disparate data silos to ensure your business operates with one cohesive data set.

ERP Optimization 500x500 - 2026-08-11T125251.204

Is managing a growing family of companies stretching your NetSuite setup?

Snapshot helps multi-entity businesses expand NetSuite across subsidiaries without disrupting operations.

Let's build the right structure for where your business is going.