In short
- An electronic workflow gathers orders from email, scanner and procurement platforms in one repository, recognises the customer and number, routes them through approval and saves them to the ERP without retyping.
- At the distributor HAMMERmed Medical Polska: 100% of orders handled electronically, zero printouts in the workflow, several thousand documents a month and an archive for the past year of tens of thousands of documents.
- A workflow for one process usually costs PLN 25,000-80,000 net (about EUR 6,000-19,000) and takes 1-3 months; at HAMMERmed implementing one workflow form took about 2-3 months.
- Every change creates a version with author and date - the basis for documentation requirements for medical devices.
- Start: an MVP for one order type as a pilot on real documents, then further types.
Where time goes today
- Every order is printed and passed to the warehouse, and after picking it returns to the office with handwritten notes.
- Order data is retyped into the ERP by hand - time spent and room for errors in item codes or quantities.
- The question "what stage is this order at" needs a call to the warehouse.
- Shipping documents travel with the driver and return days later.
- The paper archive takes up a separate room, and finding a document from a year ago takes time.
How an electronic order workflow works
- Intake: orders from email, scanner and procurement platforms land in one repository.
- Recognition: the system reads the customer and order number and assigns the document to the right person.
- Working on the document: corrections, annotations and signatures in the browser, without downloading the file.
- Approval and warehouse: the status changes in the system, and the warehouse and sales team see it on desktop, tablet and phone.
- ERP: an approved order is saved in the ERP without retyping.
- Archive: every version with author and date, search by customer, number and date.
Orders from procurement and tender platforms
If a hospital's procurement platform provides an API or export, we fetch orders automatically. If not, the document from the email notification is registered into the workflow and then follows the same path as other orders. Either way, all orders are in one place regardless of the channel.
Example: HAMMERmed Medical Polska
HAMMERmed Medical Polska is a medical equipment distributor. 2Simple built PDF Tool for it, an application that replaced printouts circulating between the warehouse, the office and drivers.
| Before | After | |
|---|---|---|
| Order workflow | Printouts between office, warehouse and drivers | 100% electronic, zero printouts |
| Data in the ERP | Retyped by hand | Approved order saved without retyping |
| Order status | A call to the warehouse | Visible in the system, also on tablet and phone |
| History | Handwritten notes | Every change as a version with author and date |
| Archive | A separate room | Tens of thousands of documents from the past year in the system |
The rollout started with an analysis of the document's path with the order desk and the warehouse, then an MVP for one order type as a pilot, and finally an extension to all document types. Today the system handles several thousand documents a month and is maintained and extended by 2Simple.
What it costs and how long it takes
| Scope | Cost (net) | Time |
|---|---|---|
| Workflow for one order type (MVP, pilot) | PLN 25-80k (EUR 6-19k) | 1-3 months |
| ERP integration (one system, one direction) | PLN 8-25k (EUR 2-6k) | 2-8 weeks |
| Further document types | Usually cheaper than the first - they use the existing system | a few weeks per type |
| Maintenance and development | about 15-20% of project value a year | ongoing |
Use the medical order processing cost calculator to see what manual order handling costs today - enter your own steps, times and rates.
Where to start
- Pick one order type with the most documents or phone calls.
- Trace the document from intake to shipment and note where it gets stuck.
- Agree what has to reach the ERP and who approves the order.
- Run a pilot on real documents and collect the team's feedback.
- Extend the workflow to further document types once the first one works.