A wholesale portal should support parent and child company accounts when buyers purchase across subsidiaries. Week one on Parcel Build is that first working version: hierarchy links plus a switcher so a parent user can act in a child account with the right prices and addresses. You own the code. Flat monthly. See custom software for wholesalers. If account hierarchy parent and child buying in a wholesale portal is the gap, start a free 30-day build.
When do you need parent/child hierarchy instead of multi-location carts?
Use parent and child hierarchy when subsidiaries are separate commercial entities with their own price lists, bill-to records, or order history. Multi-location carts fit when one company ships to many sites under one account. Week one can prove hierarchy links and a switcher for known parent and child pairs. Deep multi-entity finance consolidation can wait until that path earns its keep.
On Parcel Build, week one is a first working version of that path. Flat monthly. You own the code.
Why one flat company login fails when subsidiaries need separate price lists and bill-to records
One shared login mixes prices meant for different legal entities. A buyer places under the wrong bill-to. Finance cannot tell which subsidiary owns the order. Password sharing across entities becomes the workaround, and audit trails break.
Hierarchy with a switcher keeps each child on its own prices and addresses while a parent user can still act without sharing passwords across entities.
What stays out of month one
Defer full multi-entity finance consolidation. Defer multi-entity system rebuilds as the primary path. Month one is hierarchy links and a parent-to-child switcher for known accounts so buying stays on the right prices and addresses.
FAQ
Is account hierarchy the same as multi-location carts?
No. Multi-location carts let one company choose ship-to sites on a shared account. Account hierarchy links parent and child companies so a parent user can switch into a child with that child's prices and bill-to. They solve different gaps. Week one can prove hierarchy without cloning multi-location carts as the primary path.
Does week one need five hierarchy layers before a parent can switch into one child?
No. Week one can start with one parent and the child accounts that already break under a flat login. Extra layers can wait until that switcher path earns its keep.
Next step
If account hierarchy parent and child buying in a wholesale portal is what feels hardest, start a free 30-day build. Name that gap on the form. We scope a free 30-day build on that problem: first working version in week one, flat monthly after if you want to continue.