Lucy Workflow

Owned by Ben Dalton
Last updated: Oct 01, 2019
1 min read

This is the workflow you can expect Lucy to follow when an email arrives


1. Lucy checks the message sender. Are they recognised? 

(error) No - she marks the message for review so that you can assign / set up the Trading Partner. 

(tick) Yes - she assigns it to the relevant Trading Partner. 


2. Next, Lucy checks for attachments. Are there any?

(error) No - forward the message to your nominated email address or flag for attention.

(tick) Yes - open and determine the document type. 

3. Is the attachment a PDF (and is it readable)? 

(error) No - Lucy forwards or flags the message. An "unreadable" attachment could be:  

      • non-system-generated PDFs (i.e. a scanned image of a PDF)
      • other document types (Word or Excel docs, for example). 

(tick) Yes - Lucy checks for a document map for this customer.


3. Is there an existing document map for this Trading Partner? 

(error) No - mark the order for attention and request a document map.

(tick) Yes - process and validate the order, then integrate it to your ERP.


4. Exceptions to the rules? Lucy can handle the curve balls your customers throw. 

Code translations - your customer uses their own internal product codes? No problem. Translate them into your product codes. 

Mapping rules - your customer inserts a 'P/O' into their purchase order number? Not to worry, Lucy can strip that excess data out. 

Price or Product errors - your customer has a $1500 product listed on their order at $15? Or they've used a wildly incorrect product code? Never fear - Lucy will flag this for correction before integrating it to your ERP. 


More: