01
Every entity looks different
A parent, subsidiary, branch, and ship-to can each need their own product catalog, price, and content.
Enterprise B2B Commerce | Multi-Org, Approvals, RFQ | Nomad
Solutions / Enterprise B2B
Enterprise B2B, without the enterprise drag.
Parent-child accounts, approval rules, quotes, and multi-warehouse stock — synced to your ERP.
Preview
Where it breaks
The short version.
- Every entity looks different
- The order waits for a person
- The ERP has the rules
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
The order waits for a person
Approvals and quote reviews live in email while the cart sits.
03
The ERP has the rules
Multi-company hierarchies, contract pricing, and approval rules only work if your website enforces them.
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
One website, many contexts
The customer sees the right product catalog, price, and ship-to for the entity.
02
Rules run before the order
Approvals and quotes are visible, not hidden in a thread.
03
The ERP stays the source
Orders, bills, and customer data land where they belong.
03 / The ERP handoff
What the ERP already knows.
The website should respect the main system, not recreate it.
01
Customer hierarchy
Parent, subsidiary, branch, and ship-to context from the ERP.
02
Price and stock
Contract pricing, warehouses, and buying rules by entity.
03
Orders and bills
The transaction and financial trail stay in the main system.
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 the hierarchy and who can buy for whom.
02
Map the rules
Confirm which approval, quote, and pricing rules live in the ERP.
03
Set up the context
Make the way customers buy entity-aware.
04
Prove the edge cases
Test the parent, branch, and ship-to scenarios before launch.
05 / Questions
What this usually brings up.
Bring the hard questions to the first working session.
Start with the legal entities, branches, and ship-tos the customer actually uses.
Approvals, quote states, and price rules need a visible owner.
A shared product catalog still needs local content and delivery context.
Agree on the account, price, terms, and approval state before build.
06 / Keep going
Connect the path to the rest of the system.
Start with the closest piece, then widen the scope.
The next moveBring your enterprise complexity.
Bring your enterprise complexity.
We'll map the buying path.
Show us the entities, approval rules, and quote steps. We will map what the website should show and what the ERP should own.