01
Units and catch weights
Case, each, pound, and catch-weight rules can turn a simple order into a phone call.
Foodservice B2B eCommerce | Nomad
Industries / Foodservice
Cases, cutoffs, and orders that can't wait.
Cases, catch weights, order cutoffs, delivery windows, and smart substitutions.
Preview
Where it breaks
The short version.
- Units and catch weights
- Cutoffs and delivery windows
- Substitutions and contracts
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
Cutoffs and delivery windows
A great price is useless if the order misses the truck.
03
Substitutions and contracts
Contract items, pack sizes, and substitutions need a clear path.
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
Unit clarity
Customers see the right unit, pack, and price before they add to cart.
02
Delivery-aware checkout
Cutoffs and delivery windows are visible when they matter.
03
Contract pricing
Account-specific pricing and substitutions follow the customer.
03 / The ERP handoff
What the ERP already knows.
The website should respect the main system, not recreate it.
01
Customer contracts
Account pricing, item eligibility, and delivery context.
02
Item stock
Warehouse, unit, and pack information from the ERP.
03
Orders and bills
The order lands cleanly with the right unit and terms.
04 / The path
A focused path from pain to proof.
Start with the real version. Prove the rules before launch.
01
Map the units
Document case, each, pound, and catch-weight rules.
02
Map the delivery
Confirm cutoffs, routes, and delivery windows.
03
Set up the product catalog
Make units, contracts, and substitutions visible.
04
Prove the cutoff
Test the order that arrives five minutes late.
05 / Questions
What this usually brings up.
Bring the hard questions to the first working session.
Start with the order pad, not the item master.
The online store should show the rule before checkout.
A substitution is a promise; make it explicit.
Bring the account-specific rules into the buying context.
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 foodservice order.
Bring the foodservice order.
We'll map the buying path.
Show us the units, cutoffs, and substitutions that cause calls. We will map the online store around them.