Glivent FAQs
How could Glivent handle wholesale orders across email and EDI?
Direct Answer
Glivent could assess how orders reach your business and where staff still re-enter or check them. A first workflow might structure email or PDF orders, compare them with approved customer and product data, then send uncertain lines to sales staff before an order is created. Existing EDI and ERP functions should be checked first.
What matters first
Many distributors receive orders through more than one channel. An EDI order may already pass straight into the ERP, while an emailed purchase order still needs someone to identify the customer, match product codes and check quantities. The useful question is which orders create manual work or errors in your business, and why.
What Glivent could do
During discovery, Glivent would check the ERP, EDI service and ordering portal before proposing another intake step. If emailed or PDF orders remain a gap, an example workflow could:
- Capture the order and keep the original document attached.
- Identify the customer, products, quantities and requested date.
- Compare those details with approved customer and product records.
- Route missing fields and uncertain matches to a named staff member.
- Create an order in an authorised system only after the agreed checks and approvals.
The exact actions depend on the systems, data quality and access available. Glive Flow could give staff a place to review exceptions and trace what happened; it would be configured for the agreed implementation.
What stays with your team
Sales staff should decide how to handle ambiguous product matches, changed terms and orders that do not meet the agreed rules. The ERP remains the authority for product, price, credit and stock data. A workflow should not quietly turn a guessed product code into a confirmed order.
For the general mechanics of order intake and EDI, see the related Knowledge Base guide. This answer describes how Glivent might assess the remaining handoff in a specific business.