01
Product catalogs collide
One shared product catalog does not fit every entity, region, or contract.
Multi-Org & Multi-Site B2B Commerce | Nomad
Solutions / Multi-company & multi-site
One website. Many organizations.
Map parent companies, branches, ship-to locations, and buyer roles directly from your ERP.
Preview
Where it breaks
The short version.
- Product catalogs collide
- Pricing gets lost
- Content is local
01 / The extra work
What slows your team down when your website and ERP don’t talk.
When your store isn’t wired to your ERP, your staff ends up doing the work by hand.
02
Pricing gets lost
Parent, subsidiary, and ship-to pricing rules can disagree at the cart.
03
Content is local
Product content, delivery rules, and contacts change by site.
02 / What good looks like
What changes when your website runs on your ERP.
Customers get self-service answers, and your team gets hours back every day.
01
Entity-aware buying
The right product catalog, price, and ship-to follow the buying context.
02
One ERP truth
Customer hierarchy, price lists, and warehouses come from the ERP.
03
A shared website
One system serves many organizations without a separate site for every entity.
03 / The ERP handoff
What the ERP already knows.
The website should respect the main system, not recreate it.
01
Hierarchy and ship-tos
Parent, subsidiary, branch, contact, and delivery context.
02
Price lists and warehouses
Contract pricing and stock by entity.
03
Orders and bills
The order lands with the right account and financial trail.
04 / The path
A focused path from pain to proof.
Start with the real version. Prove the rules before launch.
01
Map the entities
Document who buys for whom and which ship-tos matter.
02
Map the rules
Separate shared product catalog rules from local price and content rules.
03
Set up the context
Make the online store respond to the buying entity.
04
Prove the edge cases
Test the parent, branch, and ship-to combinations that break today.
05 / Questions
What this usually brings up.
Bring the hard questions to the first working session.
Shared products do not always mean shared prices or content.
Delivery, tax, shipping, and terms may follow the location.
Decide what the ERP owns and what the website can enrich.
The financial and reporting entity has to be unambiguous.
06 / Keep going
Connect the path to the rest of the system.
Start with the closest piece, then widen the scope.
The next moveBring the hierarchy.
Bring the hierarchy.
We'll bring the context.
Show us the entities, product catalogs, and ship-tos. We will map the buying context and the ERP handoff.