How an order reaches your ERP
- Gebruiker
- Admin
Every order takes the same path from the e-mail to your ERP, and it can stop at some stages on the way. It arrives, Hyperfox reads it, you check it, and it is sent to your ERP. If you are new to inquiries and orders, read Inquiries, orders and lines first.
Five stages
- Arrival. An order reaches Hyperfox, usually as an e-mail with an attachment. Hyperfox stores what arrived as an inquiry.
- Reading. While the inquiry is in Processing, Hyperfox reads the document, fills in one or more orders and matches them to your customers, items and units.
- Checking. The orders wait in To validate. You compare each order with the document, correct what Hyperfox read wrong and click Validate. Only one person works on an inquiry at a time.
- Sending. Hyperfox sends every validated order to your ERP and moves it to Archive. It also remembers the customers, items and units you corrected, and uses them for later orders.
- Answer. Your ERP's answer sets the final status of the order. If sending fails, the order returns to To validate with the status Submit Failed, so you can correct it and validate it again.
One inquiry, one or more orders
Most inquiries hold one order. When a document holds several orders, for example one per delivery address, Hyperfox creates one order for each. All orders stay together in one inquiry. Validate and Reject act on every order of the inquiry that still needs work.
Some orders take a different path. An order from a connected system, such as a web shop, can skip To validate and go straight to your ERP. Reject ends the path: the orders never reach your ERP. Retry sends the inquiry back to stage 2, and Hyperfox reads it again from the start.
What each order and inquiry status means lists every status along the way.