Glivent FAQs
How could Glivent manage wholesale price and backorder exceptions?
Direct Answer
Glivent could help a distributor bring price mismatches and stock shortfalls into one review process. A workflow might compare an order with approved account terms and inventory data, show the affected lines and prepare options. Staff would still decide discounts, substitutions, allocation and what to promise the customer.
What matters first
An order can be captured correctly and still stop before fulfilment. A customer's purchase order may use an old price, exceed an approved credit limit or request more stock than is available. The right response depends on that customer's terms, the product and who has authority to approve a change.
What Glivent could do
Glivent would first check which exception rules the ERP or order-management system already supports. Where the gap sits between systems or teams, an example workflow could gather the affected order lines, the approved customer terms and current stock position into a review queue.
For a shortfall, it might show an available date or permitted alternatives for staff to consider. For a price difference, it could show the source order beside the approved price record. Once someone decides, the workflow could prepare the authorised update and customer message, then record who approved it.
What stays with your team
Credit overrides, non-standard discounts, substitutions and disputed returns are commercial decisions. They should go to the person authorised to make them. The workflow should make the evidence easier to inspect without presenting a suggested option as an automatic decision.
Discovery would test exception volume, stock-data quality, account rules and system access before Glivent recommends a first scope.