Give the warehouse a mobile workflow that fits the ERP.
An order can be ready in the office while the warehouse still works from a printed list. A delivery can be checked at the loading bay but wait until later for someone to enter the quantities. Those gaps are a useful place to start when planning mobile work around Visma.net ERP.
Raptool WMS describes mobile picking, receiving and stocktaking, while its integration tools support exchanges with business systems. Visma’s official API documentation describes reading and writing ERP data. Together, these provide a basis for scoping a connected solution.
Confirm the exact connection first. The public material checked does not establish a ready-made Raptool connector for Visma Net ERP. The workflows below show what to agree with Raptool for your installation, rather than a list of preconfigured features. Raptool’s Jeeves listing concerns a different ERP product.
Four warehouse jobs worth connecting
| Process | At the mobile device | Result to agree |
|---|---|---|
| Order picking | Open assigned lines, scan products and enter picked quantities. | How the pick relates to the sales order and shipment; how shortages are handled. |
| Goods receiving | Check arriving products, quantities and destination locations. | The receipt record and the point at which accepted goods affect stock. |
| Location transfers | Identify the source, destination, product and quantity moved. | A traceable movement with the correct warehouse and location mapping. |
| Stocktaking | Identify each item and record the physical count. | A count for review, followed by an authorized adjustment where needed. |
A mobile app is useful when staff can finish the agreed recording task where the work happens. That can remove the second round of handwriting and typing. Physical handling, checking and counting still take time.
See how three mobile workflows could run
Select a planning example. These illustrations do not connect to a live Visma.net account.
From an eligible order to a verified pick
- Bring the agreed order lines into the mobile task.
- Show the warehouse, location, product and required unit.
- Scan the product, record the quantity and flag shortages.
- Return the result to the agreed order or shipment process.
Picked, packed and shipped are different milestones. Define which one the worker is confirming; a finished pick should not accidentally mark a parcel as dispatched.
Record what actually arrived
- Open the expected delivery against the agreed purchase reference.
- Scan the product and check whether the quantity means cases or pieces.
- Record accepted goods, shortages and damage separately.
- Return the accepted result through the agreed purchase-receipt process.
Test a partial delivery and a second delivery against the same reference. Decide when goods become available for picking and how rejected stock is kept out of that balance.
Count the shelf, then review the difference
- Choose the assigned warehouse and location.
- Scan the item and physically count the units.
- Record the observed quantity and count time.
- Review differences before approving an adjustment.
Keep an uncounted item separate from a confirmed zero. Agree how receipts and picks during the count period are handled, so later movements do not look like counting errors.
Make warehouse and location data agree
Visma’s warehouse documentation describes single or multiple warehouses and locations. Multiple warehouses and multiple warehouse locations require the relevant functionality to be enabled. Check the customer’s setup before designing a screen that assumes every item has a selectable bin.
Map the app’s warehouse and location identifiers to the ERP records. An aisle label such as A-01 is useful only if both systems interpret it consistently. Agree whether stock is counted by piece, case or another unit, and how the product barcode maps to that unit.
Show staff the stock figure they actually need. Physical stock, stock already committed to orders and stock available for a new pick answer different questions. Define the selected balance and update timing for the workflow, instead of presenting an unexplained number as “live stock”.
Agree what the connection may read and change
Visma’s API spans several services, so the integration needs the right service and operations for the job. Its authentication guide describes application registration, Visma Connect and permission scopes. Confirm access for the actual company and workflow before rollout.
Choose which system owns product data, orders, stock balances and completed movements. A confirmed pick must not deduct the same quantity twice because two systems both interpret it as their own stock transaction. Keep each result traceable to its task and define how repeated submissions are recognized.
Ask for a clear view of failed updates and a named person who resolves them. If work must continue without a connection, test the chosen app’s offline collection, retry and conflict handling. Do not assume that a mobile screen automatically provides offline synchronisation.
What could 90 seconds less administration save?
360 hours / 162,000 SEK per year
Assume 90 seconds less handwriting, re-entry and routine status chasing per order, across 60 orders a day and 240 working days. At 450 SEK per hour, that is 162,000 SEK in annual labor capacity before costs.
This example changes the administration around the order. It does not assume faster walking, fewer picking errors or higher sales. Measure the whole process once so the same removed task is not counted as several savings.
| Calculation | Example |
|---|---|
| Orders per year | 60 × 240 = 14,400 |
| Time released | 14,400 × 90 seconds ÷ 3,600 = 360 hours |
| Gross labor capacity value | 360 × 450 SEK = 162,000 SEK |
| Assumed annual running costs | 30,000 SEK |
| Annual value after running costs | 132,000 SEK |
| Assumed upfront cost | 36,000 SEK |
| First-year value after both costs | 96,000 SEK |
These are assumptions, not Raptool or Visma prices. Include devices, licenses, connection work, support, training and rollout in the actual budget. Released hours become cash savings when they avoid paid work, overtime or outside costs; using the same team to handle more work creates capacity.
Prove one workflow before extending it
Start with a small picking or stocktaking area. Use real product codes, a case-to-piece example and the warehouse locations staff will encounter. Agree the expected ERP record and physical-stock result before the pilot.
Test a normal task, a wrong product, a partial quantity, a repeated submission and an interrupted connection. Check the records after each case. Measure preparation, shelf work, office entry and corrections, including the people who handle exceptions. Those results give you a sounder business case than a scanning-speed headline.
Raptool and Visma.net questions answered
Can Raptool connect to Visma.net ERP?
Raptool documents integration tools and Visma Net ERP provides APIs. The public sources checked do not establish a ready-made Raptool connector for this exact product. Ask Raptool to confirm availability, supported operations and the work needed for your installation.
Which warehouse jobs could a mobile workflow cover?
Useful processes to scope include sales-order picking, goods receiving, location transfers and stocktaking. These are proposed workflows; the connection must support the required records and completion rules.
Can we use multiple warehouses and locations?
Visma Net ERP documents multiple warehouses and warehouse locations, subject to the relevant functionality being enabled. Map the app’s warehouse and location identifiers to the actual ERP setup.
Does scanning a barcode count the stock?
A product or pack barcode identifies what is being counted. Staff must still observe and enter the quantity, or use an explicitly configured per-unit scan mode. Review count differences before authorising adjustments.
Is Visma Jeeves the same integration?
No. Raptool’s public partner listing names Visma Jeeves. That listing does not establish support for Visma Net ERP, Visma Business or Business NXT; confirm the exact product.
How much time could the example save?
The hypothetical example saves 90 seconds of administration per order across 60 orders a day and 240 days: 360 hours a year. At 450 SEK per hour, this is 162,000 SEK in labor capacity before costs. It is not a measured customer result or automatic payroll saving.
Tags
Choose the warehouse task you want to improve. Ask Raptool to confirm the Visma.net connection and scope a pilot.
Explore Raptool WMS
