
Orders nobody can price at checkout
Freight-heavy orders that close online instead of over the phone. A distributor selling to contractors, where a large share of orders ship by freight and can’t be priced at checkout.
The problem
LTL freight can’t be quoted until someone looks at the pallet. That normally means the customer pays later, by phone, and somebody re-keys the order. We had to let the web store take payment for goods, then collect freight separately, without adding a single step for the sales team.
What we built
- Integrated the storefront directly with the ERP so orders land as real sales orders, not email
- Built a payment-hold workflow: reps quote freight in the ERP as they always have, set one status, and the customer is emailed a secure payment link automatically
- Cleared the hold through the API the moment payment settles, releasing the order to the warehouse
- Configured gateway fraud rules against the real order profile rather than defaults
Result
- Nine-step freight workflow, seven steps automatic
- Sales reps do two things, both inside the ERP they already use
- Nobody at the company ever logs into the website
Automation running here
- Freight orders that clear themselvesA distributor’s reps quote LTL freight in the ERP as they always did, then set one status. Everything after that is automatic: the customer is emailed a secure payment link, the payment settles, the hold clears through the API, and the order releases to the warehouse. Nine steps, seven of them unattended.
The order, start to finish
- Order placedCustomer
- Goods paidSystem
- Sales order createdSystem
- Freight quotedYour team
- Status setYour team
- Link emailedSystem
- Freight paidCustomer
- Hold clearedSystem
- Released to warehouseSystem
Product data nobody can actually build on
The catalogue of record is a print document, a spreadsheet, and someone’s memory, and the three disagree. Nothing downstream can be better than the data underneath it, so the storefront, the search filters and the ERP all inherit the same mess.
Read the case →A storefront bolted to the side of a website
The catalogue lives in one system and commerce in another, joined by a sync that drops. Every product change gets made twice, and the two never quite agree about what you sell.
Read the case →