A wholesale portal should let each known account order in the unit of measure they buy, with price and quantity conversion that matches how you sell them. Week one on Parcel Build is that first working version for the accounts and SKUs that already break when buyers pick the wrong UOM. You own the code. Flat monthly. See custom software for wholesalers. If customer-specific UOM on portal lines is the gap, start a free 30-day build.
Which customer-specific UOM rules belong in a week-one portal (and which stay in ERP for later)?
Week one can cover the sell unit for known accounts and the SKUs that already cause disputes: each, case, or the unit that account actually buys, with quantity and price conversion that matches the quote. A buyer should see and order in that unit without a phone call to correct the line. A full material-master UOM program, warehouse pack engines, and every alternate unit for every SKU can wait.
Why email corrections and rekeyed units create price and quantity disputes after the buyer thinks they ordered correctly
The buyer submits in eaches. Your team sells that account by the case. Someone rekeys the line. The price no longer matches what the buyer planned. Emails fly. Quantity and extended price both get disputed after the order already looks placed.
The dispute is a unit mismatch the portal allowed. The account already has a sell unit. The line did not use it.
What week one can cover
An account-level default UOM on the SKUs that already break. Conversion that keeps quantity and price aligned with how you quote that account. Clear line text so the buyer sees the unit before submit. A human path when a known account needs a one-off unit.
On Parcel Build, week one is a first working version of that path. Flat monthly. You own the code.
What stays out of month one
Defer a full material-master UOM program. Defer warehouse pack engines. Defer every alternate UOM for every SKU. Month one is the sell unit and conversion for the accounts and lines that already break.
FAQ
Is customer-specific UOM the same as MOQ or case-pack enforcement?
No. Customer-specific UOM is the unit that account buys and the conversion that keeps price and quantity honest. MOQ and case-pack rules are minimums and multiples at cart. They can live together later. Week one can prove the account unit without cloning pack enforcement.
Does week one need every alternate UOM from ERP before the first accounts can order correctly?
No. Week one can start with the accounts and SKUs that already break when the wrong unit is picked. The rest of the catalog can wait until that path is earning its place.
Next step
If customer-specific UOM on wholesale portal lines 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.