OCR-Driven InFlow Inventory Automation
Budget: £750 – £1,500 GBP
I need to turn every PDF despatch note I receive into a fully populated sales invoice inside InFlow Inventory software —no manual data entry, no copy-paste. The workflow I have in mind is:
1. A script or small service watches a folder (or an email inbox/API endpoint) for new PDFs.
2. The chosen OCR engine reads the document, pulling out five fields with high accuracy:
• Item description
• Quantity
• Reference Number
• PO Number
• SKU
3. The extracted data is mapped to the corresponding fields in InFlow and pushed through the InFlow API as a new sales invoice using the agreed pricing for each SKU.
I’m open to whichever OCR delivers the best results; PDF.co is on my radar, but Tesseract, Adobe, Google Cloud Vision—or any other option you can justify—are all acceptable.
What I expect by the end of the engagement:
• A functional prototype that runs on Window / Mac or online system.
• Clear setup instructions so I can redeploy or adjust it myself.
• Source code and brief documentation explaining how the extraction logic works, where to tweak field mapping, and how to add new templates if suppliers change their layout.
• A short hand-off session to walk me through testing with my own sample PDFs.
(Examples of despatch notes are attached).
Accuracy, stability, and maintainability are key. If you have prior experience with InFlow Inventory integrations or similar inventory platforms, let me know. Many thanks.
1. A script or small service watches a folder (or an email inbox/API endpoint) for new PDFs.
2. The chosen OCR engine reads the document, pulling out five fields with high accuracy:
• Item description
• Quantity
• Reference Number
• PO Number
• SKU
3. The extracted data is mapped to the corresponding fields in InFlow and pushed through the InFlow API as a new sales invoice using the agreed pricing for each SKU.
I’m open to whichever OCR delivers the best results; PDF.co is on my radar, but Tesseract, Adobe, Google Cloud Vision—or any other option you can justify—are all acceptable.
What I expect by the end of the engagement:
• A functional prototype that runs on Window / Mac or online system.
• Clear setup instructions so I can redeploy or adjust it myself.
• Source code and brief documentation explaining how the extraction logic works, where to tweak field mapping, and how to add new templates if suppliers change their layout.
• A short hand-off session to walk me through testing with my own sample PDFs.
(Examples of despatch notes are attached).
Accuracy, stability, and maintainability are key. If you have prior experience with InFlow Inventory integrations or similar inventory platforms, let me know. Many thanks.